On 11/16/16, 10:06 AM, "Yishay Weiss" <yishayj...@hotmail.com> wrote:
>Hi Alex, > > > >Accordion, as I wrote it, will not function properly without some >mechanism for collapsing items. This code calls get >accordionCollapseBead() which searches for beads that implement >ICollapseBead, either in the beads collection or in CSS. It’s similar to >the way UIBase initializes models, views, and controllers. > > > >What dependencies are you worried about? It looked like a way to generate a dependency rather than a getter call. I'm hoping that effects for component transitions can be implemented by intercepting events. In theory, an Accordion should just send out a "change" event that its selectedIndex changed and the AccordionView should cause the affected child views to either resize or change visibility. An effects bead should be watching each child view for a resize or show/hide event, reset the size or visibility, then apply the appropriate effect. This is all theory, of course. In might require "pre" events like an "aboutToResize" or "aboutToHide" that can be cancelled if you get flickering. IOW, the basic implementations should not assume there are an effects and just instantaneously change the view. But a bead should be able to alter that without any tight coupling other than events (or some sort of notification). My 2 cents, -Alex
