Overall, It would be more convincing if it were written in Free Pascal.
I also wrote that it would compile fine under FPC, which then leads to the obvious -- that it can exist on all platforms which lazarus/fpc targets. Secondly, it's based on a Delphi codebase - why is that less convincing than one written in Lazarus/FPC? The code is the same..
When it comes to the web/HTML5 part, there is a lot of people who dont see the full potential before they try it.
For instance, consider this:
** Using Delphi/Laz you can write web-apps, typically apache/IIS extensions which are native
** You can build REST based services on top of that
** You can use third party packages, like mORMot to create SOAP/JSON services
Thats a lot of work and it's expensive because you have to rent a PC instance, as opposed to just simple hosting. Because running IIS/Apache modules is not "normal" in the eyes of hosting companies, who specialize on .net, nodeJS and php. But, when you can target JavaScript you can do the following:
** Write server using Smart Pascal, compile for nodeJS
** Write HTML5 client using Smart pascal, compile for browser
** Package client using Phonegap -- voila: iOS, Android and blackberry binaries in 2 minutes.
** Upload the whole shabam to any NodeJS host, no "native" super expensive server rent to pay!
If you want to re-cycle the nodeJS server for native FPC/Delphi clients, that is simple and super-easy. People need to catch up with how people are making apps today because it's very different from how we did things 8-10 years ago. Pascal is timeless, but the way we distribute our knowledge has changed. Especially with cloud/virtualization, which allows you to upload a whole vware-image to the cloud and host that. Long gone are the days of html hosting !
So why waste 2 months coding a JS based website, when you can spend 2 days writing it in a language you already know, and it runs in the browser and on every mobile platform out there -- native (thats what phonegap does)? By expanding our toolbox, object pascal can do some absolutely awesome tricks usually reserved for C# and (shrug) java. But pascal does it better, safer and faster!
But native is my primary concern, and as mentioned -- FPC will be the primary compiler, both for the IDE and by the IDE.
The focus here is really not so much the "what and who", but rather "how". QTX is a generic IDE, meaning that it can be used for anything. Want to build a "game pascal"? Go ahead, the IDE is ready. Have you made a GPU code compiler for your ASM projects? Oh you are missing an IDE -- well I have just the thing for you.
It's generic and will thus work with whatever you define for it. Language etc. is defined by INI files -- as are project entities (e.g Project -> Source, project -> resource file, project -> application unit).
Think of it this way: SynEdit is a generic code-editor. QTX is a generic code editor. You can use it for PHP and laugh in the face of EMB's "php builder", or for FPC as a lightweight alternative to lazarus (or delphi) -- heck, throw mingW in there and use it for C++ development if you like.
