[Lazarus] *SPAM* Re: Win 10 IOT Core

[Michael Schnell]

On 10/20/2015 11:26 AM, Michael Van Canneyt wrote:
>
>
> A browser application (any RIA) such as used in QNA is in fact a 
> client/server application.
> The client just happens to be a browser.
>
> ExtJS is meant to run in the browser.  The gui is built from A to Z in 
> the browser. It is there for a 'local' GUI from the point of view of a 
> developer or end user.

So the Client application would completely have to be written in Java 
Script. (To me: Yuck !!!)

>
> To me, a 'remote' gui is built on the server and then sent to the 
> client (browser).
> In this scenario, the server has at all times a mirror of what the 
> client sees. This is stateful, therefor not scalable, and in general 
> IMHO should be avoided.

This is exactly what I thought.

You can see it even more in detail:

In a modern PC, the Graphic card's processor renders Text and created 
things like rectangles, this might be considered very basic widgets.

To the PC's main CPU this processor is remote (i.e. attached via a 
defined API "Bottleneck"). So in fact any GUI can be considered a remote 
GUI.

With Linux the X-Server is in between. Same is "remote" (here the API 
even can be TCP/IP) to the application.

Usually a windowing system and widget set is still in between again 
"remote" to the application via an API.

In this sense, with a Lazarus application, the LCL might be considered 
"remote" to the user code.

So there are multiple layers of remoting a GUI and for a logical view, 
it is not a real difference how large the mechanical space between the 
client and the server at any API is.

So to me it depends on multiple circumstances (hardware, OS, resources, 
speed requirement, intended use, deployment issues, ....) if or if not 
"remoting" any of the multiple APIs is or is not a good idea for a given 
project.

-Michael