I am supporting my family with Tapestry 5, and I don't know it half as well as some of the people on this list. It's also the only web framework I've ever used, so I didn't have to go through the "unlearning" stage. (That's not to say I don't swim against the current from time to time!)
Daniel Jue On 9/17/07, Charles Mason <[EMAIL PROTECTED]> wrote: > On 9/17/07, Christian Gruber <[EMAIL PROTECTED]> wrote: > > Well, so far I'm just learning T5, but have been having quite a bit of > > success with the live class reloading. As stated, it only reloads > > live for components/pages/mixins, and not model classes and others, > > but given the incredibly short restart time on a T5 app with Jetty, > > even that's ok. But when it comes to the actual designing of pages > > and components, I make a change, hit reload (on the browser) and it > > magically changes. > > > > I can second that. Class Reloading has saved me a massive amount of > time and increased my productivity no end. Plus although its only the > core tapestry related classes that get the live reloading, without the > masses of XML config the tapestry start up time under Jetty is only a > couple of seconds. I have to wait at least 15 seconds before my T4 > apps appear. > > T5 is still fairly rough around the edges, for instance some doc types > don't appear to be honoured correctly and not all of the generated > HTML validates correctly (although appears to work OK in the major > browsers). > > I can certainly see it being indispensable for my web projects in to > the future. For the time being I am using it for some of our internal > projects (where I know I can support it my self in production), > although also partly as a learning / evaluation process. Although its > currently Alpha most of the core stuff is at least beta standard. What > makes it alpha is the lack of certain features AJAX for instance, and > the knowledge that Howard & Co are still wanting the chance to make > some fairly sizeable changes that my break apps with the final > version. For some of our internal projects we only need the T5 Core > and we don't have problem updating them later as there's no client to > hand it over to on a certain date. > > Of course the difficult decision we will face soon, is for big > projects. Do we start now with the alpha build of T5 know / hoping it > will grow around us as T5 nears completion, or do you play it safe > with T4 knowing that the whole projects core is out of date almost > straight away, and accepting the big app reloading productivity hit. > > That's my thoughts any way. > > Charlie > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
