/dev/null wrote:Anjuta is the bomb my friends, use it.
For the gentoo savvy, please note that it depends on a reasonble sized chunk of the gnome-base so if you have -gnome like me, prepare for a semi-lengthy compile.
I wasn't very impressed with Anjuta, sorry. ;( Main problem is that by default (and I couldn't figure out how to change it) C++ files have a .cc extension, and Visual C++ doesn't recognize them as C++ files.
Personally, I just use KWrite. I have a terminal opened for building/running, and I use Kwrite for source editing. Lightweight, syntax-highlighting (everything, literally, from bash scripts to python, html, php, c++, everything). The only problem is that you have to get intimate with your build system, but GNU's autotools really simplify that a great deal. It's worth it, I think, to spend the 10 minutes or so figuring out how to build Makefile.am and configure.ac. Also helps a lot to make sure you have certain expected files in your tarball, and once you've got it going, you can build release tarballs pretty easily.
Lately I've gotten the hang of python's distutils, and once I get the hang of writing C++ extensions to Python, I'll be all set. The advantage of Python's distutils, if you're using Python, that is, is that on rpm-based distributions you can do ./setup.py bdist_rpm and Python will use the rpm tools on your system to build an rpm that's compatible with your system automagically. It's beautiful. Now if only Python would support other packaging formats, I'd be all set. As-is, though, with good Python coding practices, an rpm you build on your system should install onto any other system (provided they have a program that'll install rpm's into their existing package manager, whatever it may be).
