On Jun 25, 2009, at 10:56 AM, Alexander Spohr wrote:


Am 25.06.2009 um 19:20 schrieb Doug Scott:

It is just like dragging out a complex Apple provided object which contains embedded scrollers and such. I don't have to connect the Apple supplied scrollers to the Apple supplied scrolling view, Apple did it with embedding ( or could have if they chose to do it that way, I don't really know how Apple's stuff is built ).

No, Apple did it with a class that does the layout by itself. NSScrollView is configuring its subviews itself and on its own. It is not composed in IB - you know why now. IB just gives you an inspector and some drag'n'drop for this class.

And now you know why IB should be dynamic too. You had to code it up the hard way. Not good. Perfectly functional, but not good.
But I now get your point. You would like to compose some views into a new (super)view and have this act like a dynamic template. If you change the template, all users should change as well.

So you could write a view class that sets up the views you want the way you want them. Put that view on a palette and give it an inspector. If you change the implementation of your class all apps will pick that up on the next compile with your framework that contains the class. You can do pretty complex stuff then, but you have to do it in code.
Been there, done that, sort of. The 'do it in code' makes IB partially pointless. You can do it all in code if IB isn't what you like and you are willing to pay that particular price. Make IB dynamic and Apple will have something to show at the developer conference that could blow the crowd away. At least those of us who make IBPlugins.

Hope that gives some helping ideas,

        atze

And now I have done it with embedding, and the power is awesome. I hope that gives Apple some ideas as to why IB should become dynamic and balance out the Xcode build system.


_______________________________________________

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

Reply via email to