cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicola Ken Barozzi" <nicola...@apache.org>
Subject Re: POI Serialization code committed
Date Tue, 12 Mar 2002 07:55:34 GMT
From: "Steven Noels" <stevenn@outerthought.org>

> Andy wrote:
>
> > Steven wrote:
> >
> > > So I am all unofficial +1 for having a separate module for Cocoon
> > > contributions, where we can add the POI integration work, if enough
> > > people step up as a maintainer.
> >
> > +1 if there are enough to justify it.
> >
>
> I hope the remainder of my arguments are not lost, however. This is
> suboptimal solution until POI admits it really should become part of
> their own codebase. Only the real Cocoon-specific classes should
> eventually go into the contrib section of Cocoon CVS. POI supporting XML
> is not in scope for Cocoon, neither.

Cocoon is becoming overcrowded with optional components, and this is a fact.
For this, I think that we need a contrib section, which is optimal for
Cocoon IMHO. In the near future it will be the famous "Cocoon Blocks"
section.

I'm +1 for this. I'm refactoring examples in this direction, and will commit
ASAP.

There is also a strong user need for XML serialization of POI formats, and
this is another fact.
I have the same feeling Sylvian has, that there is a need for xml
serialization outside Cocoon, and AFAIK noone argued against this need.
But we all should remember that POI is still in early stages in formats
other than Excel, and it has to stay tightly focused if it wants to grow
fast; this is how Andy and Marc made the project get to current level, and
it's a strategy that works.

I understand that this XML conversion stuff is not a thing that only Cocoon
needs, but this can be said also to of cocoon contributions.

All Cocoon Generators, Serializers and Transformers could be used out of
Cocoon, and IMHO this could make a cool project itself.
I think that the best solution now is to make a contrib section, move there
all stuff that is not core Cocoon, and investigate on making wrappers to
make these Components act also autonomously.

What do you think?
It seems to me as a fair solution for all.

--
Nicola Ken Barozzi                   nicolaken@apache.org
            - verba volant, scripta manent -
   (discussions get forgotten, just code remains)
---------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message