Derek Hohls wrote:
Reinhard
I have been "with" Cocoon since the late '90s and as will continue
to use it unless forced otherwise... but is it really fair to say
that Cocoon is "easy to use" unless it (one day?) gets better
docs.
Compared with JSF and Struts Cocoon is very different. This means that you have
to learn to think in Cocoon (btw, the same is true for frameworks like Tapestry
or Wicket). Without good documentation it is very difficult to learn this way of
thinking and hence my reasoning that we need better docs.
Additionally, Cocoon 2.0 and 2.1 are huge frameworks and give you the impression
that you have to learn everything before you can even start. It is also
difficult to start your own Cocoon project and integrate it into your
development process, to configure it for different deployment environments and
to modularize it. Cocoon 2.2 will solve these problems and IMHO 2.2 will become
competitive again.
Furtunatly Cocoon 2.2 isn't far anymore (the release of the first release
candidate should happen next week) and some of us are working on a relaunch of
the Cocoon website which will come together with a major overhaul of our
documentation. Then we will see if our diagnosis concerning the technical
problems and my assessment of the importance of documentation was correct.
I know this a FAC (frequently occurring complaint) - and
if I ever come into an IT fortune such as Mark Shuttleworth's
this will be the first area I will invest in!
You're welcome :-)
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
