• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: now it really gets weird
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: now it really gets weird


  • Subject: Re: now it really gets weird
  • From: Eliah Kagan <email@hidden>
  • Date: Thu, 17 Jul 2003 09:14:44 -0700 (PDT)

The other replies have pretty much answered the
question, but this might add something to clear up
some of the confusion.

> So how does the cocoa development process produce
> executable files that an
> e-mail client can separate into component files?
> I find this amazing.

Say your app was called Hello (it's probably not, but
I've got to use some name here). The icon you
double-click on to run Hello (which has 'Hello' as its
caption) really refers to a folder called Hello.app.

In fact, if you make a new folder and call it
something ending in .app, and then you double click on
it in the Finder, it will look just like an app
starting up. It just won't do anything.

You can look at what's inside this folder by
ctrl-clicking it and selecting "View Package Contents"
in the Finder. All this does is to tell the Finder to
open it up in a Finder window like it would if it were
a normal folder and you double clicked on it. It will
give you a Finder window for the folder Hello.app.

Hello.app will contain one subfolder, called Contents.
If you go into Contents, you will see the items that
make up your app package.

One of the subfolders of Contents is called MacOS. One
of the files in MacOS is your program's main
executable file. There might be other files in MacOS,
and there might not. The name of the main executable
file is usually the same as the name of the app (no
.app extension), but not always.

You can email the main executable file in
Hello.app/Contents/MacOS, and it will not be
separated. (It's a singlef file, after all.) Of
course, it won't do much of anything by itself,
because it needs all the other files in the app to be
useful.

-Eliah

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: now it really gets weird
      • From: Jeff Harrell <email@hidden>
    • Re: now it really gets weird
      • From: Eliah Kagan <email@hidden>
References: 
 >Re: now it really gets weird (From: "Michael Ciavola" <email@hidden>)

  • Prev by Date: Re: cocoa/Obj-C API for iCal
  • Next by Date: Synchronize iCal with .ics files
  • Previous by thread: Re: now it really gets weird
  • Next by thread: Re: now it really gets weird
  • Index(es):
    • Date
    • Thread