|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
Greg Guerin wrote:
Jeremy E. Denton wrote:
I don't think we can solve the layering issue, which continues in my mind to be a significantly lesser issue than not being able to exploit two monitors in MDIs.
I'm getting confused about exactly what issues you're referring to. Do you
mean issues in general MDI usage now obtainable with Swing, or are you
referring to issues with your proposal?
That is, does Swing currently prohibit you from using JDesktopPane and JInternalFrame inside a frame that spans multiple monitors?
I would think that such an implementation of the MDI interface embodied in JDesktopPane would not be of general utility, but only as a porting aide for apps that use this MDI metaphor to be Windows-like under Windows (although I do see more Windows apps going to full-fledged independent windows, forgoing this paradigm).
As a porting tool, it would be an effective way to get a Mac-like MDI without a major refactoring of an existing app. However, to do it right (in developing a new app, for instance) the MDI paradigm would best be encapsulated in a class or framework which then delegates to either a JDestopPane/JInternalFrame set, or to independent JFrames. You'd also need to watch out for JOptionPane's internal dialog methods, and encapsulate them, too.
What is the best approach in one situation may not be practical (or desirable) in another.
Personally, I hate the JDesktopPane/JInternalFrame paradigm for MDI, and would love to see it scrapped. However, that may just be cultural bias (I was raised on Mac and X11 GUIs). _______________________________________________ Do not post admin requests to the list. They will be ignored. Java-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.