On 18.12.2017 22:49, Graeme Geldenhuys wrote:
Web apps users have different needs and expect different behaviour to
desktop applications.
Not in my world :-).
Same consists of embedded software that most of the time does not need
any GUI at all. But usually a network connection is available.
But it needs to be monitored or configured whenever necessary.
Here either
a) some hardware could be provided to have the maintainer do that
(i.e. a local GUI using some standard library (such as mseGUI) and some
standard widget set)
b) a standard web server or web server interface (such as CGI or
Apache API) is implemented and a standard browser is used to attach to
the device.
c) some propriety protocol and a dedicated software to run on a PC is
implemented. The communication could be either defined by the GUI
library (-> ifi) or be propriety according to the needs of the
application (GUI and "Business-Code" separation).
Finally:
b1) part of the application runs on the remote site in the browser,
the communication could be either defined by the GUI library (-> ifi) or
be propriety according to the needs of the application.
The application might either run on dedicated hardware or on a web server.
Now in a perfect world it should be possible do to a normal (mse-)GUI
application (->a) and just set a switch to compile it to work according
to (->b).
Of course it would be acceptable if only a subset of the full range of
visual components is provided in such portable way.
Obviously b) and b1) ask for pas2js (or even better for pascal to
webassembly) compilation.
-Michael
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
