> It seems there is more than one way to skin this cat. I'm really looking > forward to Wicket in Action.
Working on it as we speak :) > I'm hoping that besides acting as a great > reference, it will be great at explaining the "intent" of the design of the > APIs so that end users can make correct design decisions. We're trying to do that, but it will be hard to get all the nitty gritty details in. There's a lot of stuff to cover. > Igor's correction > is a perfect example. Why is it better to use " > response.renderOnLoadJavascript()" versus overriding onRendered()? rederOnLoadJavascript nicely add the script to a routine that will be executed after the whole page is loaded. It will also look better in the source of your page. Finally, I'm not sure how onRendered would behave it the component was added through Ajax. Maybe Igor can clarify whether that would make a difference. > Anyhoo, I'm enjoying using Wicket. Thanks to all the developers for their > hard work. Good to hear. Have fun! Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
