Henri Dupre 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)

It's not that I find anything particularly perplexing or difficult about
hivemind.  What I object to is having to learn hivemind, period. It's
one more hurdle between being on the learning curve and being
productive.  Why add more barriers to entry? Again, let me emphasize the
my opinion that it seems like, in all, the use of hivemind for tapestry
internals is a very good thing; I think a lot has probably been cleaned
up.  However, why not keep it there? That is... if hivemind is being
used for Tapestry internals, why not keep it internal? Again, it simply
comes down to barriers to entry and/or barriers to upgrading. At some
point in the future,  I'm sure  I will upgrade from the 3.x series. But
that time isn't now for me.


Robert

P.S. all of the above having been said, the items you mention below
would certainly be very useful.

> 
> 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.
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to