Re: Panes vs. Separate Windows
Re: Panes vs. Separate Windows
- Subject: Re: Panes vs. Separate Windows
- From: Jim Lee <email@hidden>
- Date: Mon, 11 Jan 2016 10:35:25 -0500
We have an application, TopXNotes that allows multiple “documents” (notes) to be opened in adjacent views (panes). The notes can be edited individually. One can cut/paste/copy from any text document to/from a seperate text app, or from pane to pane. Just one example of something different that I hope fits into the parameters of this discussion. TopXNotes 2 (now in beta) adds “Open in Seperate Window” as an option that addresses that “best of both worlds" concept.
Personally, I have never lilked the way Photoshop implements their extra panes because I have never been a fan of the inspector, but that is just me. On the other hand, I like the way Apple has implemented its multiple views approach in Xcode. Before apple did that there were just way too many windows jumping around and opening in seeming random oirder at random times. Now I get some CUI as things appear almost always where expected.
Having stated my opinion, we did add one inspector-like Info pane as a separate window to TopXNotes.
Anyone who would liek a copy of TopXNotes 1 or the 2.- beta when it is redy (soon) please feel free to contact me. I would value feedback that we might be able to use for the next version. Along those lines there is a free download of the trial version. I am not posting a link because it might not be kosher, but I hope this is OK to discuss here.
Cheers,
Cheers,
James Lee
> On Jan 11, 2016, at 7:45 AM, Charles Jenkins <email@hidden> wrote:
>
> Interesting that so many others like the multiwindow approach. I’ve always thought that a horrible design, because you constantly have to fool with them to get them out of the way as you work on a document. I like the approach taken by Photoshop, where you can dock them them together in the layout that’s most effective for you, then mark some columns as being pinned open while others can collapse when not in use.
>
> I have Photoshop 5.5 or 6 and love the interface, but because I didn’t want to subscribe to Creative Cloud, I try to do photo stuff in other programs as much as possible—to get comfortable with other products so it’s not tempting to use PS every time. Initially I tried to do as much as possible in Pixelmator, but having tool windows scattered all over the place drove me crazy; now I’m using Affinity Photo, and the docked toolwindows are a major reason why.
>
> --
>
> Charles
>
> On January 9, 2016 at 17:21:14, Rick Mann (email@hidden) wrote:
>
> In complex apps (e.g. CAD apps, IDEs) a given document has many auxiliary windows. The trend in UI at Apple has been to consolidate these into panes in a single window. I've always preferred separate windows (e.g. separate toolbar window).
>
> One more concrete example is in a CAD program: the objects in the document are often related to each other hierarchically. There's usually a view of this hierarchy using something like an outline table. I can see this naturally fitting as either a pane in a split view, or as a separate window. Best of both worlds, I suppose, would be a dockable window (a window that can be separate, or live as a pane in a split view), but that might be a lot of additional coding (is there a nice library that offers this?).
>
> Complicating matters is whether or not each open document shares a single instance of these auxiliary windows or has its own. I think something like a tool palette is clearly shared (it's more app-global then per-document), but the model object hierarchy window is probably per-document.f
>
> Separate windows have tremendous advantages, but I think panes are considered more "simple." Simplicity has advantages, but we're talking about complex apps that by their nature demand more of their users than something like iPhoto.
>
> Thoughts?
>
>
> --
> Rick Mann
> email@hidden
>
>
>
> _______________________________________________
>
> 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
> _______________________________________________
>
> 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
_______________________________________________
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