Gernot Stocker <gernot.stocker <at> tugraz.at> writes:
>On the first hand, that migration from 4.0.2 to 4.1
is smoothly
> possible (are there any hints or special
considerations for the migration?)
Gernot,
As a matter of fact, I have spent (a bit of) time
looking into the 4.1.x as well as 5.x branches.
It appears that I have refactored my code to only declare
components in HTML templates and *not* in component/page
files (ie. .jwc and .page). My jwc and page files are now
as lightweight as possible.
The most painful thing is the upgrade of:
- If, Else and For components because of the renderTag=true
by default (but it can be disabled, see the 4.1 component
docs for it)
- My own little Javascript : I basically had to refactor
my (crappy anyway) codeand change my references to id'ed
elements from document.getElementById('${id}') to
dojo.byId('${id}')
- By chance, I had not used tacos except from the Tree
components, and I did not have to replace AjaxForm by Form
and other components as well. Advice from Andy were precious
because we knew beforehand that these components would be
base components of Tapestry 4.1.x.
And I have 100+ components! The only "hole" at the moment
is for the tacos:Tree, as well as the use of deprecated
components (Form related components in contrib:TableXXX)
which are not removed yet.
I still have to assess the Drag'n drop functionality.
That's it for my experience. Ajax is really easy to setup
(fantastic work by Jesse and Andy, and maybe others, sorry)
as long as you know how Tapestry works (rewind cycle,
sequence of rendering, but that was true before 4.1)
Hope you enjoy 4.1,
Thanks to all contributors,
K.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
