• 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: Where should AppleScripts reside?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Where should AppleScripts reside?


  • Subject: Re: Where should AppleScripts reside?
  • From: Michael Watson <email@hidden>
  • Date: Sun, 20 Jan 2008 00:40:56 -0500

1. Remember to send replies to the list, otherwise you're only talking to me. :-)

2. Allowing the user the ability to add additional scripts is mutually exclusive from storing your standard resources inside the application bundle. Either provide them a folder to drop their own things into, or allow them to point to a script in an arbitrary location, a la iChat alerts. (Or point to a folder, etc. There are several ways to do this.)

3. If you insist on installing the scripts into someone's user folder, you have to do it for all users, even ones that exist after the installation of your application, otherwise your application has no scripts for other users. You'll end up having an at-launch setup-and- install-resources check or sticking stuff in the /Library folder somewhere . . . both of which add to the complexity of removing your application at a later date as well as adding complexity to the development, testing, and support of your application.

4. If you want users to be able to modify the standard scripts you ship with, just distribute with your application copies of the standard scripts in a folder of example scripts. The power users that choose to modify the scripts you ship with will be able to do whatever they please, and your application's base configuration will be identical on every user's machine. (Your support person will be very happy and may buy you cookies for this.)


-- m-s


On 20 Jan, 2008, at 00:11, Devraj Mukherjee wrote:

Oh because I was hoping to allow the user to be able to modify/add
AppleScripts that runs on the nominated events.

Is the Bundle a good idea for that?

On Jan 20, 2008 2:35 PM, Michael Watson <email@hidden> wrote:
If they're standard resources of your application, why not store them
inside the application bundle instead of crapping them all over the
user's drive?


-- m-s


On 19 Jan, 2008, at 22:15, Devraj Mukherjee wrote:

Hi everyone,

My Cocoa app has a bunch of standard AppleScripts that are executed on
various events. I intend to write an installer for the application
which will also place the standard Applescript in a desired location.


What is the recommended path for putting such AppleScript files?
~/Library/Application Support/AppName?

Thanks a lot.

--
"I never look back darling, it distracts from the now", Edna Mode (The
Incredibles)
_______________________________________________


Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
@bungie.org

This email sent to email@hidden





-- "I never look back darling, it distracts from the now", Edna Mode (The Incredibles)

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Where should AppleScripts reside?
      • From: "Wesley Smith" <email@hidden>
References: 
 >Where should AppleScripts reside? (From: "Devraj Mukherjee" <email@hidden>)
 >Re: Where should AppleScripts reside? (From: Michael Watson <email@hidden>)

  • Prev by Date: Re: Help
  • Next by Date: EXC_BAD_ACCESS help
  • Previous by thread: Re: Where should AppleScripts reside?
  • Next by thread: Re: Where should AppleScripts reside?
  • Index(es):
    • Date
    • Thread