On Fri, Feb 25, 2011 at 20:23, Josh Canfield <joshcanfi...@gmail.com> wrote: >> They wouldn't see the difference - they'd be using the component that >> would internally >> use the mixin > > Actually, I wasn't thinking of an internal mixin. Putting a "zone" on > the Select seems random, making it an internal mixin doesn't make it > any less random.
What is an internal mixin? It needs to be a normal, public mixin for users to use anywhere (most likely it should be a copy of zoneupdater). And it needs to be attached to Select by default due to backwards compatibility - if that's not a requirement, then i fully agree with you. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
