Piroumian Konstantin wrote: > > > > > I think we (= Cocoon community) should clarify our opinion > > about this first. This includes: > > - Do we have a simple Sitemap InputModule Component? > > We have simple InputModule Component and it's not a sitemap component at > all. > > > - Are the current InputModule and OutputModules of a more > > general approach > > and do we want to donate it? > > Not sure here. The most applicable place for InputModules, IMO, are the > sitemap substitution variables. I've never used OutputModules, so > can't say > anything about them. > > > > > If we agree on this, then the next step would be to involve > > the avalon community. > > I feel that we are again going to stuck. Can't we move on with them in > Cocoon and then if we see that modules are general enough to be used in > Avalon then we'll move them there? > Ok, perhaps I didn't make myself so clear: My proposal is to define two InputModules: a) One simple sitemap InputModule as discussed in the last days b) The general approach already implemented. And this general approach should not reside in Cocoon.
Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
