• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Panes vs. Separate Windows
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Panes vs. Separate Windows


  • Subject: Re: Panes vs. Separate Windows
  • From: Ariel Feinerman <email@hidden>
  • Date: Fri, 17 Feb 2017 18:11:05 +0000

I am glad to know that a lot of people still like multiple windowed UI and
remember Xcode 3 with warm like me. Of course, it is more suitable for
using multiple screens: one window for each screen, or in the case of CAD
-- one screen for model designing window and one for everything else.
However, I should say that we fell into the  other problem: how to separate
windows from several opened projects when we need?


On Wed, Jan 13, 2016 at 7:00 PM, Dave <email@hidden> wrote:

>
> > On 11 Jan 2016, at 23:10, Charles Srstka <email@hidden>
> wrote:
> >
> > My favorite thing in Xcode is the way that Interface Builder stuffs the
> entire object library into that tiny little space in the lower-right corner
> of the screen. Way back in Xcode 3 (or whenever it was that IB was a
> separate app), the floating palette that they had for the object library
> let you browse through the UI elements, see what was there, and discover
> new widgets as they were added to new OS releases. They were even grouped
> into categories, if I’m remembering correctly. Now? Searching for the
> element you want is the only halfway effective way to use it at all. And
> then, of course, if you have it visible at all, it clutters up your code
> editor when you switch to a source file.
>
> Yes, it’s IB that is the most out of place being made to fit in with a UI
> design that just doesn’t suit this style of tool. The situation is even
> worse now we have auto layout. Its obvious to be anyway that IB really does
> need to implemented using specialised windows designed specially towards UI
> layout, not forced into a bloated out window that is designed around
> editing, maintaining and compiling source files and managing project
> settings.
>
> Dave
>
> _______________________________________________
>
> 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
>



--
best regards
Ariel
_______________________________________________

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


  • Prev by Date: Re: Some help with NSComparisonPredicate please
  • Next by Date: A horizontal line rule within a NSAttributedString?
  • Previous by thread: Re: Can't restore first responder when restoring window state
  • Next by thread: A horizontal line rule within a NSAttributedString?
  • Index(es):
    • Date
    • Thread