Hi
As I assume not everybody interested in openEHR GUIs has set watches
for the relevant pages in the openEHR wiki, I would like to point to a
rather lengthly comment of mine:
For further remarks etc please use the wiki.
- Thilo
Thanks for this Thilo - a useful discussion. You do raise how the GUI documentation and work should be organised - we have .Net and XForms work proceeding at the moment. Some of the design issues will be generic, requirements also. So my question is how to split this. I would suggest that at the top level under developers we put have an XML page (to add to Java and .Net). We can then link into the technology specific pages when the need arises. Do others agree with this?
Cheers, Sam
Thilo Schuler wrote:
(attachments)
Sounds like a good approach! It’s good to share the common requirement and design.
Cheers,
Rong
(attachments)
Thilo Schuler wrote:
Hi
As I assume not everybody interested in openEHR GUIs has set watches
for the relevant pages in the openEHR wiki, I would like to point to a
rather lengthly comment of mine:For further remarks etc please use the wiki.
- Thilo
_______________________________________________
openEHR-technical mailing list
openEHR-technical@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
We in the NHS already have a complete Xml forms engine which allows one
to define your view on a chunk of a document using either XForms (using
Chiba to render into Ajax-ified html), XSLT (we provide some Ajax
javascript or you can write your own) or JSF (Java Server Faces).
It is very easy to create forms including adding nodes etc & it comes
with a complete WYSIWYG "Word Style" XHTML editor which can be included
simply by setting an attribute on XForm (or XSLT rendered HTML) of
mediatype="html".
I would love to OSS this & we should have by now but we're waiting for
the OHT (Open Health Tools) to set up their repository.
Adam
Adam
This sounds great. Would be a great to start a openEHR GUI project
and your stuff sounds like a fantastic basis. Just for curiosity: Why
did you prefer chiba over orbeon? Also looked at both and orbeon
seemed the more active project.
The Java Project needs a simple end-to-end demonstrator to show the
power of the kernel component. The open source GUI project could be
used for the presentation layer.
Custom widgets based on templates/archetypes should be a goal in the
long time. In my XUL experiment I played with XBL to create a masked
edit.
Honkala also suggests it in his thesis
(http://lib.tkk.fi/Diss/2007/isbn9789512285662/isbn9789512285662.pdf).
Though the current server-side XForms implementations don't support it
(yet). Formsplayer and Mozilla XForms (both client side
implementation) support it partially.
We need to keep this discussion up!
Thilo