Re: woo




> One problem with this is that you still need to deactivate the last
> active component, and that requires keeping some container-global
> state, which can't be wrapped for the user very nicely.  And basically
> I think that hiding half of the functionality from the user while
> leaving some key component up to him to implement is a terrible
> decision.  I'd rather leave it all to him, and provide nice reference
> code, and a clear interface.

Good point.

Miguel.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]