The advantage to a kludge like this is that it is not a system-wide
loginhook so sysadmins shouldn't complain. However, I think we all
know the BEST answer is to write the application correctly to set
prefs on first launch from an internal mechanism.
This specific question aside -- in the grander scheme of things, as
we
go forward, shouldn't we be dropping the idea of loginhooks in favor
of LaunchAgents?
Best wishes,
Scott
--
Dr. Scott Russell
IT Support Engineer/Consultant
Arts & Letters Computing, Distributed Support Services,
Office of Information Technologies, University of Notre Dame
Instructor of Horn, University of Notre Dame and Saint Mary's College
Assistant Horn, South Bend Symphony Orchestra
234 Decio Hall
574-631-7021
email@hidden
http://www.nd.edu/~srussel2/
On Aug 17, 2008, at 5:51 PM, Stéphane Sudre wrote:
On Aug 17, 2008, at 7:08 PM, Scott Russell wrote:
Instead of login hooks, isn't the correct mechanism going forward a
launchd item in /Library/LaunchAgents/ anyway? User-specific, runs
at login ... sounds like a login hook to me. *shrug*
Can the answer be no?
LaunchAgents are only working on 10.5 and later (in 10.4 they are
not working correctly at all).
Additionally:
- LaunchAgents are for repetitive tasks. Setting default preferences
is a one-shot operation.
- There is no guarantee that a LaunchAgent item will be launched
before your app. LoginItems can be launched before a LaunchAgent
item. They can already be launched before a LaunchDaemon item.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
>
m
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden