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: Moving InputModules into the sitemap [was: [RT]: Dynamic variables in the Sitemap / Input Modules revisited]
Date Fri, 10 Jan 2003 11:35:20 GMT


Carsten Ziegeler wrote:
> Sigh..
> 
> Let's not re- and re- and re-discuss these things over and over again.
> I have the perception that (long time ago) we agreed in a lengthy discussion
> that we want to declare *all* sitemap components in the sitemap for
> visibility reasons. The user should not really know/care about cocoon.xconf.
> 
> And I had the perception that we agreed (not so long ago) in a much longer
> discussion, that the input modules (for the same visibility resons) belong
> in the sitemap and not in cocoon.xconf.
> 
> Am I wrong with this? Do I have a weak mind and should take a one month
> vacation in the south caribbean? (And if so, who can sponsor this...)

No need to discuss this again. Blocks will be able to plug in new Cocoon 
components, and those will still need to be defined by the user. How 
those components will be available is still to be decided, but IMHO all 
can be made available with no further declaration.

-- 
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