• 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: Wade Tregaskis <email@hidden>
  • Date: Thu, 10 Jun 2004 19:44:17 +1000

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?

As I mentioned in a parallel post, this should not be a problem given the provisions for versioning built into the frameworks scheme. Namely, major versions which may well break previous functionality can co-exist with each other, so each "generation" of framework users can happily do their thing. Minor versions should not, by definition of minor, introduce any changes which break existing functionality.

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

What if the user's on dial-up and doesn't particularly like having to spend an extra three hours downloading your app?

It seems self-defeating to create frameworks, and then include them only in your app bundle. Why not just compile it all into one amorphous blob and not waste the extra run-time of linking and so forth?

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.

As someone with a frequently slow net connection, too little disk space, and far too little ram, I have a few words to say against your cares. :)

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

And OmniWeb used to be 25 meg or so. It's now 15, since moving to WebKit.

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.


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: How to create a easy of use Installer?
  • Next by Date: Re: NSToolbar with multiple lines?
  • 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