Hi,
Yes I agree, first I thought thats the way to go, but it is an all of
nothing approach, which is way to heavy for example field keypressed
ajax-invokes...
Johan suggested today if we always do an ajax-renderPhase after an
ajax-invoke we might want to introduce ajaxInvalidate() method on
components to optimize the ajax-renderPhase which visits(check for
changes) the invalid components or all if ajaxInvalidate() on the page
is called. This way the developer is in control of how extensive the
Ajax render phase is.
Regards Jan Blok
Eelco Hillenius wrote:
One addition... though I think 3) would still be the easiest way, I am
no longer convinced it is the best way. It is just too brute force.
Eelco
Jan Blok wrote:
From the threads/Wiki/discussions we now have 3 ideas/strategies to
do AJAX in a generic manner:
1) partial re-rendering of page when Ajax invoke is done (Chris)
2) JavaScript lib which renders components property changes when Ajax
invoke is done (Johan/Jan)
3) full page re render and page difference returning when Ajax invoke
is done (Eelco)
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
