XSWT Design Docu Goes Live

Hi,

  Dave Orme - member of the Sweet project - has posted
his thoughts on how to move the XSWT prototype forward
in a paper titled "XSWT Requirements and Design".

  Dave proposes the following requirements and
non-requirements. If I may quote:

  * Design XSWT to be maximally human and
machine-readable/writable
    
  * Keep the XML markup portion of XSWT as thin as
possible. This requires some form of one-to-one
mapping between XSWT markup elements and SWT classes /
properties / style bits, etc.

  * Provide an XSWT rendering engine that is as simple
and lightweight as possible. This engine should be
easy to embed inside an application.

  * Maintain compatibility with Sweet metadata for
describing new SWT controls.

  * Facilitate machine-generation of XSWT from GUI
builders, etc.

  * Enable event handlers to be set on SWT objects as
simply as possible.

  * Return a simple data structure representing the
SWT layout for the purpose of dynamically registering
and unregistering event handlers from client code.

  Just as importantly, XSWT does not try to do any of
the following:

  * Implement XUL.
  * Implement XForms.
  * Implement anything higher-level than SWT and JFace
native constructs.

  The intent is that for those who desire it, XSWT can
be generated via XML transformations from XUL, XForms,
etc. 

  Full story @
http://sweet-swt.sourceforge.net/designdoc/xswt_design.html

  - Gerald

PS: What is XSWT?

XSWT is a mini-XUL prototype created Chris McLaren
(IBM Canada) that lets you create Standard Widget
Toolkit (SWT) UIs (aka Eclipse UIs) using XML.

More info @ http://article.gmane.org/gmane.comp.lang.xul.announce/18


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01