tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship" <hls...@attbi.com>
Subject Tapestry Schedule
Date Tue, 25 Mar 2003 18:37:06 GMT
Discussion in two parts.  1) beta? ga?  2) transition

How much longer can we continue in  2.4-alpha?  I know I'm running out of
steam on major feature enhancements at this point.  We're waiting on WML
components from you, and MB has threatened to add another parameter
direction. Beyond that, just a few minor feature enhancements and bug fixes.


If everything goes well on the book, it could be on the shelves by Labor day
(i.e., early september 2003).  Do NOT hold me to that, much is well beyond
my control.  I would like 2.4/3.0 to be GA by that time, after a good long
beta/rc period.


Transition 2.3 to NextGen

Outside of the package rename, most code should work unchanged, with a few
exceptions:
1) The exception heirarchy has flattened, and RequestCycleException is gone
altogether ... 
2) A few classes and interfaces moved from the root package to a subpackage.
3) Some interfaces have changed, but not ones that anyone but the most
bleeding-edge advanced developers will see.

Outside of those changes, NextGen gives without taking away.

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry



> -----Original Message-----
> From: David Solis [mailto:dsolis@legosoft.com.mx] 
> Sent: Tuesday, March 25, 2003 1:11 PM
> To: 'Tapestry users'
> Subject: RE: Tapestry...
> 
> 
> This isn't a complaint. It is a comment.
> 
> We've a messing here:
> 
> We have a couple of systems in production with version 2.1. 
> We're developing the new versions of these systems with 2.3. 
> Recently we deployed a WAP solution with a non official 
> modified 2.4 alpha 1 and last but not least we have other 
> application with 2.4 alpha 4.
> 
> I've a lot of complaints and "enemies" here. Because of new 
> features, I want to port all applications to last version. In 
> addition I'd like to know an expected date to have a 2.4/3.0 
> stable version.
> 
> David
> 
> > -----Original Message-----
> > From: Howard M. Lewis Ship [mailto:hlship@attbi.com]
> > Sent: Tuesday, March 25, 2003 8:07 AM
> > To: 'Tapestry users'; cclunis@yahoo.com
> > Subject: RE: Tapestry...
> > 
> > Thanks.
> > 
> > There are several reasons Tapestry is moving so fast.
> > 
> > I'm on sabbatical from my job to work on Tapestry and the Tapestry
> book.
> > I
> > have a bit over a month to go before returning.  Some things are
> easier
> > when
> > you can work on them well rested, and have a few hours without 
> > interruptions.
> > 
> > The other big reason is philosophical.  Tapestry started 
> from a very 
> > rigid, completely unambiguous core.  You must have an application
> specification.
> > You must list each and every page and component.  Etc., 
> Etc.  In fact, 
> > going back in time, many of the features folks rely on today simple 
> > were
> absent
> > ... like listener methods (you used to have to roll an 
> inner class!).
> > 
> > I think it is much easier to start rigid and relax restrictions than
> to go
> > the other way.  2.4/3.0 is really showing this as all sorts of 
> > restrictions drop away and yet there are no "hacks" coming into the 
> > code (except
> for
> > the
> > JSP support, that's a bit of a hack).  There's no way I 
> could design 
> > something as complex as Tapestry is today, but by getting a 
> good start 
> > (way back in January 2000) Tapestry has had the momentum to 
> get where 
> > it is today.
> > 
> > It's much harder to go the other way; start with hacks and try to
> bring
> > order out of the chaos.
> > 
> > Devil's Advocate: Struts may also be working harder to maintain
> backwards
> > compatibility. I've tended to favor new developers coming into
> Tapestry
> > over
> > established developers when making changes; sometimes a 
> release will 
> > change an API in a non-backwards compatible way.  Of 
> course, most of 
> > the APIs that
> > change are internal, and so, will not affect the majority of users.
> > Haven't
> > heard any complaints!
> > 
> > --
> > Howard M. Lewis Ship
> > Creator, Tapestry: Java Web Components 
> > http://jakarta.apache.org/proposals/tapestry
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Stav [mailto:cclunis@yahoo.com]
> > > Sent: Tuesday, March 25, 2003 8:45 AM
> > > To: Tapestry users
> > > Subject: RE: Tapestry...
> > >
> > >
> > > I have to agree with Howard, Tapestry is advancing
> > > very quickly, sometimes annoyingly so ;o)
> > >
> > > Sometimes it is tough to strike a balance between new 
> features and 
> > > stability.
> > >
> > > Struts for example, has taken over a year to move from 1.0.2 to 
> > > 1.1.x, and it's still in beta!
> > >
> > > It is nice to have full-featured, powerful framework
> > > like Tapestry that is maturing at such a rapid rate.
> > >
> > > I think Howard and his supporting developers are doing
> > > an excellent job. (I don't know where they get the
> > > time!)
> > >
> > > Personally I look forward 2.4 a.k.a 3.0, and Howard's
> > > book with relish.
> > >
> > > Cheers,
> > > Stav.
> > >
> > >
> > > --- "Howard M. Lewis Ship" <hlship@attbi.com> wrote:
> > > > From my point of view, Tapestry is progressing at a blistering
> rate!
> > > >
> > > > Please copy any feature requests you are interested
> > > > in over to BugZilla.
> > > >
> > > > --
> > > > Howard M. Lewis Ship
> > > > Creator, Tapestry: Java Web Components 
> > > > http://jakarta.apache.org/proposals/tapestry
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Programozas [mailto:programozas@hotmail.com]
> > > >
> > > > > Sent: Tuesday, March 04, 2003 3:26 AM
> > > > > To: Tapestry-User
> > > > > Subject: Tapestry...
> > > > >
> > > > >
> > > > > Hello!
> > > > >
> > > > > I'd like to use Tapestry as the framework of our
> > > > complex
> > > > > portal. Tapestry is missing some functionality,
> > > > most of these
> > > > > (for us) important missing functions are submitted
> > > > as feature
> > > > > requests. But I feel that the development has been
> > > > slowed
> > > > > down (correct me if I'm wrong). Is there a real
> > > > chance that
> > > > > the feature requests will be implemented in the
> > > > near future?
> > > > >
> > > > > Thanks,
> > > > > Norbi
> > > > >
> > > >
> > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> tapestry-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: 
> > > > tapestry-user-help@jakarta.apache.org
> > > >
> > >
> > >
> > > __________________________________________________
> > > Do you Yahoo!?
> > > Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your 
> > > desktop! http://platinum.yahoo.com
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: 
> tapestry-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail:
> tapestry-user-help@jakarta.apache.org
> > >
> > >
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: 
> tapestry-user-help@jakarta.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> 
> 


Mime
View raw message