![]() If I position the window against one side or another of my screen, I can't see the drawers that's a problem. The new setup, you can see everything at once, if you open the gull-wing drawers. Things were organized cleanly, even if you couldn't see everything at once. *Starfish used to have a most-excellent tabbed UI. While I generally agree that drawers are **way** overused, I think having controls in drawers is acceptable for non-essential controls in one-and-only-one window apps (like Starfish - I agree its UI could be better, but I don't think it's due to the drawers.) If having controls in drawers is the alternative to having a separate inspector window to contain them, I'll take the drawer. That is so unlike the Cocoa equivalent of a Zen master that you normally appear to be. At the beginning, it was just enough to get the damn thing working.īut please stop sputtering. It is certainly true that a tabbed view with one tab for the controls will take care of this in an exactly equivalent (no, a superior) manner.īut a toolbar with a dozen text fields would be kind of an abomination.ĭon't know why I got fixated on drawers for controls. The (somewhat mathematical) drawing routine requires a healthy set of parameters entered from text fields, which I have tucked away in a (now severely-deprecated, but solitary) drawer.įortunately for the shareware community, I have not inflicted this on the public as yet. One of them is a visual app (not document-based) that draws in the entirety of the window's content area. This forces me reconsider the way I am designing a couple of my own UIs. I cleaned out the suggestion about using drawers in the other discussion. Use drawers for what they're intended for - a way to organize lists of data that's directly related to the main content viewer. Or use smaller controls, menu items, customized widgets, etc. If they're just controls, use a tab view or a button bar. If you're just trying to create more space for your clutter, like that junk drawer in the kitchen, find a different way to organize your UI. The next time you consider using a Drawer, stop and think about it. Click on a project's Build Styles tab and you'll get a drawer - this drawer is again similar to the Mail / iChat interface: a list of categories you can click on to refocus the main viewer. But Xcode seems to be moving away from that decision, since they now allow GDB to run in its own window. well now, I don't think Safari uses Drawers at all! It uses a variety of interesting ways to store auxilliary controls, including using items in the main menu. Safari has lots of auxilliary controls, right? So let's see. The important thing is these are *lists* that the user is meant to drag things into/outof - hey, kinda like Mail. I suppose you could claim a list of people is an auxilliary control, but that's wrong. ![]() Look at iChat's use of Drawers: identifying the List of people in the current chat defining groups (lists!) of people. ![]() Are auxilliary controls hidden there? No, the drawer holds the mail list, which is essentially the main window's (Mailbox Viewer's) parent interface (Mailbox List). If this isn't the definition of Bad UI, then i don't know what is!įor that matter - look at how Apple is using Drawers! Look at Mail. Edit AllPages Dear God No!!! Drawer Abuse Stops Here! I am utterly tired of seeing shareware apps w/ scads of controls all buried in layers of control drawers! For example, check out Starfish 2.0 on VersionTracker. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |