Favorite IDE/editor for Qt
-
[quote author="Ivan" date="1283077985"]
Wasn't QtCreator's FakeVim based on Kate's (GSoC project from while back)?[/quote]No, it's a completely unrelated code base.
[quote author="Ivan" date="1283077985"]
[quote author="Duck" date="1283074460"]
Just typing :vsplit actually works.
[/quote]Yes, I saw. But I have no idea in which version it was introduced. And it behaves a bit odd when you want to close a split with :q - it leaves the splits, but closes the current file (and all splits that used to show it, become empty)
[...]
From my point of view, if the above (vim-like-scripting) was implemented, the actions could have a default qtc_ActionName ex command, and we could define comething like this in .qtcreatorvimrc (or wherever)@:command MyCommand call SomeFancyFunction(...)@[/quote]
The "odd" closing behaviour is inherited from Creator core. :make also works directly, :imap works at least for a limited set of actions, and regarding "if Foo was implemented...": FakeVim is really easy to get involved with, with more than a hundred contributions from outside Nokia so far.
I do agree that having a "standardized" way to access Creator core functionality would not hurt, on the other hand, hard-wiring, say :vsplit to the respective core action is only three lines, so there has to be a few hundreds of such cases of interaction to make implementing a generic interface worth while.
-
[quote author="Duck" date="1283097413"]... and regarding "if Foo was implemented...": FakeVim is really easy to get involved with, with more than a hundred contributions from outside Nokia so far.[/quote]
I know, but unfortunately I have too much already on my plate with KDE and my PhD studies so I can't really do this as well.
The only way I can currently contribute is by suggesting improvements.
-
For any complex project, Eclipse is still my IDE of choice. Due to its extensibility you can rely on additional tools for a lot of tasks, e.g. you can add XML editing with automatic XSD validation and auto-complete support or seamless integration with bug tracking tools.
The only major feature I am missing in Eclipse compared to QtCreator is its automatic parsing of Qt objects into meaningful output when debugging. But apparently someone is working on that for the next CDT release.
-
Kdevelop 3.5 with Qt Designer plugin is the best most powerful combination ever. I am new to QT Creator and I like it's automatic slot/signal features and the really good and stable UI. However Kdevelop 3.5 is extremely powerful with integrating all kinds of documentation from whatever library. I sometimes deal with chip vendors and their libraries (on top of other proprietary and open source libraries). Being able to just plugin a documentation and have it appear as you type is awesome. Even Kdevelop 4 is not as good as Kdevelop 3.5. Kdevelop 4 left out many key features kdevelop 3.5 had. I hope KDevelop 4 and QT Creator inherit those features from 3.5.
With QT Creator I haven't figured how have the libc, boost and other common library functions and classes appear as I type. I am not even sure what kind of documentation formats it recognizes. -
Qt Creator, my favorite feature is the integrated Qt documentation and with FakeVim I don't miss vim at all.
-
I have been using QtCreator for almost 3Years,and i can say i got addicted to it.Now the current projects requirement is MSVC2008 with CMake,i have convinced my manager with QtCreators ease of use,and now he started using it,Im using MSVC2010 at office,and CodeBlocks at Home.
-
I normally develop on a Mac, and then test on Windows and Solaris. Qt Creator is about the only tool that works across all these platforms (Java IDE's NetBeans/Eclipse would work too, but they are too heavy). That said the editor features are very poor compared with MSVS especially VS 2012 (which frankly is the ultimate for C++).
-
[quote author="sptrakesh" date="1360793058"]I normally develop on a Mac, and then test on Windows and Solaris. Qt Creator is about the only tool that works across all these platforms (Java IDE's NetBeans/Eclipse would work too, but they are too heavy).[/quote]
I like QtCreator for the same reasons. At work i have a Windows at home two kinds of linux and one Windows. When i workin on some project i don't care about OS and just start develop on same project without any changes. -
sptrakesh: What makes MSVS better for C++ development than Creator? Which features do you miss the most? What should we improve to make it more appealing to MSVS users?
-
Can i tell few things about code editors(Not whole IDE)?
Code collapseing is still not perfect in QtCreator, frequently its lose entry points. Only reopen a file solves problem, but all code blocks are become expanded. Somehow MSVS remember all settings even if reopen whole project. Besides i didn't find commands for collapse all and expand all in QtCreator.
Next useful thing in MSVS editor is #regions, it is very convenient.