Linked by Eugenia Loli-Queru on Tue 3rd Mar 2009 10:55 UTC
Thread beginning with comment 351650
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
They both have different goals, that's why you should not compare them. Qt-Creator is minimalistic and special purpose, and the developers said it themselves: They don't want to compete with bigger solutions like eclipse or kdevelop.
But it just doesn't seem too hard competing with other C++ ide's, since qtc already has 1) intellisense, 2) gdb integration, 3) context based code navigation. If what remains is just parsing some project files to determine what source files are part of the project, it's not a stretch to assume that some qt creator fan will want to add that stuff to the app (it's open source after all).
I choose my tools with the lowest work overhead and in the moment that is Qt-Creator for Linux/MacOSX and VC2008 + VisualAssist on Windows.
Ditto. ATM it's kscope & gdb (because of what the environment dictates - a non-ide seems to be easiest to manage in scratchbox environment). I'm keenly following where the next gen IDEs will take us (qt creator broadening its scope, kdevelop4 coming out, CDT maturing up). Good times ahead - a while ago kdevelop was the only one worth using at all.





Member since:
2006-07-12
Because they are both IDEs?
"
They both have different goals, that's why you should not compare them. Qt-Creator is minimalistic and special purpose, and the developers said it themselves: They don't want to compete with bigger solutions like eclipse or kdevelop.
kdevelop doesn't need to parse your qmake files - you can easily import the project with "custom buildsystem".
I work on a multi platform project with 56 subprojects and unit tests with over 1000 files. As long as I had a working qmake project manager I could add/remove files out of kdevelop and select the project to debug and so on. I cannot not do that as comfortable with a custom buildsystem.
I choose my tools with the lowest work overhead and in the moment that is Qt-Creator for Linux/MacOSX and VC2008 + VisualAssist on Windows.