• 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: Why initialize the menubar without Interface Builder
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why initialize the menubar without Interface Builder


  • Subject: Re: Why initialize the menubar without Interface Builder
  • From: Uli Kusterer <email@hidden>
  • Date: Sun, 4 Nov 2007 13:06:14 +0100

Am 04.11.2007 um 02:10 schrieb Erik Buck:
I admit, that most projects I have directly
experienced have had ten or fewer software developers
at any moment in time. There might have been fifty
developers in the lifetime of an application, but not
all at once.  Of the ten concurrent developers, the
usual number of GUI developers is exactly one.

Oh, wow. That must be tough. We have several people there. Of course, we have an interaction designer and a graphics designer that collaborate on the actual designs and make sure it's consistent, but we have several people who do GUI programmer work, and it's good like that. With the amount of GUI work involved in a Mac app, I'd go mad if I was the sole GUI developer on an app.


Uli makes a very valid point!  I think we need a human
readable and computer merge-able way of viewing the
target-action, bindings, and layout/nesting details of
a nib.  This is essential even just to document the
design of a nib.  It is too difficult to figure out
how somebody else's nib is put together right now.

Yeah. XIB was kinda supposed to do that, but someone had the great idea of dumping a whole binary NIB in there as well...


I don't think these problems with IB and nibs raise to
the level where I would prefer to hard code all
aspects of a GUI.

I never said "all aspects", but some of the really neat features, like bindings, are just prohibitively opaque in a NIB. So you'd have to script those using bindTo:. Trouble is, then you're back to Carbon's HIViewFindByID()-technique. And I went to Cocoa exactly to avoid this...


Cheers,
-- M. Uli Kusterer
http://www.zathras.de



_______________________________________________

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


References: 
 >Re: Why initialize the menubar without Interface Builder (From: Erik Buck <email@hidden>)

  • Prev by Date: Re: Why initialize the menubar without Interface Builder
  • Next by Date: Making bundles/packages
  • Previous by thread: Re: Why initialize the menubar without Interface Builder
  • Next by thread: Re: Why initialize the menubar without Interface Builder
  • Index(es):
    • Date
    • Thread