>>
I am -1 for this. They don't belong there for SoC. As long as we are back
compatible none of the users should care. But people starting with cocoon
from scratch should get on the right track from the start.
<<
Hmm... so a site administrator defining pipelines will _have_ to look in
both the sitemap.xmap and cocoon.xconf to see which sitemap components are
available - right? Isn't this more confusing than what we have at the
moment - where the administrator just needs to look at the sitemap.xmap?

By SoC you are saying that the person who defines the available sitemap
components is different from the person who then defines the actual
pipelines. I agree that this may often be the case - therefore the argument
is valid. However not giving the sitemap author at least a hint as to which
components he can use strikes me as being a step back from what we already
have.

Now if we had a super sitemap tool that read the cocoon.xconf and the
sitemap.xmap and then presented the author with the components he can
use.... :)

Matthew

--
Open Source Group               sunShine - Lighting up e:Business
=================================================================
Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
Tel:+49-5251-1581-30  [EMAIL PROTECTED] - http://www.s-und-n.de
           Weblogging at: http://www.need-a-cake.com
=================================================================





-----Original Message-----
From: Torsten Curdt [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 14, 2002 10:18 AM
To: Cocoon-Dev
Subject: Re: [Vote]: Where to define the sitemap components?


On Thu, 14 Mar 2002, Carsten Ziegeler wrote:

> Hi Team,
>
> I'm still not convinced that it is a good idea to have some components
> (generators, transformers etc) of the sitemap defined in the cocoon.xconf
> and some in the map:components section of the sitemap.
>
> We will confuse many users with this, believe me. There will be many
> complains that for example the file generator isn't available any
> more, as it is not visible in the sitemap.
>
> So for a forthcoming release, I propose to move them back into the
> sitemap and after the release we can think of a better way of defining
> components.

I am -1 for this. They don't belong there for SoC. As long as we are back
compatible none of the users should care. But people starting with cocoon
from scratch should get on the right track from the start.
--
Torsten


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


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

Reply via email to