And all of this translates into more sales or getting more completed games made with Leadwerks? I assume those are the 2 ultimate goals of the company? This is a pretty big investment and I'm curious what you think the big payoff is.

This doesn't seem to be about giving the community a GUI to use in game more than your own GUI for the launcher and editor and some games could take advantage of the framework for their game if they want which if not using the stock drawing still requires a fair amount of work which reduces the benefit for us.

Is it justified for the Linux share or even future Mac support share to do this? Do you know the share between the 3 OSs and does doing all of this make financial sense for Leadwerks or is it more of a pet project of yours because desktop GUIs can be painful to work with?

This aspect of what you're doing or have planned just seems like classic scope creep of a simpler idea of giving us a game ui framework. Feel free to put me in my place and explain the ROI but at face value I don't see it when there are so many other game related things people are looking for.

I'm just curious on your thoughts from a business standpoint.

good work , heh this entry was fun to read , old code but still doing the needed stuff

Rick, that's a good question. There's a few things to consider.

The education market is a natural fit for Leadwerks and a good opportunity to get real-life usability testing, but without Mac support we can't go after it. Cocoa and some BlitzMax OpenGL code are presently preventing Leadwerks Editor from running on Mac. It's not impossible, but I hate to throw a lot of work into something that's ultimately going to give a sort of half-*** result and a lot of continued bugs.

On the Windows side, the Win32 API is our primary obstacle in producing a 64-bit build of the editor. The API used 32-bit integers for some pointers, back before anyone imagined the length of a pointer would change, so that causes a lot of problems.

I know I want to add more game templates, revise the documentation, and add video tutorials. If we ever intend to refresh the UI, then it makes a lot of sense to do that before working on docs so we don't have to go back and redo everything.

Finally, I know I have to implement an in-game GUI for you to use, so it makes sense to knock the UI refresh out at the same time, with the same code.

Finally, Microsoft has completely abandoned all semblance of UI consistency, and unfortunately the standard win32 interface is now perceived as "outdated".

Taking control of the GUI code frees us from a lot of vendor APIs and bugs, and allows me to innovate in the user interface in ways I can't do with the Windows API. When I think about the editor I want new students using next year, the UI refresh makes a lot of sense.

So yeah, better learning materials + formal education = higher rating on Steam and more games.

Thanks for the explanation!

every day i felt a couple of month outdated about almost everything!

thinking it twice that's a good signature to use

Sorry but I just have to say this is so funny