Compiling and using OmniNetworking.framework

[Rick Roe rick@xxxxxxxx]

>> I now have them built into the app wrapper, which is a more involved
>> procedure - look up
>> Mike Ferris's post on the topic.
> 
> But that zeroes the advantage of a framework. For example, if you have three
> applications installed that use OmniNetworking (which isn't that unthinkable),
> you would have the framework three times installed, even though you need it
> only once.

According to Apple's System Overview, frameworks installed inside an
application bundle are available to other applications. (It may well be that
they aren't available to other applications on Public Beta -- I haven't
checked.)

Of course, this raises issues in the software distribution process. Do you
distribute your frameworks separately and tell users they need them
installed before using this or that application, or distribute them with
some of your applications and tell users they need such and such application
installed in order to use this other application?

-- 
Rick Roe
    Webmeister & Icon Dude
    http://www.icons.cx/