Perhaps a volunteer could compile the result of this thread, turn it into a Cocoon Document Dream List, and submit it as a new planning doc patch. We have a *great* start with Gerhard's original document. When volunteer asks to contribute/enhance existing docs, they can consult with this dream list for ideas.
I know planning isn't a sexy, but we sure could use this. Thanks. Diana On Wednesday, May 15, 2002, at 09:32 AM, Nicola Ken Barozzi wrote: > From: "Per-Olof Norén" <[EMAIL PROTECTED]> > >> I personally would like something like a component refererence >> (similar to >> the one that exists today, extended/rewised). >> This would include the "Cocoon Internals" that carlos suggests below. >> I´m > a >> litte fed up with looking at the code just to remember the >> attributes/elements/namespaces for a given component. >> I consider myself being on a firstname basis with cocoon and most of >> the >> times its enough with component reference and a simple usage example. > > Great idea. > > There is a proposal about using special javadocs to document Cocoon > Components, so that this ingo can be generated automatically. > > It would be really swell... what is needed to make it work? > What are we waiting to move that code over here? > > :-) > > -- > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
