With the compiler and language modernized, the next step was to create an ecosystem for it, one that could handle large-scale deployment.


What we mean with 'large scale deployment' are applications on the scale of Adobe PhotoShop, or a full accounting system, or even Quartex Pascal itself for that matter! Large applications that are technically demanding with as many as 100 forms involved. Applications that under vanilla JavaScript and HTML would be very time consuming to create and maintain.


We wanted a system that made that level of engineering possible from a traditional approach, with form design, property inspector, event handling and all the time saving benefits that RAD tools are famous for. It shouldn't take weeks to knock out a form driven web application, and developers shouldn't have to work with esoteric and often conflicting libraries.


JavaScript is powerful but it paradoxically suffers from having too many libraries available. We wanted a reliable and solid foundation, the same foundation that we were used to from Windows and Linux programming. A foundation that could easily be expanded with new components and packages, or even absorb readily available JavaScript libraries. A foundation that could target both the browser and server-side part of the equation.


We needed a run-time library similar to Delphi, C# or Swift, where it's easy to create your own classes and ramp up functionality through inheritance.

We likewise wanted a simple mechanism for users to register their own components with the IDE and form designer. And further, we wanted a package system so component collections could be easily distributed or sold.


While these things are conceptually simple on the level of idea, creating an ecosystem from scratch is quite a challenge.

Also keep in mind that we are dealing with source-packages, where things like license management and encryption had to be re-invented specifically for the medium.