Hi Tim, I do tend to agree with you that GUI generation can be useful as a startpoint, but that most real-world applications will demand much a richer GUI that will need subsequent, manual intervention.
There are 2 other areas where auto-GUI generation can be useful. One is in the area of user-defined forms, a common feature in many applications. The other is in the area of requirements gathering and prototyping, either for EHR aplication development or wider standards development work. Dr Ian McNicoll office / fax? +44(0)1536 414994 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com Clinical analyst,?Ocean Informatics openEHR Clinical Knowledge Editor www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL BCS Primary Health Care SG Group www.phcsg.org On 3 December 2010 09:35, Tim Cook <timothywayne.cook at gmail.com> wrote: > On Fri, 2010-12-03 at 10:21 +0100, Pariya Kashfi wrote: >> Dear Tim, >> >> Thank you for your response >> Could you please provide me with more detail about this? >> Would it need manual adjustment of any css/style file or would it be >> totally dynamic? > > Well, you can generate dynamic UIs; but I really doubt that they are > useful in any real world situation. ?:-) > >> ?Is it based on the templates, archetypes, or both? > > Archetype based; with a layer of templating for local constraints. > >> I am trying to summarize the answers from different contributors, so >> that we can have a better image of the situation when it comes to GUI >> generation. > > Have you considered that it would be a good idea to conform to MSCUI? > > > --Tim > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > >
