I agree it would be nice to have every component re-implemented in T5. However, components are easy to add and easy to remove (when the framework supplies one). I think T5's core code, the stuff you can't easily amend or replace, is the focus ... we could spend forever "perfecting" T5 and never get it out the door. I want to set the T5 baseline now ... it's already almost a year late based on my original plan. I'm not begrudging that year ... T5 is actually much cooler, faster, better, more finished, more stable, than I would have predicted when I started 2.5 years ago, but still.
On Tue, Sep 9, 2008 at 11:53 AM, Vjeran Marcinko <[EMAIL PROTECTED]> wrote: > I'm all for giving people first all those things that previous versions of > Tapestry already had, so migration of those old Tapestry apps to T5 would be > possible. > > One of shortcoming of T5 compared to T4 that I'm having great need of is > lack of context in Submit component: > http://issues.apache.org/jira/browse/TAPESTRY-2434 > > There is some "context submit" component on WIki, but this feature should > really be included in T5 core... > > Cheers, > Vjeran > > ----- Original Message ----- From: "Howard Lewis Ship" <[EMAIL PROTECTED]> > Newsgroups: gmane.comp.jakarta.tapestry.devel > To: "Tapestry development" <[email protected]> > Sent: Tuesday, September 09, 2008 7:25 PM > Subject: Just about ready for the release candidate? > > >> In case you've missed it, I've been raging on the bug lists the last few >> days. >> >> I think we're very close to a release candidate now. There's just a >> couple of more bugs to hit first. >> >> I hope to get something ready (by) this weekend for a vote. >> >> If you think something is dreadfully missing, please speak up (and >> vote it up on JIRA). >> >> I'm confident that >> a) Functionality people need is present. >> b) Anything missing can be added in 5.1 without sacrificing backwards >> compatibility. >> c) 5.1 will not take as long as 5.0! >> >> Seriously, about (c), I'm leaning towards future releases being >> driven, say, 80% by schedule (every four months, perhaps) and only 20% >> by features. >> >> -- >> Howard M. Lewis Ship >> >> Creator Apache Tapestry and Apache HiveMind > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
