Skins
In Wasabi, most objects are interfaceless. A skin is not merely paint, it is more like stuffing : the software is essentially a wireframe structure with no visible parts, but with events flowing freely and with listeners ready to start up yet more internal events. The job of a skin is to reveal selected events and data using the GUI/TUI, and to serve as a source of events and data for the wireframe structure udnerneath it (ie, buttons, input fields).
Skins are DOM? and group based:
- The XML will look somewhat like the old wasabi.
- The basic piece of UI is the group, every UI piece is in itself potentially a group (ie, for instentiating a group definition as child content).
- In addition to instantiating groups, UI objects may hold arbitrary children, as defined by the hierarchy of the DOM for that node, group instantiations are expanded as child nodes in the DOM.
Support for old wasabi skins (ie, win3/win5) is not planned.
Skin loading from remote locations should be supported eventually by using file readers.
