For me, learning hivemind would have been easier if: -) Configuration was either documented more, or provided more examples. Examples are the best pieces of documentation you can hope for combined with a reference.
-) Examples :) -) HiveDoc getting javadoc href links....and more examples :) On 6/16/06, Henri Dupre <[EMAIL PROTECTED]> wrote:
On 6/16/06, Robert Zeigler <[EMAIL PROTECTED]> wrote: > > I'm not saying I'm opposed to Hivemind integration in tapestry; I > suspect that it has made the code cleaner, better, more customizable, > etc. I would just like to see it much more transparent in tapestry. I > want to learn tapestry to write webapps; I'm not interested in learning > Hivemind to write frameworks. What is funny is that now that I know hivemind, I can't figure out why it took me so long to understand it... Hivemind is actually very simple, quite verbose but there are no difficult concepts involved. Which specific points do you find difficult to achieve with hivemind? (vs tapestry3) I believe it would be quite easy if there was some small examples such as: - how to inject my spring DAO into my service - how can I get in my service this or that tapestry object - how can tapestry take into account my service (example with a webrequest filter for instance) - how to deal with different scoped services (e.g. something that requires an instance for each request vs one global instance) - how to add a webrequestfilter - how to change the exception page Thanks, Henri.
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
