On Thu, Dec 11, 2008 at 2:00 PM, Shayne Wissler wrote:
> On Thu, Dec 11, 2008 at 11:55 AM, Eric Schlegel wrote:
>
>>> Can you perhaps suggest a book from which I would have learned this
>>> and other architectural nuances of systems programming on the Mac?
>>
>> I can't, partly because I haven't
On Thu, Dec 11, 2008 at 12:03 PM, Sherm Pendley wrote:
> On Dec 11, 2008, at 1:42 PM, Shayne Wissler wrote:
>
>> Just like an X application would work on Linux. I
>> don't want for it to be required to have a .app directory with plists
>> or nibs or anything other than just my binary.
>
> If you w
On Dec 11, 2008, at 1:42 PM, Shayne Wissler wrote:
Just like an X application would work on Linux. I
don't want for it to be required to have a .app directory with plists
or nibs or anything other than just my binary.
If you want something that looks and acts like an X11 app, why bother
port
On Thu, Dec 11, 2008 at 11:55 AM, Eric Schlegel wrote:
>> Can you perhaps suggest a book from which I would have learned this
>> and other architectural nuances of systems programming on the Mac?
>
> I can't, partly because I haven't done an exhaustive survey of all
> programming books on Mac OS
On Dec 11, 2008, at 10:35 AM, Shayne Wissler wrote:
Yes, that is exactly what I want, and your solution worked
brilliantly! Thanks!
Great!
Can you perhaps suggest a book from which I would have learned this
and other architectural nuances of systems programming on the Mac?
I can't, partl
On Dec 11, 2008, at 1:35 PM, Shayne Wissler wrote:
On Thu, Dec 11, 2008 at 11:18 AM, Eric Schlegel
wrote:
Jumping in late here...
It sounds like what you want to create is just a flat-file binary
that does
not use the bundle hierarchy that is typical for a Mac OS X app.
I.e., you
want yo
Shayne Wissler wrote:
I've got an application that isn't specifically for the Mac, and I
want the same standard user-experience whether they are on the Mac or
on Windows or on Linux. I want them to be able to run this program
from the command line by directly using the binary (without calling
"o
If it has an interface then I would suggest following the HIG. However
it sounds like you have a tool for the commandline and there is an
option to create that in Xcode, AFAIK.
Bruce Martin
The Martin Solution
br...@martinsolution.com
http://www.martinsolution.com
http://externals.martinsolut
Hi Bill,
I've got an application that isn't specifically for the Mac, and I
want the same standard user-experience whether they are on the Mac or
on Windows or on Linux. I want them to be able to run this program
from the command line by directly using the binary (without calling
"open"), to have
On Thu, Dec 11, 2008 at 11:18 AM, Eric Schlegel wrote:
> Jumping in late here...
>
> It sounds like what you want to create is just a flat-file binary that does
> not use the bundle hierarchy that is typical for a Mac OS X app. I.e., you
> want your app to just be a single file "MyApp" rather than
On Dec 11, 2008, at 10:07 AM, Shayne Wissler wrote:
Thanks for all the varied answers! It sounds like no one actually
knows architecturally what is going on here or why! Is there perhaps
some "dissonance" between the UNIX design aspects and the Apple design
aspects of OSX?
Actually I'd wage
Jumping in late here...
It sounds like what you want to create is just a flat-file binary that
does not use the bundle hierarchy that is typical for a Mac OS X app.
I.e., you want your app to just be a single file "MyApp" rather than a
hierarchy "MyApp.app/Contents/MacOS/MyApp". Is that cor
Thanks for all the varied answers! It sounds like no one actually
knows architecturally what is going on here or why! Is there perhaps
some "dissonance" between the UNIX design aspects and the Apple design
aspects of OSX?
But it sounds like I can hack my way through given your suggestions,
thanks
Andrew Farmer wrote:
I'm not sure, but I can tell you that mplayer does what you're talking
about and works fine. You may want to take a look at how they do it.
OpenOffice.org, too. It builds an app bundle, etc., using command line
tools. It may not be a good place to start, though. It is ab
On 10 Dec 08, at 13:47, Shayne Wissler wrote:
I have a Cocoa application that I am compiling in the traditional UNIX
manner using Makefiles and I want to be able to invoke it with
command-line arguments and without creating/installing it like
traditional OSX apps, as in "x.app/Contents/MacOS/x".
On 2008-Dec-10, at 16:47, Shayne Wissler wrote:
Is there a way to do this without making some kind of wrapper caller
that generates the directory and a script or some such? Or is it
wholly frowned upon to do what I'm wanting, and if so, why does it
half-work rather than fail with a decent error
If you are building a cocoa application, make it a normal cocoa
application and use the open command to launch it.
On Dec 10, 2008, at 1:47 PM, Shayne Wissler wrote:
Is there a way to do this without making some kind of wrapper caller
that generates the directory and a script or some such? Or
Unless I misunderstood your situation, I believe using the "open"
command should work.
Example:
open x.app
Cheers,
Mani
On Wed, Dec 10, 2008 at 4:47 PM, Shayne Wissler <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have a Cocoa application that I am compiling in the traditional UNIX
> mann
18 matches
Mail list logo