Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!shelby!polya!ali
From: ali@polya.Stanford.EDU (Ali T. Ozer)
Newsgroups: comp.sys.next
Subject: Re: Mach-O sements & Documentation ( was Re: Spirograph..)
Message-ID: <8850@polya.Stanford.EDU>
Date: 30 Apr 89 16:21:52 GMT
References: <569@hydra.gatech.EDU> <8827@polya.Stanford.EDU> <281@nueces.UUCP>
Sender: Ali T. Ozer <ali@polya.Stanford.EDU>
Reply-To: ali@polya.Stanford.EDU (Ali T. Ozer)
Organization: .
Lines: 42

In article <281@nueces.UUCP> chari@nueces.UUCP (Chris Whatley) writes:
>In article <8827@polya.Stanford.EDU> I say:
>> You can now include .nib files (and any other data file you might need)
>> in Mach-O segments of your executable. 
>
>Does this mean that "ResEdit" capabilities could exist in Interface Builder
>so that I could edit the icon that was included as a segment in my program
>without having to recompile? 

The data in the Mach-O segments is read-only and cannot be edited. (I'm 
not sure if you can edit it without changing the size; that'd be all you need
to in most cases. Avie? Actually Interface Builder does not let you edit
a .nib file that's been put into an executable anyway.)

There is however another way to include .nib files with your
application: Through app wrappers. You'd do this if you wanted your
data and .nib files available seperately from your executable, but
with the convenience of having the user deal with just one icon. If
your program is called "Foo," you create a directory named "Foo.app,"
put the Foo executable and all your data files in the directory.  When
user sees the directory Foo.app in the browser, they see a file, not a
directory. When they move it, copy it, etc, it behaves like one file.
When they "open" it (double-click on it), Workspace Manager launches
the "Foo" application in the directory.

There are ways to get in the directory; "Open Directory" in the Workspace
Manager menu lets you see the contents. You can get to it through the shell.
You can also get to it through the standard file requesters.

This capability exists in 0.8, by the way; check out the DSPMusic demo
in the demos directory.

>Re: Library
>
>Can I expect Objective-C documentation, DPS manuals, correct man pages :-) ?

0.9 does come with a lot more of the documentation on line than 0.8 does.
However, the Obj-C documentation and the Adobe DPS manuals aren't online
in 0.9.

Ali Ozer, NeXT Developer Support
aozer@NeXT.com