3 ms·
In our framework, we basically have "pages" which can be loaded/unloaded using AJAX for you, and "tools" which you can put on pages. So a developer can quickly
by EGreg 13y ago
In our framework, we basically have "pages" which can be loaded/unloaded using AJAX for you, and "tools" which you can put on pages. So a developer can quickly put together an app out of pages and tools, and wire it up, with just a bit of data going between the server and the client. What's more, he or she can set up heavy caching (e.g. on a CDN) of the AJAX responses, making the entire interface render client-side like a native app. We even have support for storing a bundle locally -- in, say, PhoneGap -- and still use the newest files as they are updated on the server in subsequent releases.
Components and models are loaded "on demand", and instead of MVC -to- MVC syncing we have opted to have one MVC, with the authoritative model on the server, and messages being broadcast to all participants in the stream.
So basically the "best practice" is to grab some existing tools and stream types, or create new ones. Everything "just works" out of the box.
- porker 13y agoIs the framework available/visible anywhere? It's a neat approach, one I've thought about but never done anything towards. Kudos for turning it into reality!
- EGreg 13y agoYep, you can see some of it here; http://qbix.com/blog http://qbix.com/blog http://framework.qbix.com http://framework.qbix.com we are working on rolling out a much better framework portal for it though.
- lobo_tuerto 13y agoI can't see too much on the second link. What's the point if it is password protected and you don't give it away?
- EGreg 13y agoWe are building it in a cathedral before releasing 0.9 to the bazaar :)