90 likes | 107 Views
This article delves into the user experience and choices made when layering an editor. It explores leaving the back door open, filling in boxes, and the integration with DDI using other standards. The article also discusses the UI, extending the basic UI framework, and fine-tuning DBXml.
E N D
Layering an editor • User experience • Choices made • Leaving the back door open • Filling in those boxes
User experience • DDI context • Conceptual view of the life cycle, questionnaire design and data structure
Sizing performance • Traditional techniques • Document Object Model • Simple API for XML • Pull parsing • DDI introduces hugeness • Default implementation • Oracle Berkeley DBXML • Data base environment
Moving around in the standard • Querying • XQuery with stripping out namespaces prefixes • Listing • Light DDI XmlBeans Objects • Self identification, parent identification and label text • Editing • DDI XmlBeans Objects defined previously in DDI Foundation Tools Project • Updating • XQuery Update specification
Leaving the back door open • Hooking into RCP with logic features • Adding a resource store complaint to XQuery Update • Using the back end for other purposes • DDI using other standards • DDI changes
Filling in those boxes • UI • Extending basic ui framework • Adding DDI prospectives, views and editors • Back end • OSGi bundling • Implement logic • Fine tuning DBXml
Thanks - Questions • Contact - Jannik V. Jensen - jvj@dda.dk • DDI FTP – Website - tools.ddialliance.org