Component Markup Language

[Robb Shecter]

Nigel Hutchison wrote:

> Then a server could project its own GUI api and leave it to the client side
> to choose C++, Java etc to build the interface at run time.

Yes.

> I suspect that
> in most cases the bandwidth required to shift the XML GUI description would
> be quite a bit less than the
> compiled java classes. If this is so than "Even Cooler" would be XML GUI
> interpreter built into a Internet Browser.

How about this: Have one XSL document per client side scripting language.  That is, different
XSL documents could implement:

Component-XML->DHTML             (This particular one would give you your "Even Cooler" idea.)

Component-XML->Java BeanShell
Component-XML->Smalltalk
etc...

...then, a client side browser applies whatever XSL template is best for it, gets the the
resulting kind of script it understands, and on the fly generates a UI.

- Robb


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)