Apologies in advance as I'm a newbie harking on about my pet topic again but...
Taking the example of TabbedPanel and AjaxTabbedPanel (only in extensions but a common UI concept) I think it shows why it would be good to use the factory pattern to generate elemental widgets (like button, panel etc assuming people want AjaxFallbackButton or Button) and automatically track dirty components. I first got this bee in my bonnet about higher level application code because I didn't think I should be messing about working out which components were dirty when I just want the result of pressing a button to fiddle with the model and change the ui state a bit. However looking at *TabbedPanel I think it would also make sense for pure UI components. Using inheritance to add Ajax to TabbedPanel means any other variations also have to be doubled (e.g. AjaxFancyTabbedPanel and FancyTabbedPanel etc). Perhaps the bigger problem is that if a Panel that is meant to be inside a TabbedPanel and needs to alter another component (e.g. update navigation component) the TabbedPanel has to ask it for changes. Presumably a component should be self contained as possible so it doesn't matter what other component it is contained within. Factory pattern is a pain but presumably many people don't want the overhead of AjaxFallbackXXX. It would also make it possible to program against interfaces which might give more power to Igor, Eelco etc Please don't get me wrong GWT is still my true love but Wicket is a fabulous framework taking us out of the dark ages of struts. -- View this message in context: http://www.nabble.com/auto-dirty-and-widget-factory-tf4421187.html#a12610663 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
