Sylvain Wallez wrote:
So one big problem again here is documentation. Not user-level docs that has been identified as a problem for long an which is currently considered seriously thanks to Reinhard, but developer-level documentation. We can reasonably suspect that many potential developers try to find they way in the code but go away because the internals are poorly documented. And this includes both source-file docs (javadocs & comments) and higher-level big pictures.
For this reason I've added a section "Cocoon internals" with some sub-topics. It would be very helpful if Carsten, Torsten and you could help out to fill in the blanks there. (The named topics are orientated on what I'd like to see there ;-) )
--> http://brutus.apache.org/docs/build/cocoon-doco-2-2/
I don't think that each and every details has to be explained but the big concepts behind with some pointers to the sources. Then I'm with Stefano that the navigation in your favorite IDE should be enough.
--
Reinhard P�tz Independant Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}web(log): http://www.poetz.cc --------------------------------------------------------------------
