IMO, MDI is a specific implementation of an "overlapping windows" 
implementation.  In some scenarios (like AIR apps) the true MDI windows 
(equivalent to other top-level windows of other apps) was the AIR NativeWindow 
itself and no ActionScript code managed how those MDI windows behaved.

But even if you try to simulate MDI within a browser window, each MDI window 
might itself have a stack of popups and z-order and focus/activation have to be 
managed within that window.  So there are lots of possible PAYG 
implementations, IMO.  It shouldn't take much code to just handle someone's 
"Find" dialog, but it was a fair amount of code to do what Flex did and divide 
SystemManager into normal, popup, tooltip, and cursor layers.

This will probably be DAYG (Do As You Go).  We'll figure out some 
implementation when someone actually needs it.

My 2 cents,
-Alex

On 1/16/19, 12:44 AM, "Carlos Rovira" <[email protected]> wrote:

    Ok,
    
    I always refer to that concept as MDII (Multiple Document Interface). And
    in Flex we had external MDI library to do that. For me that's a concrete
    case and people that wants to do MDI should start that effort and make a
    new library. So IMO we should start to that need to invest time in this.
    
    Regarding zindexes, in Jewel I put things on some concrete index but I as
    well thinked that I should define a range, but still didn't. For now seems
    not urgent, but I remember in Flex at some point was needed (and was in
    that MDI app we did).
    
    
    
    El mié., 16 ene. 2019 a las 8:54, Harbs (<[email protected]>) escribió:
    
    > Sure.
    >
    > All I was saying with the z-indexes is that it makes sense to stick to
    > some conventions when implementing different beads/managers so they play
    > nicely with each other.
    >
    > > On Jan 16, 2019, at 8:41 AM, Alex Harui <[email protected]>
    > wrote:
    > >
    > > Royale offers choices.  For PAYG reasons we probably wouldn't want to
    > implement only the "ultimate floating window manager".  There are 
different
    > strategies as to what goes on top and when (on mouseDown or mouseUp).
    > Modal dialogs can have popups and float stuff over them if they want.
    > >
    > > My 2 cents,
    > > -Alex
    > >
    > > On 1/15/19, 10:13 PM, "Harbs" <[email protected]> wrote:
    > >
    > >    Floating windows could probably be handled pretty easily by changing
    > the z-index on each of the popups (in HTML).
    > >
    > >    Of course you’d need a manager to handle that, but it shouldn’t be
    > too hard to implement.
    > >
    > >    That would probably be either a FloatingWindowManager singleton or
    > FloatingWindowUtils static class.
    > >
    > >    We probably want to standardize on different number ranges of z-index
    > for different “classes” of floating things.
    > >
    > >    I imagine modal dialogs would have the highest z-index. The possible
    > exception to that would be popup menus. Floating windows somewhat lower
    > than modal dialogs, etc.
    > >
    > >> On Jan 16, 2019, at 2:39 AM, Alex Harui <[email protected]>
    > wrote:
    > >>
    > >>
    > >>
    > >> On 1/15/19, 2:48 PM, "Carlos Rovira" <[email protected]> wrote:
    > >>
    > >>>
    > >>> Support for "overlapping windows" would be PAYG and added via some
    > other
    > >>> classes.  I don't think we've done anything there at the Basic level,
    > the
    > >>> emulation components may have to support it since Flex did.
    > >>>
    > >>
    > >>   What do you mean with "overlapping windows". Don't understand that
    > concept.
    > >>   For me windows are always one on top of another...
    > >>
    > >> Oh yeah, forgot to describe that.  "overlapping windows" means that two
    > or more popups can be visible and potentially overlap each other based on
    > which one was clicked on last.  In some IDEs you can have all of these
    > floating panels.    Spell-check and Find dialogs are other examples where
    > they can be popped up and not dismissed while some other popup or dropdown
    > shows up and has to show up above or under the floating Spell-Check or 
Find
    > dialog.
    > >>
    > >> Flex had a whole ActiveWindowManager that worked with the
    > PopUpManager.  Royale should try to make support for floating dialogs 
PAYG.
    > >>
    > >> Thanks,
    > >> -Alex
    > >>
    > >
    > >
    > >
    >
    >
    
    -- 
    Carlos Rovira
    
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&amp;data=02%7C01%7Caharui%40adobe.com%7C89b73a6569614a4cfa5608d67b8ec6bf%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636832250487144183&amp;sdata=SqCecW%2B%2FI9WzjTOMQQxuWZCn1T0TzkwXORYYCbtHiaA%3D&amp;reserved=0
    

Reply via email to