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 <[EMAIL PROTECT
On Sun, Mar 23, 2008 at 5:08 PM, Carsten <[EMAIL PROTECTED]> 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 star
The "Mac way" to do this is to make your app scriptable via AppleScript.
--
Scott Ribe
[EMAIL PROTECTED]
http://www.killerbytes.com/
(303) 722-0567 voice
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or mod
Running from both the GUI and commandline at the same time would be
rather unusual. I don't expect that heavy commandline batch users will
use the GUI app for anything but setting up some configuration files,
so it would be acceptable for the script-launch to detect that it was
running already, pri
On Mar 23, 2008, at 4:43 AM, Carsten wrote:
Ah, okay, I see now. My script will just launch the application
executable with a specific commandline that forces it into batch mode,
so the difference in functionality or convenience between a symlink to
a tool and a generated one-liner script (plus
On 23/03/2008, Marcus <[EMAIL PROTECTED]> wrote:
> I agree. I would recommend /usr/local/bin if you're only targeting
> Leopard. Tiger and previous versions of Mac OS X does not come with /
> usr/local and doesn't have it in the user's path.
A-ha, I didn't know that! Hmm, that makes it a bit har
23 mar 2008 kl. 09.10 skrev Carsten:
/usr/bin should normally be for programs used by the system during
startup, if I understand correctly, and /usr/sbin for system programs
used after /usr has been mounted. /usr/local/bin really ought to be
the correct place for user scripts and programs.
I
/usr/bin should normally be for programs used by the system during
startup, if I understand correctly, and /usr/sbin for system programs
used after /usr has been mounted. /usr/local/bin really ought to be
the correct place for user scripts and programs.
I am not sure what the advantage of using an
23 mar 2008 kl. 00.01 skrev Carsten:
The script installation in a more central place is an interesting
thought. Is /usr/local/bin the Apple-sanctioned place for
user-installed commandline utilities, rather than something like (the
non-existent) /Users//bin? I could also install such a
script al
The script installation in a more central place is an interesting
thought. Is /usr/local/bin the Apple-sanctioned place for
user-installed commandline utilities, rather than something like (the
non-existent) /Users//bin? I could also install such a
script alongside the .app bundle, which is a thoug
On Sat, Mar 22, 2008 at 4:26 PM, Carsten <[EMAIL PROTECTED]> wrote:
> However, image processing apps can benefit from batch modes, and
> although some things can be nicely handled by an in-app batch manager,
> the ideal would be to also allow the application to be run from the
> commandline, as
I am new to Cocoa and Mac development, but not to development, being a
C/C++ graphics programmer by trade. I am working my way through
Hillegass' book, and although I am forgetting the details as fast as I
am reading them, it all makes sense, and I suppose it will come
together and stick in my head
12 matches
Mail list logo
