If someone at MM wants to improve their write-up at http://www.macromedia.com/support/director/ts/documents/ bundle_proj.htm my experience may be useful.
The writeup is imperfect; however, examining a few .app bundles can be very useful in figuring out how to assemble your own. (Evidently you did that yourself. ;)
Under Getting This on a CD, the MM writeup says that the alias to the OS 9 projector should be placed "at the root," and in the same paragraph, it says the alias should be placed "at the same level as the bundle." In fact, it should be placed at the same level as the Contents folder.
Yes; that's not the clearest paragraph, but the alias does need to be alongside the Contents folder inside your app bundle, and the graphic that accompanies the article does show the alias in the correct location (but the expanded folder views make it hard to see that).
What the writeup actually says at that point is this:
==
The "stub9" alias at the root will have to created from a disk image, otherwise the alias will point to the original hard drive location of the original projector. Use the OS X application Disk Copy to create a disk image to be burned to the CD. Once a disk image is created, create an alias to the OS 9 projector and place the alias at the same level as the bundle.
==
The "stub9" alias referenced is at the root of the app bundle; that is, it's right inside it. It seems the term "the bundle" is here referring to the Contents folder, which is imprecise.
It also seems that the alias to the OS 9 projector has to have the filename extension ".alias" although I'm not entirely sure about this.
No. Just the word "alias". That is, make an alias of your OS9 program and don't change its name. Just put it alongside the Contents folder.
While the illustration that accompanies the page shows the alias being renamed, there's no reason to change it, really. As you suggest it's a dubiously wise thing to do...
The MM write-up says nothing about the contents of the plist files and does not explain which properties must match which filenames, etc.
That's true; however, Mac's OSX is crawling with plist files that can be copied and altered.
Much of the info in the plist files is optional, but some of it seems crucial. (E.g., what in the world is "com.macromedia.Otto"--do we need to use that?)
That is the name of your preferences file. You can rename it anything you want, since you can't change the file's contents anyway. Information on how to properly name preferences files is available from Apple, but briefly they follow the Java scheme of your domain name backward, finished by the name of the app. So if I had a program named "goofball" I'd use the name com.nightwares.goofball for the prefs file.
(This is not the same as files written using setPref.)
The MM downloadable example does not use a custom icon, which requires another property added to info.plist:
key: CFBundleIconFile string: MyIconFilename
Also true. It would be nice if the writeup could include a properly formatted plist that contains all the necessary references, along with some kind of icns file.
Warren Ockrassa | President, nightwares LLC [EMAIL PROTECTED] nightwares LLC | Consulting Programming http://www.nightwares.com/ Developer | Structor, a presentation development/programming tool Info and demo | http://www.nightwares.com/structor/ Author | Director 8.5 Shockwave Studio: A Beginner's Guide Chapter samples | http://www.nightwares.com/director_beginners_guide/
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
