kennar

If you search for my username in this forum, I uploaded a couple PDFs years ago.

In that case, probably of little value for your purposes. There is also Cairo: https://cairographics.org/download/ AntiGrain abandoned in 2006/7 but I seem to recall a fork of v2.4 by users: http://www.antigrain.com/index.html

Don't know if you're looking but thee is also G'MIC + CImg: http://gmic.eu/, http://cimg.eu/

Thank you. Now, I haven't yet looked at the tutorial but I think any effort to build teaching materials should be applauded.

Thanks, I'll probably go with the recommended option though good to know about Junctions.

I've just upgraded to a larger C drive and would like to move the Leadworks installation from another drive. I looked but it doesn't appear that the Steam client makes this easy. I assume I have to delete, manually or otherwise, then re-install. If not, suggestions would be appreciated. Thanks.

If you have the means, why not put your furniture in storage, then spend a few months in various cities. And, don't just limit yourself to the US.

That's great. There seems to be an error with downloading at the moment, will try later. I had started a manual conversion a couple weeks ago - just a few pages to explore formatting - and may continue in the new year. See attached. le3xb.pdf

Rick: This may not be to your liking but it looks like the Albalynx source has been opened (https://bitbucket.org/wolfhound512/albalynxproto?). I don`t mind it for my Allegro stuff because I essentially reuse the same code in every project. Also, ImGUI (https://github.com/ocornut/imgui) may be be suitable for utility projects.

Are updates immediate for everyone or are there geographic differences in how Steam handles new releases?

Is it confirmed that standalone will not get the 3.3 update?

Does one have to be connected to Steam whenever developing?

Again, I'm not opposed to upgrade costs and will likely (maybe) do this one but I would rather see a model of constant development and releases, with no lulls in the middle of the year. No bizarro marketing philosophies or teasers, just plain reliability. The example of Purebasic was offered earlier. Such an approach provides some confidence that the user base will grow. As noted above, this market is not captive meaning that users can simply switch, impacting the entire community. The potential for silence in the middle of the year is the perfect time to lose clients - too much ambiguity. Or, as in the case with Adobe, users often choose every second upgrade cycle. For a small operation that can prove fatal. And, again, the community suffers as a whole. Just my two cents.

Personally, I think anywhere from $50-70 would be fair while $99 is pushing the cost/benefit analysis over the long haul. Upgrade fees themselves are not a problem. Rather, the business model should be that features are added at such a rate as to attract and retain a large user base at that lower rate. What's the attrition rate at $99/year? Products die because users are not retained and there is no growth. The upgrade fee is only a part of the equation. I would suggest that this model of planning for yearly paid updates will work against an aggressive campaign to fortify the user base. The clockwork approach leaves me with a sense of something missing or that I'm being trapped. That said, it remains to be seen whether the Linux port will create additional synergies and growth. If 'yes', what should the upgrade fee be under those circumstances? Optimistic planning might have resulted in an upgrade fee of $50-70. Have faith.

How about integrated GUI before 3.2 comes out...during that year of development.