I was quite "afraid" leaving spindle and moving on to tapestry 4 - it is
such a great tool -
but in the time since I addopted some practices which make my life
really not so difficult - so I decided to share them here - maybe the
one or other can benefit:
1. I Start with the html - desing the component roughly.
1.a) in the html I use only jwcid="someComponentId"
1.b) that I shouldn't write, but I write it anyway: use good names and
conventions for component ids : things like "ifUserLoggedIn" and
"iterateItems"
2. I move on to the .jwc/.page
2.a) I use a splitted editor : on top the html, on the bottom the .jwc
(or the other way around ;-) )
2.b) in the jwc/page file I declare all my components, and components
*only*.
2.c) I use all bindings as direct properties, when using ognl, to
minimize the use of reflection. later I can refactor to use HLS's prop:
prefix easily.
3. Now the java class:
3.a) open a splitted editor: on top java, on bottom the jwc, go through
the jwc and resolve all java dependencies, all properties, aso, in order
of apearance.
3.b) use annotations for properties and parameters.
Its somehow doctrine but makes my life very simple...
Hope tat helps until Spindle 4.0 is there :)
Cheers,
Ron
Cui, Fanzhe wrote:
According the Spindle web site, it seems the current version of Spindle
supports Tapestry 3. Does any one if there is new version that supports
Tapestry 4?
Fanz
---------------------------------------------------------------------
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]
