Yesterday evening we hit the publish button for Quartex Pascal v1!
It has been a long, long road with too much work to list, but we feel that its reached a level of maturity that makes it usable by everyone.
It is easy to forget just how much tooling is involved, not just in the IDE or RTL, but also on the back-end. Our back-end system is written in QTX itself, dealing with everything from the internal build process to licenses to everything else under the sun.
Well, we hope everyone has a great time with v1.0 -- and help us spread the word!
Hello,
Where can I read the documentation?
Thank youÂ
It is in the IDE. The "documentation" button, last on the toolbar to the right.
The docs are being worked on every day here, so it will grow more and more, but it has the essentials for digging into QTX 🙂
I'm disappointed with the price and licensing.Â
And no, I'm not disputing all the work that has gone into it. I actually *want* to like your product. But TMS Web Core comes out cheaper than your first (fairly limited) version.
The entire Delphi community knows what great support TMS offers. Add to that all their FNC components and well...
I will experiment with the 15 day trial, and hope for the best. But I really can't (yet) make a personal case for the expense of continuing.
Fair enough. We are not forcing anyone.
There are two different philosophies between Webcore and QTX. We work closer to the metal with focus on JS integration, while TMS is more focused on having a delphi web environment. They also have a couple of years head start.
The first release now is more "the foundation" stone if you will, and we will issue hotfixes and updates almost weekly for a while (one due tomorrow).
When mistakes and minor issues are taken care of, then we can focus more on the widgets / controls and pull in things like database grids and so fourth.
There is a lot of functionality in the IDE and RTL that doesnt get attention yet. Things like ragnarok, being able to sculpt your own message protocols and the IDE generates code for you. That is very valuable when you are making a clustered back-end with async connections (or rest for that matter). I think remobjects charges $250 (or something like that) for their editor which does similar things for delphi.
Once we push v1.1 with non-visual components and drag & drop database, ragnarok will make a lot of sense. The same goes for the desktop environment.
Our goal is not just to give you some prefabricated controls, but to build a tool that covers "full stack", meaning back-end and front-end, while also integrating directly with established JS frameworks.
I've been waiting for the first release and can understand the price bump. I'm already carrying a bunch of commercial licensing costs for Pascal / Delphi where it's not being used to make money (yet, it's always a fallback plan).
I'm willing to get a license, because I want to see every ones efforts here, the technology and company be successful. Both the subscript and yearly one time purchase are billed annually.
Will there be changes in licensing and subscription costs anytime soon?
Will there be any discounts on future renewal - or full price as advertised year on year?
If one starts as a subscription, your licensing implies you can no longer use your current version at the end of the subscription term ... This doesn't make much sense, and there is no clear benefit of subscription, or yearly purchase year on year (other than you can continue using your frozen in time release). Which seems really weird since they're the same price yearly to start.Â
I love where Quartex is going for Web and Server based system on web native based technologies like node (bun or deno) .. but to move over to it from native code to replace existing investments is a long stretch for me. This is just some personal commentary from a interested developer.
Your licensing forces me to only go for a single year, and find out what ends up being delivered, and where you pricing and licensing ends up. And I really hope this last year of funding see's Quartex begin successful.
Have I misunderstood anything here?
Thank you.
I am wondering which license option is right or recommended for me to purchase.Â
@tkaytraviskay-ca "If one starts as a subscription, your licensing implies you can no longer use your current version at the end of the subscription term"
No, you are free to use the product as much as you like. The subscription is for updates. So just like any other product the subscription ensures that you get updates and access to all new features that year 🙂
@tkaytraviskay-ca Easiest is to go with a normal, one year license. We are building up a lot of things now, with new features every month - so it will be an exciting journey. Right now we have QTX running natively on MacOS, Linux and Windows (x64) and MacOS + Linux for ARM. We got non-visual components in and the RTL is being adjusted for exposing underlying RTL classes as components. Oh and datamodules too 🙂
