Re: Adding commandline batch mode to Cocoa app

FROM : Carsten
DATE : Sun Mar 23 22:43:52 2008

Fair enough. I will keep these hints in mind, as well as Scott's
Applescript suggestion. On the bright side of things, it looks like I
have more than one option. That is always good. I am off to code up
the engine now, starting with File/Open.

Carsten


On 23/03/2008, Sherm Pendley <sherm.<email_removed>> wrote:
> On Sun, Mar 23, 2008 at 5:08 PM, Carsten <<email_removed>> wrote:
>
> >
> > Note that I am not planning to attack all this at once. I just want to
> > make sane choices up front about how things would be done, skeleton it
> > out, and then leave most of it for a later full implementation. I want
> > to start with the core engine and the Cocoa GUI. The initial overall
> > architecture should not be done later though. That might make it very
> > hard to accomplish cleanly, if at all.
>
> An alternative that hasn't been mentioned yet is to put the core engine in a
> library. The Cocoa GUI would link against it, and include it in its .app
> bundle. The command-line tool would also be included in the the
> Contents/MacOS subdir, so as to allow the library's install_name (if it's a
> .dylib) to resolve correctly for both the command-line tool and the GUI app.
> You would, of course, want to create the symlink in /usr/bin as described
> earlier.
>
> Another possibility would be to write a tool that parses the command-line
> options, but doesn't do the "heavy lifting" itself. Instead, it could
> communicate with the .app by way of AppleScript, raw Apple Events, or some
> other IPC mechanism.
>
> One thing I would *not* do is try to write a single binary that attempts to
> provide both GUI and CLI interfaces. Horses for courses, and all that. :-)
>
> sherm--
>
>