Thanks Eelco, It is mainly navigation logic and I think its state can quite happily live in the components...
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. So at least my application code does not see the gory details of Ajax, code handlers only once and changes get cascaded... Anyway, I'll see if I can manage without setEnabled, setVisible, add, addOrReplace etc not being final... 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. -- View this message in context: http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12483783 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
