Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!brutus.cs.uiuc.edu!apple!sun-barr!newstop!sun!coherent!next!aozer
From: aozer@next.com (Ali Ozer)
Newsgroups: comp.sys.next
Subject: Re: file packages, NXMapFile
Message-ID: <109@next.com>
Date: 8 Feb 90 18:52:02 GMT
References: <1219@shelby.Stanford.EDU>
Reply-To: Ali_Ozer@NeXT.com (Ali Ozer)
Organization: NeXT, Inc.
Lines: 28

In article <1219@shelby.Stanford.EDU> Jim Brinkley writes:
>I'd like to create a file package similar to Librarian.app for an
>application I'm writing, so I can include a help file in the package.
>I couldn't find any documention on how to actually create a file
>package, so I just made a directory called Myapp.app, and put the
>executable Myapp together with the help file in Myapp.app. That seems
>to work ok - when I double click on Myapp.app the correct application
>starts up. However, the icon associated with Myapp.app is the generic
>application icon rather than the custom one I associated with Myapp.
>So what I'd like to know is, 1) how do you get a custom application
>icon to be associated with the file package, and 2) is there some
>other way I'm supposed to create file packages?

What you need to do is specify that files named MyApp.app have the same icon
as the executable named MyApp.  To do this, you need to perform a little 
surgery on your IB-generated iconheader file --- add the following line:

F	MyApp.app	MyApp	app

Note that the fields are separated by tabs.

Unfortunately IB doesn't help you too much with packaged apps, so you should
do some work on your Makefile.postamble; maybe by defining an "install::" rule
that creates the .app directory and moves the executable into it.  You also
need to make sure your custom .iconheader file isn't blown away everytime you
edit your project.

Ali (Ali_Ozer@NeXT.com)