Quote:
Original post by Prefect
What "entire concept" are you talking about? The "entire concept" of Anjuta (and KDevelop, and ...) is to create a good IDE. If you "don't like" that, I wonder what you're here for.
I guess our definition of the terms "good IDE" differ significantly. Anjuta is no good IDE, and neither is KDevelop. Here, I'll give you a quick rundown over what I dislike about Anjuta (from the top of my head, there are probably many more subtle points):
* Its complete reliance on an obsolete and crappy build system
* The lack of any working source tree management (forced autotools source structure, no virtual tree, etc)
* No multiple dependent projects and targets within a solution
* The fact that the interface customizability is exactly zero
* The GUI is clumsy and confusing, and doesn't support an efficient workflow
* The debugger integration is very bad (this also applies to other external tools, such as gprof, valgrind, etc).
Basically, it's messed up beyond hope (well, according to my definitions ;) Fixing it by a fork would be more work than starting a new IDE from scratch.
Let me state it like this: Anjuta & KDevelop are nice IDEs for the amateur developer, that adheres to the GNU development style. But they are not usable for more complex and professional projects. Eclipse is different in that respect. I would definitely classify it as a professional IDE, but it comes with a lot of other problems (bloat, stability, missing features).
Quote:
Original post by Prefect
In fact, I would argue that the build system is actually one of the *least* important aspects of an IDE.
Tell that the project managers at any large software company ;) The build system is actually an extremely important part of an IDE. Even more important, is its tight integration into all other tools, such the editor and debugger.
This is actually the magical two words: seamless integration. That's what pretty much all Linux IDEs lack (except Eclipse). They're more a patchwork of tools that were thrown together, and lightly coupled by the IDE. Many current Linux IDEs are nothing but a graphical frontend for autotools, gdb and make. And this is not what an IDE is supposed to be - it is supposed to tightly glue these tools together, so that as a user, you don't even feel like using separate tools anymore.
Quote:
Original post by Prefect
And I don't see you mentioning anything at all about debugging (which is where current Linux IDEs are most lacking IMO).
No, I didn't mention it explicitely - because I saw it as a given. An IDE without good debugger integration is no IDE, yet good debugging support does not exist in Linux IDEs. It's as simple as that. A big problem is GDB - it's a pretty good debugger kernel, with a horribly broken interface. We are trying to achieve a seamless integration with the IDE, in the style of MSVC, yet with more debugging options (in the style of Watcom's excellent debugger). As I said, GDB offers a lot, it's just a pain to interface with it in an efficient manner.
EDIT: BTW, if someone would like to help with the GTK stuff, I just created a topic in
Help Wanted.
[Edited by - Yann L on February 20, 2005 6:08:48 AM]