Does anyone know if it is possible to integrate AJAX techniques
with the tapestry approach? This is something which we have used
to great effect where I currently work where for instance we have a multitude
of linked dropdowns where the choices of 1 affects another and so on, and, with
lots of items on the page, it is clearly more efficient to just reload the list
from the server using a combination of AJAX and Javascript.
For this scenario, I am concerned that if this solution were not available, the
performance would be significantly affected.
Is there an alternative solution which would work with tapestry if AJAX is not
compatible?
Does anyone have any thoughts they would be prepared to share?
Thanks :-)
Gareth Deli.
[EMAIL PROTECTED]
--- John Coleman <[EMAIL PROTECTED]> wrote:
> Hi,
>
> > I was a little concerned about the comment in the serverside article that
> > essentially said that tapestry does not look like it will be adopted on a
> large
> > scale, simply because of the steep learning curve... as someone new to it,
> I
> > can certainly agree that the learning curve is pretty much vertical, but
> is
> > this something that is on the cards to change? One thing that would help
> > 1000000% is to have more tutorials, taking people through form submission
> and
> > logging in for instance.
>
> I think Tapestry is unlikely to be adopted large scale simply because it is
> not a Sun standard and isn't a natural progression from the existing
> JSP/Struts domination. But look at the popularity of Struts, it's not Sun
> and also takes a while to master. And I'd like to know what practical
> expereince these Tapestry critics have - IMHO don't bash it until you've had
> a good go at it and compared it to more conventional means of production. It
> took our developers a few weeks to get up to speed with Tapestry, it is
> harder, but they really like it, and going back to Struts and JSPs now can't
> be taken so seriously. Furthermore the code they produce is of much higher
> quality than when you work so close to the servlet. With Tapestry we find
> module tested code can be released to the client for a play with little more
> than a look over. With prior projects on JSPs/Struts we need a system tester
> to really bash the app hard for a long time to get out all the bugs, of
> which there would always be plenty. We are seeing shorter times from
> conception to result, and less cycles of test and fix.
>
> What would help Tapestry is for tools like Spindle and Palette to get up
> with version 4, as v4 contains many radical improvements, it's easier to
> use. We need more RAD tools, and I'd like to see some kind of component
> generator for hooking up to ORMs easily, maybe a form designer. I remember
> how easy it was to write neat, but feature rich GUIs using MS Access. With a
> COM like Tapestry, this should be a realistic possibility.
>
> Sun have already adopted ideas out of Hibernate for EJB3, and facelets is
> similar to Tapestry. But how long does it take to learn JSF and facelets
> anyway? And at the moment Tapestry seems to be more established than JSF.
>
> John
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo!
Security Centre. http://uk.security.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
