The "To Do" list has a very important task which appears
to be neglected. The cocoon.xconf configuration files need
all parameters for all components to be listed inside the
various cocoon.xconf files.

I tried to raise this issue in a previous thread (copied below).
However, that thread has been misinterpreted and is now
being continued with a different topic.
--David

----------------------------
Date: Mon, 5 Nov 2001 12:25:05 +0100
Subject: documentation of components in */cocoon.xconf
From: "Carsten Ziegeler" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
>
> just do it today, as we have the outstanding changes
> to the factories, today will not be rc2 day.
> 
> Carsten
> 
> > -----Original Message-----
> > From: David Crossley [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, November 05, 2001 6:45 AM
> > To: [EMAIL PROTECTED]
> > Subject: documentation of components in */cocoon.xconf
> > 
> > One of the big todo items before final release is to 
> > document everything in cocoon.xconf
> > There are various xconf files:
> >  documentation/cocoon.xconf
> >  webapp/cocoon.xconf
> >  webapp.site/cocoon.xconf
> >  webapp.tutorial/WEB-INF/cocoon.xconf
> > 
> > Before we all dive in and document our favourite component,
> > i thought that it would be a good idea to tidy these files to
> > make them more readable and consistent. There were a lot of
> > differences that were not necessary (e.g. indentation)
> > so i fixed that. I also added consistent structure for the
> > comment section for each block. I have not added anything
> > new - just aligned and tidied the files as a start.
> > 
> > Now it can be more clearly seen that there are some differences
> > between the various xconf files. Anyway, we can each
> > attend to that, now that there is a consistent base.
> > 
> > I am holding back on these commits, because today is RC2
> > day. Should i do it now or later?
> > cheers, David


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to