3 Introduction Problem Separate the User Interface from the structure and behavior. Many User Interfaces with many Platforms and Devices need many different toolkits. Solution One User Interface Description produces multiple User Interfaces.
8 Multiple Device Markup Language XML User Interface for cross platform development. Schema http://shrike.depaul.edu/~pjohnso2/UISchema.xsd MDML Documentation and Usage http://shrike.depaul.edu/~pjohnso2/MDMLAppendixD.htm
10 Rule File Profile describes properties of the toolkit and environment. Events describe the methods that are used to add listeners and classes that are used to provide the functionality Tags consists of rules for MDML tags that can be mapped to some GUI Toolkit attributes or methods.
11 Swing Profile javax.swing.* javax.swing.event.* javax.swing.border.* java.awt.* java.awt.event.* javax.swing.tree.* show SWING name
28 Requirement Update New Requirement User A needs another Calculator based on SWT. Solution Write A Parser and Engine to Map MDML or some XML User Interface to SWT. Create new rule specification for SWT.
36 Project Information Website: http://shrike.depaul.edu/~pjohnso2/
37 UI Framework Advantages Separation of User Interface from Behavior and Structure User Interface design and development is not tied to any functionality. Loose Coupling MDML is only mapped to GUI toolkit methods through a rule specification. This mapping is changeable. Code Generator Input file is a xml file; XSLT can provide the input for another code generator.
38 UI Framework Disadvantage Overhead As with any XML based project a user must first write the xml. In this case the rule specification and the MDML. But, once the rule specification is written this a one time event unless the toolkit changes.