Re: Tools, installers, and login items
Re: Tools, installers, and login items
- Subject: Re: Tools, installers, and login items
- From: Eric Peyton <email@hidden>
- Date: Fri, 9 Nov 2001 20:41:11 -0600
Then it needs to be a login item. I would suggest
a) make sure your foundation tool is executable and name it
<name>.command and then terminal will attempt to launch it as a Terminal
item. This should be "addable" to your login items, but I haven't tried
it. It will have the ugly (dis)advantage of launching Terminal on the
users login however.
b) that you create a small wrapper application that will launch your
foundation tool so that users can add it as a login item.
Eric
On Friday, November 9, 2001, at 08:29 PM, Angela Brett wrote:
On Friday, November 9, 2001, at 10:52 pm, Angela Brett wrote:
I have a foundation tool which is intended to be running all the
time. I would like to make an installer for it which will make it a
login item or something, so it will always be open. I have two
problems though... firstly, it doesn't seem like a tool works as a
login item, since it doesn't run when doubleclicked. Secondly, I
don't know how to get an installer to make something a login item...
looking at the Package Maker help I guess it would be a post-install
script but I don't know what should be in that. Am I borking up the
wrong tree here? Can/should it be a login item? It's only meant to
run for the user who installs it.
If it should always be running, it should be a StartupItem instead.
There is a howto on startup items here:
http://www.opensource.apple.com/projects/documentation/howto
It looks to me like StartupItems are for system-wide things which
aren't just for individual users. I would like my tool to be running
all the time when a user who has installed it is logged in.
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev