Hi! On Wed, Feb 9, 2011 at 19:03, Ian McNicoll <Ian.McNicoll at oceaninformatics.com> wrote: > I very rarely now use DV_BOOLEAN when modelling but agree that using > DV_TEXT/CODE_TEXT is a pain to map to a checkbox/radiobutton GUI.
Unless you reduce that mapping pain by having nice GUI-hints/directives with documented semantics that you can use (primarily in templates) to indicate that this DV_CODED_TEXT should be presented as a radio-button-style group or checkbox (possibly with default). Good GUI-hints combined with logic machinery could also be used to open follow-up questions if desired as previously discussed in the thread named "Re: GUI-directives/hints again (Was: Developing usable GUIs)" where on Mon, Dec 20, 2010 at 13:05, Erik Sundvall <erik.sundvall at liu.se> wrote: > Discussion examples follow (with the risk of ADL errors that Tom's > brain-integrated ADL parser :-) will catch and he then can correct) > > In section 6.5.4 of > http://www.openehr.org/svn/specification/TRUNK/publishing/architecture/am/adl1.5.pdf > a way of defining variables is specified. > Perhaps a (preferably Boolean) variable could be defined as an > archetype rule like... > > $smoker:BOOLEAN ::= > /data/items[at0003.7]/items[at0009.3]/value/defining_code matches > local::at0013 > > ...and an annotation on a tree structure that should be shown in GUIs > only when documenting smokers could be... > > annotations = < > ["/data/items[at0003.7]/items[at0010]"] = < > items = < > ["GUI-show-if"] = <"$smoker"> -- Other annotation name > examples: GUI-hide-if ... > ["some other annotation"] = <"whatever"> > > ...or perhaps... > > annotations = < > ["/data/items[at0003.7]/items[at0010]"] = < > items = < > ["GUI-trigger"] = <"$smoker"> > ["GUI-action"] = <"show"> -- Other annotation value examples: > hide, collapse, expand > ["some other annotation"] = <"whatever"> Best regards, Erik Sundvall erik.sundvall at liu.se http://www.imt.liu.se/~erisu/ Tel: +46-13-286733
