Re: Xcode's Find in Project
Re: Xcode's Find in Project
- Subject: Re: Xcode's Find in Project
- From: Laurence Harris <email@hidden>
- Date: Sun, 18 Feb 2007 23:10:38 -0500
On Feb 18, 2007, at 9:21 PM, John Daniel wrote:
Larry,
I'm at a loss to understand why you say that.
Then I think you're just lost. LOL I know a lot of people who hate
Xcode's Find in Project window.
I think it is great and I literally use it all the time.
In fact, I was about to list my one and only complaint with the
Find in Project feature, but I thought I should test it again just
to make sure. (I don't want to sound like a dolt again after my
earlier FileMerge complaint). Sure enough, I can use Find in
Project to do a multi-file regex search and replace, complete with
back reference. I swear that I tried that before and it didn't
work! Oh well, it works great now. I have literally zero complaints
with Find in Project. I would go so far as to call it one of my
favorite features of Xcode.
What do you not like about it? I would certainly like to start
earning my fortune!
- 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.
- 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.
- 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.
Oh, and if Xcode supported putting search results in their own
windows, maybe Single File Find could have a Find All button.
Larry
John
On Feb 17, 2007, at 9:43 PM, Laurence Harris wrote:
On Feb 17, 2007, at 9:23 PM, John Daniel wrote:
Xcode's "Find in Project" is so much better than what Codewarrior
had. But this is now, that was then.
You must know ways to use it that elude many of us. You could make
a fortune running workshops if it would get us to the point where
we agree with your assessment. Personally I think (and I know I'm
not alone in this) that Xcode's "Find in Project" is the worst
Find window I've ever used.
Larry
.
_______________________________________________
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