I think thats a fair comment. Even so, making upgrading easy is just a
question of making the proper tools.
Regardless of Howards sceptism, I don't see how an easy upgrade path
could not be implemented.
Rather than hope for upgrade tools to eventually surface, I think we need to
make
those tools available together with
ver 5 from day one.
Anyway I think we will need the version 4 branch for quite a while to
support JDK
1.3 & 1.4
Henrik
----- Original Message -----
From: "James Carman" <[EMAIL PROTECTED]>
To: "'Tapestry development'" <dev@tapestry.apache.org>
Sent: Friday, July 28, 2006 7:34 PM
Subject: RE: Tapestry 5 Discussions
Howard, I know you're very innovative and all, but doesn't this really sound
somewhat crazy to you? If you really want Tapestry to gain acceptance, then
backward compatibility is a big issue. I jumped into the Tapestry world
with the 4.0 release and I'm really enjoying it, but if switching to 5.x is
going to be "VERY difficult", then I don't know if I'll ever upgrade.
Tapestry is definitely (IMHO) very superior to the "standard" JSF, but if it
keeps becoming a "moving target", then it will never gain market acceptance.
The big wigs will win out because they support a "standard." If Tapestry
has the reputation of becoming the "consultant's framework" (as has been
said in the past) because it requires so much work to upgrade, then it's
going to suffer. It's not that I disagree with the direction you're
heading. It's that I don't know whether or not changing paradigms so
drastically is a good idea for the health of the "product" or "brand."
I agree so far with what you're doing. I don't like the fact that you're
switching from HiveMind to TapIoCa (that's my little nickname for the
Tapestry IoC container), but if you don't want to be tied to HiveMind or
don't want to be constrained by the release schedule, then I understand
(although you're a big part of the HiveMind community and we can easily
accommodate any changes you could need IMHO). Anyway, this is your baby,
but if you want to gain some market share, then you should really listen to
your users. Tapestry is starting to get a bad reputation for not supporting
backward compatibility. Again, I think the direction you're heading is a
good one, if you don't have to consider your current users, but we don't
have that luxury.
-----Original Message-----
From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
Sent: Friday, July 28, 2006 12:09 PM
To: Tapestry development
Subject: Re: Tapestry 5 Discussions
Right now its impossible because there's nothing to convert to :-)
It will be *VERY* difficult. This isn't a slap of new paint. Basic
paradigms are shifting around in a major way. It would be comparable,
or perhaps even larger than, converting between JSF and Tapestry 4.
Possibly on the order of converting from Struts to Tapestry 4.
On 7/27/06, Norbert Sándor <[EMAIL PROTECTED]> wrote:
I know that it's far away, but how easy/difficult will it be to convert
an application from 4 to 5?
Regards,
Norbi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
