Interesting blog concerning AJAX:
http://www.theserverside.com/blogs/thread.tss?thread_id=35170
Martijn
Eelco Hillenius wrote:
So, I think we all agree that pimping up our models with an observer
pattern and decoupling the rendering process more to be able to render
just some components instead of the whole page is the way to go here.
Who wants to build it? I'm quite bussy with other Wicket stuff, like
the bean panel and - when there is ever a quit evening on the mailing
list - starting up the portal integration thing.
Done (at least the draf) is the ajax handler stuff. To be done:
- implement the model observer pattern;
- implement a mechanism that allows components to indicate that they
are 'dirty'/ should be re-rendered;
- decouple the current rendering process so that components can be
rendered on their own;
- implement a render collection mechanism e.g. in the abstract ajax
handler class. implement making a message of it, sending that message
back to the client, and implement applying the changes to the page.
Volunteers?
Eelco
Chris Turner wrote:
Yes, I agree about attaching AJAX handlers to the components. These
handlers should then be able to access the nodel of the specific
component and all other components on the page. The handler can then
cause model changes, detect external model changes or alter the
hierarchy. What we then do is rather than render the whole page
agaiin, we just visit each component, ask it if it needs to rerender
and then return the new html portion within the AJAX response.
regards,
Chris
Eelco Hillenius wrote:
Why do request handler need to be more intelligent than existing
event handlers - they are doing exactly the same thing: reacting to
events. Where the added complexity comes in is in the model objects
as these need someone waht to support change detection.
If rendering would not change, and would thus still be the
responsibility of the component, it wouldn't be the problem I meant.
Yes, we must only have one component tree. However, what we need to
do is AJAX enable the existing components rather than have AJAX
alternatives.
Not sure if I understand what you mean. Why I think it is usefull to
be able to attach ajax handlers to components instead of building it
in, is that it is a matter of combining. E.g. in one case, you like
to check the validity of a TextField on an onchange, but in another
case, you might want to do a lookup of and render another component
(like an address lookup) on TextField's onchange. So the components
stay the same, but the wanted ajax behaviour can vary.
Cheers,
Eelco
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar
happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in
dual
core and dual graphics technology at this free one hour event hosted
by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar
happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted
by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar
happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted
by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
