On 8/28/06, Mattias Forss <mattias.forss at gmail.com> wrote:
>
> 2006/8/28, Bert Verhees <bert.verhees at rosa.nl>:
>
> > > There is already a Java-based archetype editor available here:
> > > http://svn.openehr.org/knowledge/archetypes/dev/index.html
> > Too bad, the sourcecode still is not published [...]
>
>  If it had sourcecode with it, I would
> > have repaired this, for my own use, because I have need for an
> > Archetype-editor which can also be used for debugging purposes.
>
>
> The source code will be published as open source in the future, but we at
> Link?ping university haven't decided when that will be.
>

If there now are people that seriously want to contribute to the development
with patches etc (like Bert suggests) I believe that it's time to publish
the source very soon. We'll try to look in to this within a couple of weeks.
Remind us if we forget it ;-)

So there are two Archetype-Editors, both look about the same in GUI, but
> > both are build on complete different technologies. And both need
> > improvement.
> > I think there is a need for more, specially if there are improvements on
> >
> > GUI-thinking. I know, all Word-processors look the same, and all cars
> > look
> > the same, but is it the best way a car or Word-processor should look?
>
>
> Your suggestions on improvements are always welcome...
>
> We do not know, so I suggest that someone who want to build an
> > archetype-editor, should not look at those who exists, he could get
> > trapped in obvious thinking.
>
>
> We had a lot of ideas when building the Java archetype editor concering
> the GUI, but eventually decided to design it like Ocean's GUI. There are a
> number of reasons we did this...
>

Since it begun as a master thesis project I believe one of the main resasons
for not inventing too many interface changes was the limited time available.
Personally I am interested
in information visualisation and usability and have several thoughts
regarding possible interface alternatives. Time/resources still remain
constraining factors so focus is on geting a somewhat complete editor first
(and debugging/stabilising existing archetypes & specifications underway).
But feel free to experiment with and contribute alternative views as soon as
we release the code.

Best regards,
Erik Sundvall (ex-supervisor of Mattias, but now a colleague)
Currently at MIE in  Maastricht
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060830/a639d998/attachment.html>

Reply via email to