From: "Stefano Mazzocchi" <[EMAIL PROTECTED]> > giacomo wrote: > > > > On Thu, 7 Mar 2002, Jeremy Quinn wrote: > > > Regardless of the particular issue of reorganisation proposed by Nicola Ken > > > Barozzi and Stefano's response, which I agree with ..... I think the > > > samples in the main sitemap would definitely be improved by being seperated > > > into several sub-sitemaps. The main sitemap is far too complicated, it > > > makes Cocoon look more complicated than it really is to use! > > > > Good point. As a general usage pattern to show how stuff can be > > implemented with the current instrumentation it would make sense to have > > the root sitemap only mounts all examples. The Cocoon samples site have > > grown to a point where this will make absolutely sense. > > +1
Ok, so I'll start reorganizing them (from a directory POV) incrementally as subsitemaps served under "samples". If anyone sees issues with this happening, I'll be happy to know them and change my actions accordingly. As for patches-bugs, I've been trying to get them to a low level in these days, and patches are basically all applied-reviewed. There is one that IMHO needs detailed scrutiny: "Cache improvement using ESI invalidation protocol" (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6879). Anyone has comments on this? As for bugs, they are 32. I'm starting to try and fix them now that patches are applied. If anyone wants to give a hand, I don't mind ;-) Finally, when are we doing 2.0.2? What are we waiting for? Following Stefano's roadmap: 1) DOCUMENTATION IMO samples are the best documentation one can give. Hey, did you guys learn XSLT reading the spec or hacking on ready made ones? ;-) This is where the sample reorganization can help a bit. As for the proper documentation, the usual rule applies: who want to contribute is well accepted :-) As for the auto-documenting classes using Javadoc tags, any news? IMO it would be great! 2) SPEED The compiled sitemap is part of the solution. To make it easier to be tested, I propose a simple installinterpretedwar (I'm not the king of names, suggestions are welcome ;-) that can install Cocoon with the new sitemap easily. And we can use the treeprocessor, starting from now, to make documentation with it, like Forrest does. 3) SYMMETRY Where are we at currently? I've seen Jeremy's editor and saw great possibilities ahead. Comments? 4) APPLICATION MODULARITY Scheduled for 2.1 Can't wait to see it happen :-) 4) FLOWMAPS 2.2 and beyond, in the deep space of XML nirvana... -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
