{
CFBundleDevelopmentRegion = English;
CFBundleExecutable = Start;
CFBundleGetInfoString = "Start Application";
CFBundleIconFile = "Start.icns";
CFBundleInfoDictionaryVersion = "6.0";
CFBundleName = Start;
CFBundlePackageType = APPL;
CFBundleShortVersionString = "1.0";
CFBundleSignature = CFINTRO;
CFBundleVersion = "1.0";
}{
BuildVersion = 02;
CFBundleShortVersionString = "1.0";
CFBundleVersion = "1.0";
ProjectName = Start;
ReleaseStatus = GM;
SourceVersion = 0200;
}"Start" is the name of my projectors and the topmost folder, Start.app. (I used "foo.app" in my original post because that's what the MM write-up uses.)
Slava
At 05:58 PM 7/8/03 -0400, Mathew Ray wrote:
What do your plist files look like?
~Mathew
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Slava Paperno Sent: Tuesday, July 08, 2003 4:39 PM To: [EMAIL PROTECTED] Subject: <lingo-l> OSX/9 bundle puzzle: foo.app = foo.app
I'm trying to create a Mac OS 9 / OS X bundle for my Director application, and I've run into a puzzle. I wonder if anyone else has seen the same thing.
I followed the directions at http://www.macromedia.com/support/director/ts/documents/bundle_proj.htm
One of the first claims made there is that a volume root folder that you
name "foo.app" will actually display its name as "foo" and will appear to be an application rather than a folder (both under OS 9 and OS X) until you Ctrl-click it and select Show Package Contents. This works fine for me under OS X but fails under OS 9.2.
I burned the volume to a CD under OS X. The disk works fine under OS X on other machines, but on OS 9.2 machines, the name of the folder is foo.app and it looks and acts just like a folder. I can start my application by opening this folder and then opening folder Contents inside, and then double-clicking the alias for the OS 9 projector in that folder--but that should not be necessary.
A couple of things I discovered while practicing this arcane art:
If you use lingo.ini and MyProjector.ini, these have to be duplicated and placed alongside each of the two projectors. This is not mentioned in the MM writeup.
If you use "the moviePath" anywhere in your movies, that will return the
actual path on the volume, i.e. MyVolume:foo.app:contents:MacOS: etc. This was not apparent to me at first. The consequences are dramatic for a movie that needs to access files by specifying the complete path.
Any tips on why my volume's root "foo.app" folder is still called foo.app under OS 9.2 would be appreciated.
Slava
[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!]
