On Aug 7, 2009, at 5:01 PM, David M.Cotter wrote:
the problem is i'm stuck with a very large legacy code base that i must modify minimally to shoehorn into Cocoa. this same code must cross compile on windows, so i can't change the underlying architecture, which has for a decade now relied on the fact that we can share submenus across many super-menus.
You really will need to adjust your application’s architecture. You can’t expect it to remain static forever, especially when changing the underlying framework. Cocoa in particular is not amenable to such an approach: The framework expects that you will work with it in the way that it is designed to be used, not in the more arbitrary “mix and match” fashion that earlier procedural systems like the Mac Toolbox andWin32 supported.
If nothing else, you can create your own menu classes to represent the menu structure you want (including sharing of submenus) and use them to construct appropriate Cocoa or Windows menu objects on the target platform.
— Chris _______________________________________________ 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
