[Don't Design Libraries Like This]

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 Design Libraries Like This]

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

[[BallGame] - Easy game development with LeadWerks]

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

[Relocation]

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.

[What's Next]

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.

[Leadwerks Game Engine 3.5 Now Available]

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

[Leadwerks 3.1 Pre-orders Now Available, Indie Edition coming to Steam January 6th]

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.

[Leadwerks 3.1 Pre-orders Now Available, Indie Edition coming to Steam January 6th]

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.

[Native Code Tutorials]

I would also prefer that the tutorials not be scattered across dozens of documents. Easily accessible and downloadable will avoid the problems experienced with the LE2x. Everyone should have the opportunity to download the entire 'course' in one click. PDFs would also be a bonus.

[Native Code Tutorials]

Might I suggest that you not directly launch into the FPS but rather spend some time detailing and expanding on the major elements of the API, with examples. I would prefer comprehensive generic knowledge versus what may become a narrow trajectory.

 

Indeed, marketing on native code coupled with too much focus on Lua sends mixed messages. A coherent presentation would be most appreciated.

 

Also with many features currently missing I do hope that the documentation will not be left incomplete (as those features are being added).

[New environment set for sale: Kabul Streets]

Great offer. On my list of TODOs for this weekend.

[Lesser gaming.]

Rick: Makes sense however the research/simulation world is a blend where individual projects as defined stand a greater chance of completion. With respect to school children or the military applications the constructed scenarios are effectively game-like, minus the full story.

 

Let's rephrase and suggest that skills could be "leveraged" while still working games. These worlds are not mutually exclusive. My assumption is that most here would like to remain in the gaming marketplace knowing that income must be supplemented.

 

I wasn't really suggesting that folks switch streams rather the key point was that a product like LE serves multiple overlapping markets consequently design choices must take these into consideration.

[The Basics]

Thank you.

 

That's a very big step from this perspective.