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: Allan Odgaard <email@hidden>
- Date: Thu, 10 Jun 2004 10:30:02 +0200
On 10. Jun 2004, at 10:04, Nicko van Someren wrote:
Preferably you should ship your application on a disk image and allow
the user to drag the application to where ever he wants it (including
the trashcan if he no longer wishes to use it).
While installing using a dragable application icon is clearly
preferable
Another advantage is that the application can easily be moved around,
either copied to a friend (or another computer in the household) or to
another system disk.
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.
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?) :)
I am inclined to use a package installer in this case but I'd be
interested to hear if anyone has got a better plan.
If I really had a suite of 5+ programs and they all used the same
framework, and that framework was larger than maybe 2 MB, then perhaps
I'd do the package installer, although I would probably try the thing
about having them in a directory with a frameworks folder (or perhaps
library folder, that way I could also ship them with some shared
application support data or similar).
_______________________________________________
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.