Just hypothetically, what's the possibility of throwing it all away and
just include an integration layer with the old components / pages?
It may be cheaper that evolving? Is it possible?
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Howard Lewis Ship wrote:
This is the direction I'm looking to evolve the framework.
This will start being easier in 4.1. I'll be able to seperate user
code from framework code since user code will no longer extend from
Tapestry base classes (a compatibility layer will remain until 4.2 or
4.3).
Right now, Tapestry code and user code gets too involved with each
other via inheritance, makes it hard to seperate. I really want there
to be a much more minimal API, a stable SPI, and more internal ocde
that is free to change at any time.
If I started a new Tapestry from scratch, you can imagine all this as
day-1. It's much harder to evolve release by release than to throw it
all away. I still think we can get there, eventually. The new
infrastructure in 4.0 is making this trend much easier.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
