> > In order to integrate self-written components we currently only have > > user-roles to make these components available to the component manager. > > But the configuration of these components still needs to be added to the > > cocoon.xconf. This is IMHO dead ugly and bad for upgrade and maintainace > > cycles. > > We should be able to have a separate configuration besides the > > configuration for the core components. We should be able to define a > > user.xconf. (or better user-components.xconf?) > > I've brought this up a couple of times, and we've talked about > this offline as well -> I think it's a great idea, and will be > really useful. > > It would also be great if it allowed hierarchical including of config > data (not just a single level of includes).
Hmm.. let's start with a single level first :) did you come up with an idea for a multi-level syntax yet? -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
