On Thu, 15 Jun 2006 22:51:26 -0400, Jesse Kuhnert <[EMAIL PROTECTED]>
wrote:
People shouldn't have to go to the hivemind site to use tapestry. This is
true. Not even to use the cool hivemind features of tapestry. The
removal of
.library/.application combined with a proper page or two of
documentation on
the tapestry site might be able to fix this.
This is the crux of the issue, I think. Tapestry 4 made Tapestry easier
to use in many ways, but made it way more difficult in other ways by
relying on HiveMind so heavily. Tapestry has always been criticized for
having a high learning curve -- requiring learning HiveMind on top of that
doesn't help matters any.
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.
Please just consider the balance between flexibility in the framework and
intuitiveness / learnability for the users.
--
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
