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]
