Re: info.plist problem
Re: info.plist problem
- Subject: Re: info.plist problem
- From: David HM Spector <email@hidden>
- Date: Wed, 26 Dec 2007 13:21:38 -0500
David,
Sorry... braino... I misspoke.. I meant the plist utility, not gcc...
re: XCode3's layout.. I can see your point, and I am sure I have not
worked with it enough to really appreciate the depth of how XCode's
view of the project works... my impression is that for very large
projects with multiple targets (most of my apps have needed a very
flat structure until this latest one) it's bound to eventually bite
you since there is no relationship between where you actually have
files and how XCode maps them internally.
Since we're on a nice Unix machine which supports symlinks,
referencing things in disjoint folders or even across mounted
filesystems could easily be supported using them. It would also cut
down on the file copying that XCode does when you import a file or
library.
It also (as in lots of Apple's own examples, such as the CoreRecipes
example: http://developer.apple.com/samplecode/CoreRecipes/
index.html ) leads
to dragging references around to files that mimic their on-disk
presence but have no relationship to where the files actually are.
Of course, if you do move things on disk, you break the build and then
have to edit all the XCode references you've dragged to various groups
in the project too.
At the end of the day, its just a different style of doing things, but
the disconnect between form and function is jarring for a Mac
application to be doing since it violates what should be the
"Principle of Least Astonishment."
regards,
David
On Dec 26, 2007, at 11:42 AM, David Dunham wrote:
On 26 Dec 2007, at 07:18, David HM Spector wrote:
7) click Build ; get 1 Error gcc can't find the file
So is Info.plist still part of the target after your changes? And
why is GCC involved with it?
Of course this brings up another problem that I am surprised Apple
didn't fix with XCode3 - the disconnect between
XCode's faux "groups" and the actual layout on disk... IMHO it's
very frustrating and violates just about every HIG
guidelines the Mac has ever had... to say nothing of making the
management of complex projects really hard...
Not everyone shares your humble opinion. This feature makes the
management of complex projects easier, because it lets you group
things like "External Libraries" even if they come from a multitude
of disjoint folders.
Think of it as tagging if you like. Everything in the Resources
group is a resource. The fact that you may have a folder called
Resources is a mere coincidence.
David Dunham
Voice/Fax: 206 783 7404 http://www.pensee.com/dunham/
Imagination is more important than knowledge. -- Albert Einstein
_______________________________________________
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
----------------------------------------------------------------------------------------------
David HM Spector
spector at zeitgeist dot com http://www.zeitgeist.com
~ ~ ~
"New and stirring things are belittled because if they are not
belittled, the
humiliating question arises, 'Why then are you not taking part in
them?'"
--H
. G. Wells
_______________________________________________
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