GUI-directives/hints again (Was: Developing usable GUIs)

Hi Koray, I agree with Thomas here, Koray, but I take your point about the separation into a further layer represents added potential development complexity. I think we should expect tools to handle this in the same way that a complex development environment like Visual Studio handles various

GUI-directives/hints again (Was: Developing usable GUIs)

these separate layers during development. exactly - thomas -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101208/71781480/attachment.html

GUI-directives/hints again (Was: Developing usable GUIs)

suggest that the GUI templates just reference paths found in the openEHR template. - thomas -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101208/57ab6747/attachment.html

GUI-directives/hints again (Was: Developing usable GUIs)

-- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101208/679651d3/attachment.html

GUI-directives/hints again (Was: Developing usable GUIs)

Hi Pablo, In both ADL1.4 and 1.5 every path is still an archetype-based path. The proposed schema for an operational template is very similar to the XML schema of an individual archetype but obviously includes multiple aggregated archetypes and omits any nodes which are constrained out.