On 6/16/06, Kevin Menard <[EMAIL PROTECTED]> wrote:
On Thu, 15 Jun 2006 22:51:26 -0400, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: I'm not sure adding more documentation will fix it. People simply don't want to have to read all of it in order to do what are trivial tasks in other frameworks. If you're well-versed in HiveMind, it actually is quite powerful, but to casual users HiveDoc and the HiveMind registry are confusing as hell.
I really believe more documentaiton will fix it. Look at hibernate... It is a complex system, and what makes it accessible is IMO their documentation. There are enough examples and explanation in the documentation to get most of the usuall configuration and programming done. And understanding all the different hivemind constructs, and how to apply them in tapestry is not straightforward at all. The examples on the hivemind website are very simple. I learned most of the hivemind stuff by looking at the tapestry xml files. I also find the hivedoc confusing. I understand it now after I'm familiar with hivemind and some of the tapestry code but when I started moving our stuff to tapestry 4, I couldn't figure out how to connect anything together or how to inject somekind of service. If there was a little documentation on the tapestry website on how to create a new hivemind service would make the learning way easier. And also more hivemind configuration examples would be great.
Please just consider the balance between flexibility in the framework and intuitiveness / learnability for the users.
My theory on this is that the documentation makes the difference. Spring and hibernate are not straightforward at all but they have large documentations that make it easy to get a project going. Thanks, Henri.
