Hi Alex, I think is a good approach. PopUpManager should not be present unless application requeriments needed. As well a more advanced manager like an MDIManager would be required if application is MDI, something that we don't have in Flex 4 out-of-the-box. So maybe Managers could be added as beads at application level so you add as needed.
I think popups should be parented by application by default but could be configured to be parented by some specific view. In this way when using MVC frameworks like Swiz with modules, popups can dispatch events easily that will be managed by application or by a module so beanproviders can break into parts and and each "domain" could handle its events. If there's no event to be managed at that level, it could continue bubbling so it can be handled by other parent and in the end by main application. I think z-order will be managed by the manager using the mark you sugested, and I think it should support grouping or something that could make easy to handle a discrete set of popups. Right now we have PopUpManagerChildList with just 3 preset "spaces" APPLICATION, POPUP and PARENT and although this could work since parent could be the root of a group, I remember to have many problems in the past (I should revise it since maybe it was due to some bugs that could be solved now that we are in Apache). Maybe someone more could add his point of views to this thread so we can complete more info about this? 2013/6/8 Alex Harui <aha...@adobe.com> > Hi Carlos, > > Thanks for bringing this up. The plan is to change the popup > implementation, but it isn't completely settled on how, so any input is > welcome. > > In FlexJS, the Application is not a display object. That's because it > encourages you to separate your views from other code, and because it > didn't make sense to tie the JS Application to <Body>. > > So, generally, you will have a main View. It will not be the SWF root in > AS, and it will probably be the <Body> in JS. My current thinking is that > Popups will just get added to the main view via addToParent() but marked > as a popup. That allows you to plug-in different popupmanagers that > manage child order based on different strategies. Simple apps don't > really need a popupmanager at all unless they have non-modal floating > windows, and simple apps don't have to carry around all the MDI > overlapping windows code either. > > So, I think the View will parent the popup and events will bubble up to > the View. But this is not set in stone yet. Much more prototyping and > input is needed. > > -Alex > > > On 6/7/13 3:08 PM, "Carlos Rovira" <carlosrov...@apache.org> wrote: > > >The thread opened by Peter about Alert, is very interesting since there's > >some question about underlying Popups in actual Flex 4 that I will like to > >see if can be enhanced in FlexJS. Maybe others could thing are ok with > >actual implementation, so for this reason is better to discuss a bit. > > > >One legacy thing about PopUps in Flex that I think should be discussed is > >the location in displaylist tree. Actualy we have sys manager as root and > >the Application and then 1..n popups as childrens. This make difficult > >sometimes to handle events since popups are separated from the application > >that usualy launch it. For example in MVC frameworks like Swiz this break > >general management of events (that use to bubble) since popups does not > >find the dispatcher necessary for your code to work. > > > >Other issue is that actualiy is more easy implement an MDI system in the > >Application layer domain that in Popups zone, but at the price that you > >loose activation/desactivation feature (and it's skin representation). > > > >So what do you think. A new implementation should be in the same tree > >structure pattern or you think this could be changed to other > >implementation? > > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 94 80 80 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
