[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Re: [Gnumed-devel] NOT pretty XUL?!?
From: |
Thilo Schuler |
Subject: |
Re: Re: [Gnumed-devel] NOT pretty XUL?!? |
Date: |
Mon, 21 Feb 2005 02:54:16 +0100 |
Tim,
thanks for the link. I know the tutorials at xulplanet. There are also two
online books on xul (mozilla-xul-book @ xul-http://sourceforge.net/projects/xul
and http://books.mozdev.org). The latter one is 2 years old and the framework
has changed partly!!!
I have played a little bit with XUL and I know how error-intolerant it is. An
IDE would be a great step forward. Still,
http://www.faser.net/mab/installation.cfm is a role model what can be done and
with the firefox success XUL will become more popular.
As a test run I want to build a front-end for Horst's new Drugref (via XML-RPC)
as a semester project. If it works I want to use it as output format for an
openEHR generator based on archetypes.
Would be good to stay in contact. I like your comments on the GNUmed list.
-thilo
address@hidden schrieb am 21.02.05 01:32:56:
>
> Tim Churches <address@hidden> wrote:
> >
> > Thilo Schuler wrote:
> >
> > > Hi Tim,
> > >
> > > I have been trying to approach you with this. I would like to know
> > > more about your XUL explorations and why you thought it's not pretty.
> >
> > > Maybe I have to reconsider the implementation tools.
> > >
> > > I am in SYD too, so we can either discuss it via email or I give you
> > a
> > > ring or even meet with you.
> > >
> > > Hope you didn't purposely ignore my other attemps and this is just
> > > another annoyance... ;)
> >
> > Thilo,
> >
> > Go ahead and assess XUL and PyXPCOM yourself. Don't allow my comments
> > to bias you.
>
> Thilo (and others if interested),
>
> Further to that, have a look atteh ttorial on XUL app development at
> http://xulplanet.com/tutorials/xulapp/
>
> If you follow the tutorial carefully you should end up with a simple
> working app. If you get *anything* wrong it will fail completely and you're
> unlikely to see any debug output indicating where the problem lies. And
> there are a **lot** of files to check through looking for the error
> despite this being a trivial application.
>
> The whole thing seems incredibly fragile and at this stage poorly documented.
>
> Tim C
>