Re: Xcode's Find in Project
Re: Xcode's Find in Project
- Subject: Re: Xcode's Find in Project
- From: John Daniel <email@hidden>
- Date: Mon, 19 Feb 2007 10:26:59 -0600
On Feb 18, 2007, at 10:10 PM, Laurence Harris wrote:
Then I think you're just lost. LOL I know a lot of people who hate
Xcode's Find in Project window.
I think if any of us cared that much about what other people though
we'd all be using Windows and Visual Studio :)
- It doesn't have an option to put the results of searches in their
own windows. This becomes a real pain when I want to work with the
results of multiple -- but related -- searches at once. The current
implementation makes about as much sense to me as only being able
to view the contents of one source file at a time. I know I can use
the drop down history to switch back to the results of other
searches, but that list only contains the text for which you
searched. If you searched for a term once in your headers and
another time in your source, there's no way to distinguish the two
in that list. This is a serious shortcoming in the Find in Project
window.
- There's no simple way to just search a folder. To do that you
have to open the Options dialog and use or create a find set.
- In general the whole business of having to use a second dialog to
set up searches is klunky. Maybe you're used to klunky, but I've
been using Macs for a long time and I'm used to more elegant ways
of doing things. Many of the options in the Options dialog should
be in the main Find in Project window so that a) I don't have to
open a separate dialog to use them, and b) using an option one time
doesn't require the use of a find set. Sure, I could create a whole
slew of find sets to cover everything I might want to do, but the
more of them I have the harder it is for me to remember what each
one does unless -- you guessed it -- I open that second stupid
dialog and look.
I really don't get it. You think Xcode is clunky and prefer
CodeWarrior's find? I never used the MacOS X versions CodeWarrior so
I don't know if they improved it. But the Classic versions of
CodeWarrior had a truly awful Find feature. I remember there were
several clicks and selections you had to use. If you wanted to search
headers at all, you had to manually choose them.
- There's no Replace All option. You have to do a search first,
then do a replace on the results. I've never seen a text search
window in any other application, be it CodeWarrior, Word, BBEdit,
whatever, that didn't have an option to just replace all
occurrences directly, without having to do a search for all
occurrences first. Even Xcode's Single File Find window has a
Replace All button. Certainly there are times when the Xcode way is
handy, but the normal approach also has value and when that's what
I want to do, the Xcode way feels awkward.
I like the Xcode way. If you make a mistake in Single File Find, you
can just undo. What happens if you do that in Find in Project? For
multiple files, I like the (one) extra step.
- There's no way as far as I can tell to find the first occurrence
in a multi-file search. In CW you could find the first, do whatever
editing you wanted to do, and then find the next occurrence whether
in that file or another. That came in handy sometimes and I miss
it. CW had Find and Find All buttons.
Didn't CW open up every file with a find result in a new window? I
seem to remember having to type Apple-S, Apple-W 27 times in a row.
Maybe there was a close all. I don't remember for sure. I really
haven't used CW much in 5 years or so. I definitely remember that
Find and Replace was the one thing I didn't like about CW. I also
know it is one of my favorite features of Xcode.
I think your complaints are more nits than serious shortcomings. Does
the Find in Project feature actually get in your way every day? And
is there no acceptable workaround? That is my criteria for "serious
shortcoming". There are very few parts of Xcode that get in my way on
a regular basis. The only thing that really comes close is the
debugger, and that is just GDB. There isn't much Apple can do with that.
John
_______________________________________________
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