On Thu, Jun 25, 2009 at 11:33 AM, Doug Scott<dougrsc...@comcast.net> wrote:
> Perhaps there is something basically wrong in the way I'm making IBPlugin > projects... That was essentially my point. I think you are trying to use them in a way that doesn't give you much benefit and possibly ignoring another way that may be more aligned to what you want. Step back from the plugins... consider creating xib 1, xib 2, and xib 3 that together get what you want at runtime. This could be shared across projects. As you modify the nib all project feel the effects since xib is what you use at runtime while the plugin is essentially a template/tool extension used when modifying xibs. Anyway it is hard to fully grasp/express all of the nuances of what you are doing, what you want to do, and what I am trying say in email... so I am just trying to point out a different way to think about it and see if helps you get closer to what you want. Also do you know that you can drag a set of objects into a xib, configure them, wire them up, etc. and then drag a parent (assuming view containment, etc.) back into the object library. This then become a template that you can use in future. -Shawn _______________________________________________ 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
