> But at the end I may warn you about Tapestry Magic. Ha ha! :) I'm with you all the way on that one! Nowadays, I tend to write more Workers than I do pages! There's nothing that can't be solved with a good Mixin and a bespoke Worker! (Actually I have a question coming up about that...)
On 11 September 2011 19:43, Taha Hafeez <tawus.tapes...@gmail.com> wrote: > Sorry, iphone's send is too eager to send a mail... > > This is a question for which you are going to get a lot if responses. > Here is mine > > On Sun, Sep 11, 2011 at 4:51 PM, Taha Tapestry <tawus.tapes...@gmail.com> > wrote: >> >> >> On Sep 11, 2011, at 2:26 PM, Alfonso Quiroga <alfonsose...@gmail.com> wrote: >> >>> Hi! I've used tapestry 5.0 some time ago, in a small app at home. Now >>> in my work I've to decide which framework we will use for a state >>> application on internet. >>> I've a lot of experience with struts2, I can just choose that, but I >>> prefer the component model against the action model. >>> >>> 1) Is tapestry 5.3 a good choice for a site, where 2 o 3 web >>> developers will be developing? >>> > > I would say yes as I have upgraded one of our applications to 5.3 and > it is better with more widgets, alerts, new ajax support. I am now > working on moving our second application to 5.3 > >>> 2) I'm NOT an expert in tapestry, and I know the "static structure, dynamic >>> behavior" has some limits, which are this limits? >>> > > The limits are there for developers who tend to think in terms of > structs. If you use tapestry as a component based framework you will > almost never notice these limits. At least I haven't (I can't say the > same about Wicket). > >>> 3) Finally, in the future, in my job I will need some widgets that >>> could use ajax, is hard to accomplish this? (in struts2 is really easy) >>> > I am not sure what you call easy. May be you haven't tried tapestry's > ajax. I have worked with structs and nowadays I am working on a rails > project and I can tell you ajax is a pain in these frameworks when you > compare it with tapestry. Tapestry abstracts away a lot of your ajax > and once you put them in a component you can just forget about the > complexity of ajax. > >>> Thanks in advance, >>> >>> Alfonso >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>> For additional commands, e-mail: users-h...@tapestry.apache.org >>> >> > > But at the end I may warn you about Tapestry Magic. It is an addiction > and once you start using it you get lazy and are always searching for > a way to make the framework do everything for you. You just want to > write an annotation and a worker and say "Abrakadabra".. :) > > > -- > Regards > > Taha Hafeez Siddiqi (tawus) > http://tawus.wordpress.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
