Automatic event hookup. Specify event handlers on XSWT objects using the x:id mechanism and have a reflection-driven engine that hooks them up automatically.
Support “dom”-like UI events: e.g. activating or deactivating a control affects the other controls.
Have the XSWT compiler generate code that automatically hooks up events.
XSWT editor proposals
Interoperate with Eclipse’s Visual Editor Project (hard).
Extend current XSWT preview to do GUI editing (straightforward, but a bunch of work).
WADs (works as designed) and known bugs
Full accelerator key support for menus:
"accelerator" is done. But accelerator text 't' does
NOT work in "setText".
will display "NewtAlt+Shift+N" in the menuitem.
XSWT Preview. <getshell> may have side-affect to Eclipse RCP when changing shell’s properties inside a XSWT preview editor. A new Shell may be constructed from a dummy composite in the XSWT Preview editor whenever such method is called.
Sometimes x:id is not matched properly. There seems to be a bug in the forward-reference resolver.