> People, please, order! > > The sense/nonsense ratio in this thread is dangerously low.
Hm.. sorry, but I feel a bit defensive... When thinking about the way the user-roles are currently used I think it's only straight forward also to have a user.xconf (whatever you like to call it). And the replies proove there is a requirement - so it makes perfect sense. (I'm a bit sensitive about the word nosense ;) That this might not be sufficient is another story... but then the user-roles is also not enough anymore... > Torsten, > > I do see the need for componentized Cocoon apps, but in order to provide > this a significant number of things must change in Cocoon. So what do yout think must change? We are talking about configuring components that are already known by the Cocoon CM (user-roles). So what's the big deal? Enlighten me... > My idea is: let's make it a fully-baked solution, rather than a > half-baked 'it does what I need so I'm happy' one. Hm... I think you have already more in mind that you willing to tell right now... So I forgive you ;)) and I'm looking forward for your RT on this. Cheers -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
