Separate UI and data
Posted: Fri Nov 21, 2014 12:27 pm
I always found frustrating the user interface of web applications: no one would ever think to use a "photoshop" in a browser. Web browser are too generic and just not up to the task. Java and PHP are tough...
LiveCode suggested to me, by its very structure, how easy it would be with it to separate the engine, the interface and the data. But strangely I can not find a trace of this on the web.
Imagine that you download from a web page, on your handheld or iPad, the "engine" (a LiveCode standalone you built): a blank page able to dowload from a web address, to create buttons, fields...controls, but nothing else. From the web you then download a "UI", that is a document (txt, xml or stack that describes the interface that I bought, which is nothing more than all the properties of the objects to be created + the scripts that make the application work).
The "engine", when it is launched on the handheld, read these data and creates buttons, fields, text, graphics, scripts and all that is needed (such as a database interface or the game of tick / tack / toe).
Once the interface has been built, the application is able to upload / download the necessary data (in the case of the database) or connect with other users (tick / tack / toe) and give the user a "satisfying" UI .
In the case of the database, an heavy "sort" of data would be made on the remote server, but the local processor could handle the display of those data, the changes of the layout, and so on. A graphic update of chart tick / tack / toe would be managed by the local processor, but statistical analysis of 10 years of gaming could be made and served by the remote server. Version updates would be a snap. Security would be a big concern but, seen the power of modern processors of handhelds and iBooks, everything could be encrypted. And the download web sites would have to be qualified...
It seems to me an excellent idea and I do not understand why I can not find a trace of this on the web. And Livecode is perfect for this (beside the lack of sockets on mobile). Unless it's a dumb idea.
Someone wants to comment?
LiveCode suggested to me, by its very structure, how easy it would be with it to separate the engine, the interface and the data. But strangely I can not find a trace of this on the web.
Imagine that you download from a web page, on your handheld or iPad, the "engine" (a LiveCode standalone you built): a blank page able to dowload from a web address, to create buttons, fields...controls, but nothing else. From the web you then download a "UI", that is a document (txt, xml or stack that describes the interface that I bought, which is nothing more than all the properties of the objects to be created + the scripts that make the application work).
The "engine", when it is launched on the handheld, read these data and creates buttons, fields, text, graphics, scripts and all that is needed (such as a database interface or the game of tick / tack / toe).
Once the interface has been built, the application is able to upload / download the necessary data (in the case of the database) or connect with other users (tick / tack / toe) and give the user a "satisfying" UI .
In the case of the database, an heavy "sort" of data would be made on the remote server, but the local processor could handle the display of those data, the changes of the layout, and so on. A graphic update of chart tick / tack / toe would be managed by the local processor, but statistical analysis of 10 years of gaming could be made and served by the remote server. Version updates would be a snap. Security would be a big concern but, seen the power of modern processors of handhelds and iBooks, everything could be encrypted. And the download web sites would have to be qualified...
It seems to me an excellent idea and I do not understand why I can not find a trace of this on the web. And Livecode is perfect for this (beside the lack of sockets on mobile). Unless it's a dumb idea.
Someone wants to comment?