Re: Running normally-GUI Cocoa apps as background processes
Re: Running normally-GUI Cocoa apps as background processes
- Subject: Re: Running normally-GUI Cocoa apps as background processes
- From: Markus Hitter <email@hidden>
- Date: Fri, 27 Jul 2001 21:05:51 +0200
Am Freitag, 27. Juli 2001 um 17:45 schrieb Ken Tabb:
Hi,
Supposing I have a GUI-based Cocoa app, is there any way I can run it as
a background process (i.e. invisible, like Apache, not just 'behind the
current app')? I've got an app which I'd like to be running in the
background of some macs (doing background processing for image
crunching)
and I'd like to be able to ssh in and start them up remotely, without
the
user getting a faceful of half-processed image.
You want a GUI based App, but don't want to show anything to the
user ?!?!?
If you only want to process your image, why do you want to show it on a
(hidden) screen?
I know this can be done with X Windows apps, but bearing in mind there's
only 1 instance of the Quartz / Aqua window manager I'm not sure if it's
possible.
Startup a secondary X/OS X Window Server to process an image in
background? Not the sort of efficiency I like.
Or are there some clever argc argv tweaks which can achieve it.
XFree86 for Darwin does something similar. Don't know exactly how they
do it, though.
I'm hoping that I can then control it via DO on another mac.
You can use DO, but you could start your tool in a remote-connected
shell as well. commands/progress info would go trough stdin/stdout.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/