Re: XCode usable? Part II
Re: XCode usable? Part II
- Subject: Re: XCode usable? Part II
- From: Dix Lorenz <email@hidden>
- Date: Wed, 5 Nov 2003 09:54:35 +0100
My post was too big, so I divided it...
On 04.11.2003, at 19:22, Scott Tooker wrote:
In PB it was reasonable to use the project-window for just the tree
and not having an editor right next to it, basically working as you
would in CW. In XCode it isn't: I know I can collapse the editor-part,
but when I have compile-errors, I have to doubleclick the file in the
projectwindow, scroll until I find a small red "x" and hover with the
mouse over it to see the tooltip. Or use the buildwindow, but the
editor there is gone, for no reason I can think of.
You might try cnrtl-cmd-opt-down arrow to go to the next "detail" (in
your case a warning or error) (previous detail uses up arrow with same
modifiers). I think this was working in Xcode 1.0 (if not, it should
work in the next version).
It sometimes works, when the editor-part is open, which I don't really
like. Otherwise it doesn't do anything. I have to switch back and forth
to the build window, which after the first fix is behind my editor
window... Very inconvenient.
We've also added markers in the scroller for
warnings and errors in the next version.
Okaayyy... But why not also put back an editor in the build window? The
code can't be too hard (it is basically all there already), people
using the "big" project window won't notice and people using the
collapsed project window are back to using the Build Window the way
they used to. Although I kind of like that "Errors and Warnings" smart
list in the Project window... I see no reason, why that can't go into
the build window too. Maybe as a drawer?
And why can't I set the active target and/or buildstyle in the
buildwindow? That one is usually big enough to handle two popups. My
collapsed Project window isn't. Again: No reason I can see to not give
the user the ability to set these there.
I've also stumbled about most of the bugs others saw, had one project
corrupted... It is the buggiest release of anything I've yet seen from
Apple. Luckily the bugs usually don't destroy data, but working with
XCode is more of a fight than it should be.
So far I'll have to say I am pretty disappointed. Usability is way
down from PB and I can't attribute that only to me being used to PB or
CW. It tries to force me into a direction I don't like. The
iTunes-metaphor is not good for everything and I'd say an IDE is one
of the last places where it's the best solution.
The new UI really lives or dies on the use of the search field. If you
like the search field and use it, then I think the UI becomes very
powerful. However, if you don't use the search field then you may be
happier just collapsing the project window to just show the group view.
I like the idea of the search field. But I usually want to have about
4-5 files open, 2 or 3 next to each other, maybe another 2 on my second
display... I just don't like to have one big editor. I know even with
the expanded project window I can create new windows, but that quickly
becomes an ugly mess of two different metaphors and just feels "weird".
I'd like to be able to have a window with that search field, but not
"attached" to the project tree. Basically I'd like to have the project
window as two different windows. Of course, with the option of multiple
"Searchfield-Windows"...
I am little relieved now, from what you have said you are not only
fixing bugs but also aim to improve the UI. One question though: How do
you (does Apple) see XCode? As the next version ProjectBuilder or as a
completely new product? Up to now I saw it as the next version of PB
and that would mean it is going in a direction UI-wise that I
absolutely don't like and some things are IMHO objectively worse than
in PB. That would be a bad direction. From your mail it seems more like
a completely new product, which has the usual growing pains and where
parts of the UI are not thought to be the better version of the way it
was in PB, but more of a stepping stone until a better solution has
been found. In the first case I would be worried, in the latter I'll
just keep hoping for the next XCode: a lot of bug fixes, an improved UI
and a release date way, *way* before 10.4...
My biggest concern is that users like me who don't like to work in one
big window but prefer to use more windows will be forced to work with
the big project window. I never really used PB until 2.0 (?), where
there was an option to choose between single Window, more windows and
many windows (or something like that). Or even to custom-build the
windows to your liking. I thought that was an amazing way of satisfying
all kinds of users, no matter what they are used to or what they
prefer. Before PB 2.0 I did all my editing in CW and the compiling and
building in PB.
I really *want* to like XCode and I am sure a lot of thoughts, ideas
and hard work went into it. I am just concerned that the tool I will
probably be using the next few years has just acquired a lot of the
things I've hated about MSVC for years.
Thanks,
Dix
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.