most db driven models don't know if they are dirty or not
For this kind of thing the developer itself can say invalidate youreself (the component or maybe say it to the model) and render again.
Because i know or think you are changed.

You also have non db models (the non detachable once) and that one can set the dirty flag by firing a property change where the components who has
that model are setting the dirty flag)

then the question is should there be some automatic part where wicket as a framework guesses now it is time to do the complete page render
or this component (that is backup by a database/detachable model) render.

johan


Martijn Dashorst wrote:
I don't know whether it is a good idea, but adding a marker interface (AARGH I said the I-word ;-), to a/the models in order to make them Ajaxian? This way Wicket can check whether the models allow for dirty bit checking. By supplying an AjaxDirtyModelExpansion class, users can delegate to that model.

Or allow observers to attach themselves to the models.

Martijn


Eelco Hillenius wrote:

I guess you mean dirty by invalid?

To make a start somewhere, how should our observer-enhanced models and components look like? That's the first part we need for components to be able to regconize that they are 'dirty' and thus should be rendered the next (ajax) request.

Eelco


Jan Blok wrote:

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





-------------------------------------------------------
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



-------------------------------------------------------
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

Reply via email to