Re: Why use frameworks?
Re: Why use frameworks?
- Subject: Re: Why use frameworks?
- From: Mike Blaguszewski <email@hidden>
- Date: Fri, 20 Jul 2007 14:44:10 -0400
We use frameworks here at Ambrosia for similar reasons to what
Olivier mentions. We have code that gets shared across multiple
products, and it's nice to have a modular component that can be
dropped in to any given client app. The framework I work on has its
own nibs, other resources, a custom build phase to embed 3rd-party
dylibs, even its own initialization routine. That would be a pain to
set up for every product that uses it.
You've also got to consider maintenance. If you're dragging source
files and resources into multiple projects, it's easy to fall out of
sync when the shared component changes. If the component is in a
framework, you just recompile the framework and you're all set.
In your case, a compromise might be to consolidate into a single
embedded framework for all your shared code (even if everything isn't
used in all apps). And cross-project references can help with the
build hassle.
--
Mike Blaguszewski / Cocoa Hacker / Ambrosia Software, Inc.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden