I understand there's always a lot of trepidation when thinking of switching to a new framework.
> Tapestry ready for production? The short answer is yes (T5.2 tidied up a lot of loose ends and really brought the framework together). 1). Yes, that's an ideal size. I'm in an active team of about 5, but 2 or 3 of us are always working on the front end somewhere. 2). The only limit I was ever aware of was not being able to dynamically load templates on the fly (say from the file system). But I think there's a way to do that now in T5.3 - but it's not something you're ever going to want to unless your developing some kind of Portal Editor 3). There is already a fair bit of built in support for Ajax for a lot of common scenarios (e.g. updating parts of the screen on clicks and selects). It's not too difficult to hook in your own stuff either. People come to Tapestry because they're looking for a web framework, but it offers so much more than just that. I find the IoC far superior to any of the rivals (Guice, Spring, etc...) Depending on what you're developing, T5 is not just about pushing content to a browser, it's about doing it an efficient and scalable way. Automatic JS and CSS consolidation combined with GZIP compression is just the tip of the ice-burg. But in the end it comes down to how you develop; I find a lot of web developers are happy enough cobbling pages together by means of cut'n'pasting Spring examples from all over web and layering random jQuery scripts on top. It's not my favourite approach, but it does yield quick results and suits a lot of people. Now, I dare say you can't develop the same way with Tapestry - for it's a powerful "Framework" that allows you to do cool stuff. It is not (currently) a library of 1000s of components that will do all the work for you - but it is really easy to develop your own components that do exactly what you want. When they say, "Code less, deliver more" they really mean it. Any problem can typically be solved in a few lines of code - you just have to think about it for a minute first - which may not be everyone's cup of tea. Tapestry is an event driven framework with (typically) 2 phases / trips to the server per request - and this can confuse the un-initiated. Then again, in a retrospective we had this week, one of the new guys wrote up, "T5 - I get it now! It's Awesome!" I left Struts years ago (after producing much commercial software for it) and never looked back. But you're on a Tapestry Forum, asking if Tapestry is any good - you're not going to get a lot negative answers! All you can do is have a play, ask questions and see what you think. Have fun, Steve. On 11 September 2011 16:56, 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? > > 2) I'm NOT an expert in tapestry, and I know the "static structure, dynamic > behavior" has some limits, which are this limits? > > 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) > > Thanks in advance, > > Alfonso > > --------------------------------------------------------------------- > 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
