Re: WOLips: 80 character width gutter?
Re: WOLips: 80 character width gutter?
- Subject: Re: WOLips: 80 character width gutter?
- From: Marc Guenther <email@hidden>
- Date: Sat, 26 Jan 2008 14:37:52 +0100
On 23. Jan. 2008, at 2:15, Art Isbell wrote:
On Jan 22, 2008, at 2:45 PM, Thomas wrote:
Surely I'm not the only WOLips user who wants text wrap just like
in TextEdit?
Prior to Eclipse, I don't recall ever using a source code editor
that didn't support soft wrapping including vi and emacs way back
in my System V Unix programming days...
Exactly. Eclipse is quite notorious for succeeding in things i would
have never dreamed possible (there is so much magic in Eclipse, that
I am convinced I will never be able to work with any other IDE
again), while completely failing in the most trivial of categories.
When I first used Eclipse, I felt stupid, because I didn't find the
setting to enable soft wrapping. I asked our local Eclipse guru (a
Windows guy) and he didn't know either. In fact, I'm not sure he
really understood what I wanted (soft wrapping?). That was the first
time I actually considered the completely insane idea, that Eclipse
really does NOT support soft wrapping. Took me several hours till I
could finally believe that this is in fact the case.
Now its four years later, and Eclipse still does not have soft
wrapping (and now I work at a company, which enforces a 80 character
width rule, ahrg). It still does not have a working double click'n
drag behaviour (although I provided working patches, well, at least
it works for me now :) ). The FindPanel is so unusable that everytime
I want to find/replace something, I copy the entire file into
SubEtha. The editor tabs are constantly jumping around to positions
where I least expect them (but they do this so reliable that at some
point you get used to the fact that they are not where you expect.
Isn't that ridiculous?). The CVS Synchronization view flags normal
and completely harmless concurrent modifications (= the C in CVS) as
red conflicts and I still haven't figured out how I am supposed to
fix the REAL conflicts in the Compare view (I'm using CVL and
FileMerge for that).
Back then, one of our developers refused to use Eclipse, cause he
couldn't select a method name, and then Cmd-E Cmd-G to its
declaration (probably opening lots of promising looking files in the
process). That was what he was used to use. While I would certainly
like to have Cmd-E functionality in Eclipse (and a FindPanel which
remembers what I typed into it), I prefer to simply press F3 to go to
the declaration of a method. Or Ctrl-Alt-H to find from where its
called. Or whatever...
I remember a full build used to take almost half an hour with
ProjectBuilder. In Eclipse, it took 4mins, and then, when do you ever
need to do a full build in Eclipse? It was quite common for a
developer to break the nightly build, cause she committed a low level
change which wouldn't compile in a dependant framework. Which meant
half an hour coffee break for everyone the next morning.
In Eclipse, everything is always built. No manual builts, no missed
compilation warnings, all dependencies magically taken care of. I am
now so used to this, I wonder how any IDE could be taken seriously
which doesn't provide that kind of build integration. Yet at the
time, it was revolutionary. So revolutionary, that most in our team
didn't understand it, and stuck with their, ah, this is so ugly, its
one huge window, it doesn't do everything 120% as I'm used to do it,
how can you stand this thing, whining.
I wonder what will happen to me if I ever have to use Xcode again :-)
Marc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden