OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Component Markup Language

[ Lists Home | Date Index | Thread Index ]
  • From: Robb Shecter <shecter@darmstadt.gmd.de>
  • To: Nigel Hutchison <nwoh@software-ag.de>
  • Date: Fri, 04 Nov 2011 17:51:38 +0100

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.


> 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

...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@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@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)

  • Follow-Ups:
    • XML Mail
      • From: Clark Evans <clark.evans@manhattanproject.com>


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS