begin quoting Paul G. Allen as of Sun, Feb 20, 2005 at 04:32:59PM -0800: [snip] > >Dunno about the rest, but most of 'em are abhorrent because they provide > >such a crappy editor. I don't _want_ and editor that forces me to grab > >the mouse, for example. > > Both Understand and Code Forge allow you to use the editor of your choice. > The Code Forge editor has several modes it can operate in (including vi > emulation - one of the original modes it ever used IIRC) as well as > programmable hot keys.
How /good/ is the vi-mode? Most of the time such "modes" tend to be abysmal, and not worth the effort. Are you saying that Code Forge possibly did it "right"? > >Secondly, most of the IDEs I've worked with don't let you work on more > >than one file at a time -- sure, they have *tabs*, but I want to have > >two, three, four, or more editors open and visible at once. > > Both can do that as well. Good for them. That is _not_ at all the impression I get from the website screenshots, thank you for correcting my misperception. > >Third, using an IDE requires you to be present on the system, or to have > >a fast connection -- and a lot of UNIX people have spent years learning > >that the ability to log in remotely to work is a Good Thing[tm]. > > That is one drawback. If you don't have a fast connection, that running > them remotely is more than painful (I once ran Quake 3 remotely over my LAN > - it ran but boy was the frame rate low! :D ) I don't even like X over long network hops, even with a fast connection. > >The advantage of an IDE, as I see it, lies in the "lookahead" feature > >of the editor, where it will look up the possible methods for a class > >and let you chose the "correct" one, instead of having to guess or look > >it up. > > Understand has got to be my favorite tool thus far. It gave me a fast > enough understanding of the Linux kernel that I was able to make my Tyan > board (back when almost no one had a dual Athlon system and Linux ran like > crap on them) work with Linux. This is the reverse-engineering tool? I don't really see that as something that *needs* to be integrated -- cscope and cflow are early attempts at that sort of thing, right? > It also allowed me to get a fast handle on the software at my new job and > helped get me weeks ahead in my project. It's not really an IDE, though Aha! Okay. That makes a lot more sense. It didn't *look* very much like an IDE... > being extensible, with a Perl and C API, configurable menu and tool bar (I > can compile from a user configured command), it can be used as one, and I > use it as such. "Integratable" != "Integrated". IDEs are pre-integrated, thus the problem; tools that are loaded with hooks to extend the tool are another matter entirely. > >Syntax hilighting? Got it. Make from within the editor? Got it. Jump to > >the compilation error? Got it. > > Again, I have them as well. Naturally. Those are IDE "features" that don't require an IDE... -Stewart "And then there's the GUI vs Console distinction" Stremler -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
