W3C home > Mailing lists > Public > public-forms-testsuite@w3.org > December 2004

RE: XML-Forms

From: Thomas Mueller <tomtom.mueller@gmx.de>
Date: Mon, 6 Dec 2004 18:23:35 +0700
Message-ID: <000801c4db86$0adaab60$fb78fea9@bigmac>
To: "public-forms-testsuite lists.w3.org" <public-forms-testsuite@w3.org>

>>Idea here is to use JAVASCRIPT within XML documents to create
>>User Interface and exchange information between user form and Ada
>>application.
>>I think this approach is very good as along term strategy.
>I agree very much with you. What is needed is a simple HTTP server written
>in Ada so we don't ended up married to Explorer.
>It would also be possible to set up connections between JavaScript and Ada
>using either AdaApplettes or TCP/CORBA/COM connections to Ada code from a
>Java proxy to the JavaScript.

The approach for using WEB browser as user interface to an application via
uploaded HTML (XML) documents from the embedded HTTP server is already
implemented in LynxOS.

In LynxOS this is a standard approach to create user interfaces
to the (embedded) applications.

So use LynxOS and you will have off-shelf solution.

Here some quotes from Linx:
=============================================================
GUI Provider
A Web browser can provide an ideal environment for the graphical user
interface of
development tools. The GUI for these tools could be written in, say,
Java.

Embedded Systems and the Web
Web protocols are already revolutionizing the user interface to
embedded systems. In the past, in order to meet cost limits, many
embedded systems had only non-graphical user interfaces, or
manufacturers provided special client side software for PCs running
Windows or Workstations

Embedded systems can now provide powerful, user friendly graphical
user interfaces to virtually any client without any client side
software and only use a small amount of system resources

This allows the embedded system to be accessed by a Web browser.
To provide a simple graphical user interface to the system, the
developer creates an HTML page that sits as data in ROM or mass
storage on the embedded system. This HTML page could be only a few
Kbytes of data. Pictures and icons are easily added as GIF or JPEG
data. For a more powerful GUI, a Java applet can be added. The Java
applet sits on the embedded system as byte code. A few tens of Kbytes
of Java byte code can create an impressive user interface. The byte
code is actually loaded onto the client side PC or workstation for
execution and communicates to the rest of the embedded application
via a socket. No Java interpreter or run time memory is required on
the embedded system in order to provide networked graphics with this
scheme. There is a huge memory savings over running X clients on the
embedded system to provide a GUI.

Benefits of Web protocol approach
There are many benefits to the Web protocol approach to providing a
GUI for remote embedded systems. First, no client side software need
be written. The embedded system can provide a friendly user interface
to any computer over a local network and even over the Internet
itself. Very few resources are needed in the embedded system to
provide the graphical interface, especially if the system already
supports networking. Systems with local graphics can run a local
browser to provide the same look and feel for both local and remote
access. There is no shortage of programmers who know or wish to learn
how to use HTML and Java to build first rate graphical user
interfaces. Full user level interoperability to the desktop world is
provided.
---------------------------------------------------
http://www.lynx.com/products/whitepaper_galaxy.html
===================================================

--- GoldED/386 2.42.G0614+
 * Origin: Everything goes the bach runter ... 
 * http://casinogamblingtest.com
Received on Monday, 6 December 2004 11:24:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:38:40 UTC