Re: Automation Sans Window Server
Re: Automation Sans Window Server
- Subject: Re: Automation Sans Window Server
- From: has <email@hidden>
- Date: Wed, 16 Apr 2008 02:24:30 +0100
On 15 Apr 2008, at 22:29, Paul Scott wrote:
It would be useful to be able to send events to applications to get
things done that only that application knows how to do, without
creating a gui instance of that application.
Since Mac applications require a Window Server connection to run an
event loop capable of handling incoming Apple events, running
scriptable apps on a machine without a logged in GUI user isn't going
to change anything: you either get a WS permissions error when trying
to launch the application, or get the application GUI popping up
behind the login dialog if you sudo it.
Maybe that means application developers must provide scripting
additions for their product, but as it stands now, even that won't
work because AppleScript seems to insist on connecting to the Window
Server and that the user is logged into it.
FWIW, appscript can be used within WS-less processes (though not its
osax module, as that relies on System Events). Not that this will help
you here - the ability to run applications GUI-less is a separate
problem, and something that you'll need to take up with individual
application developers as a feature request - but it'll let you
explore the issues a bit further yourself.
has
--
Control AppleScriptable applications from Python, Ruby and ObjC:
http://appscript.sourceforge.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden