Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!ucbvax!dewey.soe.berkeley.edu!oster
From: oster@dewey.soe.berkeley.edu (David Phillip Oster)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Binding ICN#'s to applications
Message-ID: <28230@ucbvax.BERKELEY.EDU>
Date: 28 Feb 89 10:53:08 GMT
References: <8959@orstcs.CS.ORST.EDU> <14891@cup.portal.com> <711@microsoft.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster)
Distribution: usa
Organization: School of Education, UC-Berkeley
Lines: 14

In article <711@microsoft.UUCP> stuartb@microsoft.UUCP (Stuart Burden) writes:
>One point that no-one has meantioned yet, is:
>With the ICN#, FREF, BNDL and signature resources, you should be set.

One more thing: before you give the application to anyone else, you have
to register the signature with Apple Developer Technical support and get
their okay.  Even if it is a game or a toy, register it!  They are trying
to make sure that every application with an icon has a unique signature
so, for example some poor user won't double click on an Excel file and
have the Finder start up MacSuperCar to try and read the file. 

--- David Phillip Oster            --"When we replace the mouse with a pen,
Arpa: oster@dewey.soe.berkeley.edu --3 button mouse fans will need saxophone
Uucp: {uwvax,decvax}!ucbvax!oster%dewey.soe.berkeley.edu --lessons." - Gasee