Quote: "Darkbasic is DX based. Eventually AppGameKit will have all teh bells and whistles of Darkbasic, but done in a better way, as now TGC have much more experience of what users want "
This is what I fear. I will admit, anything that The Game Creators programs and sells now is way out of my league in terms of coding ability and management. I will concede that fact.
However, instead of adding new features,
how about working out the current problems with the toolkit? As a customer who is developing multiple projects with AppGameKit, I would much rather:
*Get multiple sounds to be played at the same time, which is implied in the documentation but fails in real-life
*Manipulate arrays within the code, without having to wonder whether or not declaring it in a IF/ELSE block will crash the app
*Be able to deploy my application onto the Amazon Marketplace, which currently can't be done because the Android AppGameKit Player cannot hold state between switching apps
Look at Google Code. Many of the issues there are improvements slated to be in the next build of AGK. I understand that, as a toolkit there is supposed to be a natural evolution of the tools. But instead of worrying what new features will be included in the next build, let's make sure AppGameKit has a proper debugger. Let's make sure that the compiler always correctly displays which line the code errors out on.
In a sense, switching back to procedural programming from object-oriented has been a huge change for me. I programmed in DarkBasic for a bit, but in the end for me it became less about programming and more guessing how I can jury-rig the applications to work.
As a customer, I don't want to see AppGameKit go down that same path.
Hi there. My name is Dug. I have just met you, and I love you.
