> But most probably Checkbox and Radio will have the same initialization.
Radio is more complicated and needs more code because of IE change event bug, also it would be nice to have a zone parameter on RadioGroup. I can't understand why anyone would want a mixin in this case, it can't be reused for other components and tapestry users will probably look for a zone parameter on the Checkbox component rather than studing all mixins. Denis On Aug 12, 2011, at 5:37 PM, Thiago H. de Paula Figueiredo wrote: > On Fri, 12 Aug 2011 06:03:38 -0300, Denis Stepanov <[email protected]> > wrote: > >>>> Perhaps the patch should be to make select component do it as a mixin ;) >> >> I don't want to break backwards compatibility, > > Nor we. > >> Select nad Checkbox component need to have different JS init and onChange >> method, I don't see any advantage of using mixin here. > > But most probably Checkbox and Radio will have the same initialization. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
