Hi Ian,
I think there is a way to customize the GUI without (direct) manual
manipulation.
If an application can generate expressive HTML, you can do all the
customization with CSS (a good web designer can make this work for us).
For "expressive HTML" I mean, HTML code with tags, ids and classes that let you
customize every aspect of the way each template/archetype node is displayed:
position, size, labels, etc.
This is the only way to do GUI customization for projects that generate the GUI
on the fly and that are web-based. (like the Open EHR-Gen).
Example:
This is an inexpressive HTML:
<form ..>
a label: <input type="text" name="xxx" ... />
<input type="submit" .. />
</form>
This is an expressive HTML:
<form id="openEHR-EHR-SECTION.soap" class="SECTION">
<div class="SECTION">
<div class="OBSERVATION">
<label for"xxx">a label:</label>
<input type="text" name="xxx" ... />
</div>
</div>
<div class="actions">
<input type="submit" .. />
</div>
</form>
Other idea is to use some CMS-like functions, like dragging and dropping
generated components on different zone of a web page layout. So, each user can
have its own customized GUI.
We can create a couple of these layouts, based on some GUI patterns and good
practices, and adjust our GUI generators to use one layout or the other to see
if the page generated is usable or not.
Our Open EHR-Gen Framework has some of this ideas already developed (each node
in our GUI-templates have a "pageZone" attribute that indicates in wich zone of
the web layout, this node has to be displayed). See:
http://www.openehr.org/wiki/display/impl/GUI+directives+for+visualization+templates
--
Kind regards,
A/C Pablo Pazos Guti?rrez
LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez
Blog: http://informatica-medica.blogspot.com/
Twitter: http://twitter.com/ppazos
> From: Ian.McNicoll at oceaninformatics.com
> Date: Fri, 3 Dec 2010 10:17:57 +0000
> Subject: Re: GUI-directives/hints again (Was: Developing usable GUIs)
> To: timothywayne.cook at gmail.com; openehr-technical at openehr.org
>
> 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
> >
> >
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101203/497f114b/attachment.html>
