On Sat, Jul 18, 2009 at 1:18 AM, Dale Miller<dalelmil...@cableone.net> wrote: > I've satisfied myself that trying to use IB which is essentially a > bind-at-compile-time approach is a pita when trying to deal with an > execution-time-specified number of windows which must accommodate a tab view > which must accommodate a workspace (text view imbedded in a scroll view), > the size of which is run-time-specified.
IB is not a "bind-at-compile-time" approach. I'm really not even sure what that means in this context. Yes, you're creating objects and playing around with them before freezing them at compile time, but they're all unfrozen using -initWithCoder: or other well-defined initialization mechanisms at runtime, at which point they're normal objects. Perhaps you need to overcome this mental hurdle? Interface Builder is, simply put, How It's Done. --Kyle Sluder _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com