Short answer : You do not have to write a single line of javascriptcode
to use wicket ajax behaviors. This is already done for you.
Regarding browser differences, I belive they are handled(by
wicket-ajax). AFAIK in beta 4 even safari works:)
Chris Colman wrote:
To date we've built all of our static pages in Wicket and all dynamic
pages/user input forms etc., in Echo because it provides a pure Java (no
need to write any JavaScript) solution to generating AJAX powered pages.
The problem is when users switch from Echo pages back to Wicket pages
using the browser's back button (Echo only ever has one URL for all
pages so bookmarkable pages don't exist). They kind of do a "hyperspace"
jump that's not very user friendly. The 'back operation' does not return
them to the previous element in the path of their navigation through the
Echo based portion of the application but instead returns to them to the
last non echo 'page' that they were on. Echo is very cool and very fast
to develop in but this one issue is causing us some grief.
I'm contemplating implementing the dynamic pages in Wicket instead of
Echo but have a few questions:
1. Will I have to write any Javascript to implement AJAX powered pages
(I'm a Java programmer of 12 years and don't want to get down an dirty
with the browser/JavaScript ever again - tried that in about 2002 and it
was very painful).
2. Can AJAX powered pages be generated by Wicket in such as way that
browser differences are accommodated automatically by the Wicket
framework - ie., transparent to the developer?
These two issues are why I chose Echo (all AJAX is done transparently to
the developer) in the first place but if Wicket covers these issues
satisfactorily then I could move the app to 100% Wicket.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
