• 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: saving OSAX in package contents
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: saving OSAX in package contents


  • Subject: Re: saving OSAX in package contents
  • From: Walter Ian Kaye <email@hidden>
  • Date: Fri, 30 Jan 2004 02:09:18 -0800

At 08:31p +1100 01/30/2004, John Cochrane didst inscribe upon an electronic papyrus:

I seem to remember Chris Nebel mentioned some time ago that it was possible to save an OSAX in the package contents of an Applescript saved as an application bundle. I have just tried unsuccessfully to do this. Does it only work with certain osaxen? Where in the application bundle should it be saved?

Only took a minute to search my Eudora mailbox:


At 04:45p -0800 11/20/2003, Christopher Nebel didst inscribe:
From: Christopher Nebel
Subject: Re: "save as" question
Date: Thu, 20 Nov 2003 16:45:42 -0800

On Nov 20, 2003, at 2:30 PM, roy whelden wrote:

Can someone explain to me in a few short sentences what Script Editor's "save as application bundle" means?

It's a new flavor of AppleScript application that uses the standard "bundle" format, which most Mac OS X applications use. The resulting application "file" is really a folder with a well-defined internal layout [1]. At the moment, we're not exploiting this for very much [2], but in the future, it will allow a lot more flexibility in an applet. The major gotcha for them is that they only work on Panther (10.3) and later.


--Chris Nebel
AppleScript Engineering

[1] Details of the bundle format are covered in the Application Packaging chapter of the Mac OS X System Overview -- see <http://developer.apple.com/documentation/MacOSX/Conceptual/ SystemOverview/AppPackaging/index.html>

[2] You can, however, exploit it yourself in a couple of interesting ways. First, using "path to" and a bit of relative path jiggling will get you the internal Resources folder, in which you may store whatever you like. Also, a fairly obscure feature of Panther is that if you put a scripting addition inside :Contents:Resources:ScriptingAdditions:, it will be loaded for that applet, so you don't have to muck around with telling people to install it manually. Of course, that only works if they're running Panther.
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.

References: 
 >saving OSAX in package contents (From: John Cochrane <email@hidden>)

  • Prev by Date: saving OSAX in package contents
  • Next by Date: Call a handler from applescript
  • Previous by thread: saving OSAX in package contents
  • Next by thread: saving OSAX in package contents
  • Index(es):
    • Date
    • Thread