On Nov 2, 2014, at 16:23 , Luther Baker <lutherba...@gmail.com> wrote: > > Is Xcode worth considering here? Tap a class file and you get details about > that class in the right pane. Open a XIB ... Tap something in the XIB and the > details pane changes to reflect the XIB selection, not the file anymore. Same > goes for core data modeling while creating entities. > > Does that not demonstrate a potentially fine way to build user facing > software?
What Xcode does kinda sucks. Did you notice that Xcode 6 introduce *two* highlight states into the navigator pane, just to resolve the sorts of ambiguities Graham mentioned? Suddenly, things get twice as complicated (in terms of working out what you’re looking at), and it doesn’t really solve the problem anyway. For example, if you click on the “other” highlighted item to get back its editor, you’ll usually start editing the file name accidentally. Also, your original plan breaks down when using the keyboard. Pressing Tab will change the item that’s controlling the detail view, but the think you tab to might not be your final destination. In your scheme, therefore, some state changes are not possible via the keyboard. You’re better off doing something simpleminded, such as: — Put a pushbutton in each outline list row, which causes the corresponding detail to appear — Put a pushbutton at the bottom of each outline list, which causes the detail corresponding to the selected list item to be displayed — Put a checkbox (which doesn’t have to look like a standard checkbox) in each list row, and coordinate the states between the items and lists. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
