I haven't done c++ for a while, but when I did I used anjuta. Probably worth checking out.
On 6/7/07, Chuck Esterbrook <[EMAIL PROTECTED]> wrote:
On 6/7/07, Lan Barnes <[EMAIL PROTECTED]> wrote: > > On Thu, June 7, 2007 3:44 pm, Stewart Stremler wrote: > > begin quoting Lan Barnes as of Thu, Jun 07, 2007 at 12:14:59PM -0700: > >> I had a sig in an old sig file from an uber-developer to the effect of > >> "I'd crawl across a hundred yards of visual-this and integrated-that to > >> get to gcc and gdb on a console." > > > > A compiler, a console, and a decent editor. > > > >> I guess to some people Alt-F[2-6] _is_ an IDE. > > > > It worked for me, back in the day. > > > > Let the record show that Stewart was not the uber-developer in question. > But I thought of vi (and how much I hated it when I first was learning it, > and how much I love it now) as I typed. > > Have I ever told this list how hard it is for me professionally not to > puke when windoze developers whimper and whine when they're asked to use a > code archiving/issue management tool that isn't actually integrated into > their precious IDE and they have to actually _switch windows_? I remember > how one supposed professional (blessedly out of my life now) wasted 20 > minutes in a tool-search meeting calculating how much "creative" time he > would waste if it took him 2.5 seconds to toggle between his IDE and the > Perforce GUI. I wanted to say "WHAT ABOUT MY DAMNED TIME IN THIS MEETING, > BOZO?" but of course, I am far too professional for that. Yes. And mature. > Far too mature. So... what was the total time he would have wasted? :-) I used Perforce briefly and my jaw hit the ground when I found out that Perforce couldn't even remember what repository and path a local workspace came from. You had to tell it! Each time! Don't know if they still have that problem. Subversion knows where its files come from. Even CVS can do that. (Yay, let's start a source code control flame war! ;-) -Chuck -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
-- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
