This is a good thing because these performance improvements coupled with new framework technologies like Enyo, NodeJS and PLV8 are allowing us to build a browser based client with performance that meets or exceeds our compiled C++ based client. Another even more obvious benefit is that it has allowed us to build a new client architecture that works on any device, mobile or desktop.
Here's a short over view of the technologies in our new stack:
Enyo and Backbone
Enyo is a framework for building HTML5 applications that work on all devices, but ironically the way it works it allows us to do this without writing any HTML. Our Enyo application structure is built as an object model hierarchy so that components are reusable which is essential for an enterprise application. In layman's terms what this means is we've created a set of building blocks that we can quickly mix and match to create new modules and applications with unprecedented speed. We call our framework of user interface objects enyo-x. You can see an example of an object like our ComboBox widget here. What I find particularly exciting about an example like that is it is only 149 lines of code! Less code for us will mean a higher quality and more powerful application for you!
Wed, 11/28/2012 - 14:44#1
John, just the overview and diagram I was looking for tie it all together!
Thu, 11/29/2012 - 17:39#2
Are you still using PLpg/SQL
Are you still using PLpg/SQL for your business logic?
Thu, 11/29/2012 - 18:29#3
Yes and no. One of the
Yes and no. One of the important goals of this initiative is that the web client be completely interoperable with the existing GUI client. Another important goal is that we not add major new dependencies to the GUI client, at least on this first pass, or destabilize it by gutting and completely rebuilding it from the inside out. It is very, very important to us that the GUI client remain solid and reliable because thousands of people depend on it for mission critical business operations. The GUI client itself will have no reliance on PLV8 in 4.0, and continues to use the existing plpgsql business logic it always has.
Fri, 11/30/2012 - 10:31#4
I have to admit... this
I have to admit... this overview looks fantastic!
Wed, 05/15/2013 - 22:20#5
are we moving away from QT++?
are we moving away from QT++? I hear Openbravo also uses enyo.
Thu, 05/16/2013 - 06:20#6
We are continuing to maintain
We are continuing to maintain the Qt Desktop client. Version 4.1beta of that client will likely be released today which upgrades to Qt version 4.8.