, or am I on the wrong track ?
I am very new to tapestry (first week), so any pointers will be appreciated.
--Thanks.
--
View this message in context:
http://www.nabble.com/Best-strategy-to-do-custom-server-side-validations-and-add-errors-tf4760676.html#a13614831
Sent from the Tapestry - User
(stuff like ADD or DELETE or
EDIT).
--
View this message in context: http://www.nabble.com/Best-strategy--
tf3201900.html#a8959162
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
Julian Wood [EMAIL PROTECTED]
Software Engineer
Teaching Learning Centre
University
Damn!
Just reading about that T5 Table gives let's me wishing I could fast forward
time to let Howard finish and release it!
Just seams a waste of time to develop a grid for T4 that is will no even get
close to what Howard describes for a few months life-time...
Oh well...
On 2/14/07, Julian
so on PHP. The javascript has many event hooks which
fire off AJAX requests to it's PHP backend.
My question is, what is the best strategy for moving to Tapestry?
I think the quickest and dirtiest solution is to create an engine
service for each of the AJAX calls, which replicate what the PHP
. It is heavy on javascript, AJAX and
somewhat less so on PHP. The javascript has many event hooks which
fire off AJAX requests to it's PHP backend.
My question is, what is the best strategy for moving to Tapestry?
I think the quickest and dirtiest solution is to create an engine
service
Yes that is a nice table, but I think you could do all that (minus
the AJAX) with some CSS around the current contrib:table.
Tap 5 has a new grid component you might be interested in:
http://tapestryjava.blogspot.com/2007/02/more-tapestry-5-grid-
component-case.html#links
I haven't tried
Either way you want to use FilteringTable not Sortable. (sortable is
the old version)
On 2/13/07, Julian Wood [EMAIL PROTECTED] wrote:
Yes that is a nice table, but I think you could do all that (minus
the AJAX) with some CSS around the current contrib:table.
Tap 5 has a new grid component you
://www.nabble.com/Best-strategy--tf3201900.html#a8959162
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
2007 00:58
An: Tapestry users
Betreff: Re: Best strategy?
Ok thanks Jesse. Even hearing that it _is_ a large undertaking gives me some
direction. I think I will explore the EventListener annotation a little more to
see if I can see a way to hook it up to the events created by this planner
.
-Ursprüngliche Nachricht-
Von: Julian Wood [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 12. Februar 2007 00:58
An: Tapestry users
Betreff: Re: Best strategy?
Ok thanks Jesse. Even hearing that it _is_ a large undertaking gives me some
direction. I think I will explore the EventListener
://www.dhtmlgoodies.com/scripts/dhtmlgoodies-week-planner/
dhtmlgoodies-week-planner.html
and moving it into tapestry. It is heavy on javascript, AJAX and
somewhat less so on PHP. The javascript has many event hooks which
fire off AJAX requests to it's PHP backend.
My question is, what is the best strategy
requests to it's PHP backend.
My question is, what is the best strategy for moving to Tapestry?
I think the quickest and dirtiest solution is to create an engine
service for each of the AJAX calls, which replicate what the PHP does
in it's current incarnation. This does feel like the wrong
12 matches
Mail list logo