Re: Panes vs. Separate Windows
Re: Panes vs. Separate Windows
- Subject: Re: Panes vs. Separate Windows
- From: Alex Zavatone <email@hidden>
- Date: Mon, 11 Jan 2016 11:06:35 -0500
On Jan 11, 2016, at 2:17 AM, Britt Durbrow wrote:
> My preference would be multiple windows (one primary document window and several utility panel windows) that can be snapped into place against each other. This gives the freedom to use multiple monitors while also having the screen-real-estate efficiency that a single-window approach would. (FWIW, I’m typing this on a 27” 2560x1440 Acer LCD connected to a 13” Retina MBP; both displays are active at the moment).
>
> I find that as the problem space that the app is trying to solve becomes more complex, the all-in-one approach that is being pushed by the “full-screen-window” model gets too inflexible.
Back when Macromedia tried to do this what I noticed was that there never is a perfect fit when trying to force everything into one window. There always is unused space or not enough space.
Xcode seems to do a pretty good job with this, in its layout but I always end up with as many windows as I want and just command ~ or command-shift ~ through them to get to the ones that I set up the way I want.
But the joy of setting up multiple inspectors or a shared inspector is restoring the shared inspector to what the user set it to and where they positioned it whenever the user changes the source of the inspector.
It always ends up being quite annoying when you set up your inspector position, then switch to something else, resize the inspector and reposition it and then go back to your other source and find that the inspector doesn't remember the position you had put it in.
Lovely little details.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden