Most programmers would like us to have some form of auto-update components.
I can imagine that we provide an Ajax enabled PagingNavigator, which updates itself and the Pageable component it directs.
Wicket can update multiple components in one request. There is currently no library that supports this, other than through _javascript_ evaluation.
I think Wicket can provide a basic mechanism without visual effects (the Scriptaculous, Dojo, MooFx and Rico maintainers are much better at that) that allows us to update components using Ajax and not having to use Prototype, Dojo, etc.
Martijn
On 1/31/06, karthik Guru <[EMAIL PROTECTED]> wrote:
Just a general question -
What does it really mean when somebody says that a framework needs to
have ajax support baked in?
- Now we have a Listener and components that responds to Ajax requests,
- The framework allows you to add Ajax behaviour as needed and does not
impose it by default.
- There are ways to add contributions to the header/body..although not perfect.
- Allows you to integrate different _javascript_ libraries.
What else s'd a framework provide?
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
Living a wicket life...
Martijn Dashorst - http://www.jroller.com/page/dashorst
Wicket 1.1.1 is out: http://wicket.sourceforge.net/wicket-1.1
