• 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: How to create a easy of use Installer?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to create a easy of use Installer?


  • Subject: Re: How to create a easy of use Installer?
  • From: Nicko van Someren <email@hidden>
  • Date: Thu, 10 Jun 2004 10:53:50 +0100

On 10 Jun 2004, at 09:38, j o a r wrote:

On 2004-06-10, at 10.04, Nicko van Someren wrote:

While installing using a dragable application icon is clearly preferable, 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? 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 am inclined to use a package installer in this case but I'd be interested to hear if anyone has got a better plan.

How would you manage the case where you distribute one application with a new version of the framework but the user might have some other application around that expects an older version of the framework? Are you ready to handle the versioning issues and binary compatibility issues involved?

I'd be inclined to manage it the same was Apple does, with the version subdirectories.

What if the user moves to a new machine and just copies over his /Applications directory?

That's a very good point. On the other hand (to play Devil's advocate) one can argue this is a good thing from a copyright control point of view since the user will need to re-install on the new machine. Photoshop does this. It is however certainly a usability issue.

Personally I don't care about a couple of extra MB of disk space used (what you call "bloat") and a couple of extra KB of RAM used, for the convenience of knowing that the application is self contained.

Fair enough. The other thing I might do is put all the functionality into a single application and simply feature enable the parts.

OmniGroup distribues their applications with their frameworks inside the applications wrapper. I think you should do the same.

OK, I'll do it that way.

Thanks for the input,

Nicko
_______________________________________________
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.


References: 
 >Re: How to create a easy of use Installer? (From: Stéphane Sudre <email@hidden>)
 >Re: How to create a easy of use Installer? (From: Allan Odgaard <email@hidden>)
 >Re: How to create a easy of use Installer? (From: Nicko van Someren <email@hidden>)
 >Re: How to create a easy of use Installer? (From: j o a r <email@hidden>)

  • Prev by Date: Re: newbie questions about objective-c, ruby, python, groovy and cocoa
  • Next by Date: Re: drag and drop on Dock
  • Previous by thread: Re: How to create a easy of use Installer?
  • Next by thread: Re: How to create a easy of use Installer?
  • Index(es):
    • Date
    • Thread