I started doing the migration of a web site a few days ago.
the very first impression is that many things must be changed or modified.
I need to learn a lot of new stuff: usually this is something I like,
but it requires time, which is something I don't have now.
I don't know anything about hivemind, how it is integrated, I would
like to understand all new "best practices", I need to understand the
new components parameters directions, the use of annotation, and so
on: it's going to be for me a big task.
Another impression I had is that the start up time has considerably
increased, but may be this is only a problem of my configuration.

I think I will migrate anyway, because tap4 is the future, tap3 will
be longer developed, and all the new components will be developed for
tap4.

I would really like to see tapestry stabilize now and concentrate on
the realization of components: I think it is very important for its
adoption to have a stable API with not so big changes between releases
and a rich set of components, which is what can attract new users.

Anyway, a big thanks to Howard and all the development team!!

Just my 2 euro cents.

Enrico


On 19/10/05, Patrick Casey <[EMAIL PROTECTED]> wrote:
>
>
>             I've been reading these lists (and looking through the doc and
> change notes) for 4.0 for long enough to see that Tapestry 4.0 is a *big*
> change in the way a lot of things work. Lots of stuff is getting deprecated,
> some things are apparently just going away and, equally importantly, the
> preferred way to do a lot of things is being changed pretty dramatically.
>
>
>
>             With that being said, is there a compelling case to upgrade an
> existing Tapestry 3.0.3 project to Tapestry 4.0? I'm not talking about a
> fresh project starting form line one, but rather an extensive, large and
> complex 3.0.3 application. My gut feel is that any upgrade is going to end
> up being close to a reimplementation; is that true? Has anyone tried porting
> a non-trivial 3.0.3 app to 4.0?
>
>
>
>             I'm worried that I won't be able to port to 4.0 and, in doing
> so, I'll be stuck on an orphan branch of the source tree :-(.
>
>
>
>             --- Pat
>
>
>


--

Enrico Donelli
http://www.enricod.it

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to