> I have the habit of having a fixUpTheStateOfThisWidget method (real name > changed to protect the guilty) that I'm starting to wonder if I can hook > this into marking components as dirty. So maybe I can get away with explicit > marking of components as dirty.
Or e.g. work with bean properties and use property change listeners. > Perhaps coming from GWT I imagined Wicket would magically handle all the > state changes for me. All the AjaxTarget stuff seems very low level for > writing user interfaces. Yeah. Thing is that everything in Wicket works automatically for normal processing. Since GWT is Ajax only, and they 'own' everything that happens in the browser, they can do that. The way Ajax with Wicket currently works is very flexible etc, but agreed requires more hand work. It's not a static framework though. We're always on the lookout for improving things, and this might be an area for that. You could open a JIRA issue (feature request) for it so that we make this discussion more persistent. And of course, please share any insights you might develop while working on this. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
