Quoting Matthew Langham <[EMAIL PROTECTED]>:
> I suggest we go for whatever solution allows us to get development of
> tools
> such as the sitemap editor moving quickly. One of the important factors
> that
> will decide the success of Cocoon in the long run will be the
> availability
> of tools.
>
> So either include it in the Cocoon CVS or go for sourceforge. I think
> that
> it would be best to go for Cocoon CVS as this would allow Cocoon to
> become a
> "complete" package (building up tools as we go along) and also make sure
> the
> tools stay in sync with Cocoon (which may be more difficult if they are
> on
> SF).
>
> Also - the developers would probably be the same as those currently
> working
> on Cocoon (or come from the same groups) - At least they would in our
> case
> :-)
This might be a short term solution. But take into account what Bruno said: "It
might edit every XML file" and thus might start a project of itself.
The same is true for the xml-java toolkit.
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
