Re: Why use frameworks?
Re: Why use frameworks?
- Subject: Re: Why use frameworks?
- From: "Philippe Casgrain" <email@hidden>
- Date: Fri, 20 Jul 2007 13:08:20 -0400
- Thread-topic: Why use frameworks?
Randall Meadows wrote:
> Why am I putting myself through all this agony (granted, most of the
agony is passed, but still)
> with the frameworks?
[...]
> What argument would you give that would convince me to keep this
layout? Why *shouldn't* I
> simply include the frameworks' source files directly into the
application project build?
That really depends on your application(s), and what you are attempting
to do. Is reusing this code across applications useful? Especially
applications that you did not write?
My own example is Painter, and in it we have:
- 6 static libraries (individual Xcode projects that compile to .a files
that are linked in the executable)
- 2 plug-ins (Spotlight and a Carbon/Cocoa bridge)
- 2 embedded frameworks
The 2 embedded frameworks *could* be static libraries, but they are
designed as re-usable frameworks so that we could (eventually) ship a
SDK to allow third-parties to read/write Painter files.
Right now, there is no direct benefit to have embedded frameworks. But
it forces us to think about what we want as an independent, re-usable
piece of code that could (eventually) go to third-parties.
And it is not that much more trouble to debug, if you have a common
build folder.
That being said, I also agree with Wil Shipley
<http://wilshipley.com/blog/2005/11/frameworks-are-teh-suck-err.html>:
for your own stuff, that is not likely to be re-used, static linking is
easier.
Philippe
_______________________________________________
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