Why use frameworks?
Why use frameworks?
- Subject: Why use frameworks?
- From: Randall Meadows <email@hidden>
- Date: Fri, 20 Jul 2007 10:22:53 -0600
Now that I finally have my project building with its 10 dependent
frameworks behaving correctly, and I think I actually understand
what's going on and why, I have a question:
Why am I putting myself through all this agony (granted, most of the
agony is passed, but still) with the frameworks? This project
actually has 2 parent application projects that both depend on most
of these frameworks, but the project files (I inherited them, I
didn't create them) actually embeds them into each built
applications' bundles, rather than installing the frameworks into
some common location (I don't want to ship an installer anyway, I
want the "installation" to be drag-and-drop). The two applications
work together as a suite, but in practice, the two applications will
be running on different machines, so installing frameworks in a
common location is impossible anyway. So I really don't see the need
for having so much code be in separate frameworks at all.
- It makes it harder for me to follow what's going on in the code
when debugging or simply reading the code.
- It seems to be fragile in that when I make a change that's going to
affect the frameworks, I have to make it in 10 different targets
spread across 7 project files, plus the application project itself.
- It seems to be more inefficient building.
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?
Thanks in advance for the enlightenment.
randy
_______________________________________________
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