• 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: Creating the app menu from scratch
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Creating the app menu from scratch


  • Subject: Re: Creating the app menu from scratch
  • From: "Jim Crafton" <email@hidden>
  • Date: Mon, 14 Jul 2008 10:29:07 -0400

> Your application's menu isn't that big of a deal, but your application's
> integration with Mac OS X is a very big deal and that is most of the battle
> of doing "nib less" development.   It is much more than just populating the
> main menu.   Specifically, the application wrapper -- the .app -- typically
> contains all kinds of metadata that is used by Mac OS X to integrate the
> application into the system, both from the Finder's perspective and when the
> application is run.

Well that I understand. And I've made pains in my framework library to
account for that, and in fact have borrowed many ideas from Apple and
used them on Win32. In fact the resource loading works in much the
same way as resource bundles do on OS X, as well as the presence of
info.plist resource files.

>
> How do you bootstrap the framework?  I.e. what executable is run that uses
> the resources from the framework?  That is the most likely place to stick
> the MainMenu.nib and let Cocoa bootstrap the normal way.

Well you'd create your standard C++ app in Xcode (with standard app
settings, i.e. you're creating a full blown .app bundle, not a unix
command line utility), and then link to my libraries as Frameworks
(i'd like to offer the possibility to link statically, but I'm 100%
sure about how to do that). Given that I've created my libraries as
Frameworks, can I have a .nib as part of one of the Framework bundles?
My framework is laid out like so:

FoundationKit.framework
GraphicsKit.framework (depends on FoundationKit.framework)
ApplicationKit.framework (depends on GraphicsKit.framework)

If you're writing a GUI app, then you'd link to
ApplicationKit.framework (and GraphicsKit.framework +
FoundationKit.framework).  Can I have a MainMenu.nib file in the
ApplicationKit.framework? That way it's all built in and the developer
doesn't have to worry about creating it.

Cheers

Jim
_______________________________________________

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

  • Follow-Ups:
    • Re: Creating the app menu from scratch
      • From: Bill Bumgarner <email@hidden>
References: 
 >Creating the app menu from scratch (From: "Jim Crafton" <email@hidden>)
 >Re: Creating the app menu from scratch (From: "Michael Ash" <email@hidden>)
 >Re: Creating the app menu from scratch (From: "Jim Crafton" <email@hidden>)
 >Re: Creating the app menu from scratch (From: Bill Bumgarner <email@hidden>)

  • Prev by Date: Re: NSViewController and View Swapping
  • Next by Date: NSBezierPath fill pattern?
  • Previous by thread: Re: Creating the app menu from scratch
  • Next by thread: Re: Creating the app menu from scratch
  • Index(es):
    • Date
    • Thread