Re: How to create a easy of use Installer?
Re: How to create a easy of use Installer?
- Subject: Re: How to create a easy of use Installer?
- From: Wade Tregaskis <email@hidden>
- Date: Thu, 10 Jun 2004 19:31:10 +1000
is there an efficient alternative for the case where you want to
provide frameworks that are going to be used by multiple applications
in a suite?
If all applications are shipped together, you could keep them in the
same directory, make a frameworks-directory in that same dir, and link
the executables to search there (relative from the executable_path).
That would require a framework-dir in the same dir as any of the apps
in the suite, less elegant than ~/Library/Frameworks, but easier to
"maintain" by the end-user.
Don't do this. I and many others despise apps which think themselves
important enough to require support files & folders to waste space in
my Applications folder. If your app needs anything it should be
included in the bundle, or in an appropriate system-wide location (e.g.
Application Support folders, for example).
Including the frameworks inside each application leads to bloat since
they get duplicated and also does not allow the OS to do any resource
optimisation when the same framework is being used by more than one
application.
I'm all for shared resources -- but generally 3rd party frameworks
will probably only be used by a single application on the users disk,
and anyway take up no space compared to what he has, and the OS
optimization would only happen if more than one application was
running which used the framework, which is probably rare... again,
it's not that I am not all in favor of shared resources, but the
advantages are hardly measurably, but the advantages of putting the
framework in the app bundle certainly is, and there wouldn't be
version problems either (e.g. what if an older version of the
framework were already installed?) :)
Frameworks are designed to avoid these conflicts - you can have
multiple major versions in the same framework, so you can "upgrade" an
existing installation without breaking any existing users which may
depend on the older functionality.
Wade Tregaskis (aim: wadetregaskis)
-- Sed quis custodiet ipsos custodes?
_______________________________________________
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.