This is exactly what I ended up learning in the end. :) Using
open allows launching of the application from rush, but you loose all
subsequent control. I gave up after that and decided to wait for
NewTek to release a proper command line version of lwsn for OSX
(realising of course that I could be waiting for a very long
while....!).
On 02/11/2005, at 10:58 AM, Greg Ercolano wrote:
[posted to rush.general]
open -a /Applications/LWSN/LWSN
open "lwsn cmdline"
I dunno -- anything that involves using open(1) is probably not
going
to yield satisfaction; at best you'll be able to start the
application,
but control over the app will be lost.
AFAIK, once open(1) is used to run an application, the shell
and the app
go their separate ways; the app 'forks off and away', becoming
parented
to the WindowServer.
At that point the shell/rush will no longer have control over
the process,
and the process pretty much becomes managed by the window manager.
Both reparenting and involving the window manager are two deal
breakers;
command line apps should do neither to be apps managable by
shell scripts.
In my experience, if an app can't be run from the command line
unless
open(1) is used, it's not really a command line app, and
shouldn't be
considered for use in shell scripts where controlled, serial
execution
of programs is needed.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)
---
Luke Cole
Systems Administrator / TD
FUEL International
65 King St., Newtown, Sydney NSW, Australia 2042
|