KDevelop4 Beta 3 Released

mikesd81 writes "KDE announced on May 30th the third public beta of KDevelop4. Some new features include a new code-writing assistant, a new documentation plugin showing you the API docs for Qt and KDE APIs, a reworked Mercurial plugin, and a rewrite of the classbrowser plugin. Two plugins from the KDevelop source, QMake support and Qt Designer integration, were let go and moved to the KDE Playground area."

Comments

code writing assistant

[Anonymous Coward]

I already have a code assistant, he's called Intern 1.0, he does all the shit work I don't want to do, and when I don't know how to do something, he figures it out, lays out the algorithm for me, and then I take the credit.

Since he doesn't have a family or girlfriend, he also works about twice the number of hours I do.

I don't see how KDevelop can improve on that.

Fantastic

[12357bd]

Maybe the best free C/C++ IDE. For other languages old & true Netbeans or Eclipse without a doubt, but for C and C++, it's the only one me.

Thanks!

Re:Fantastic

[HatofPig]

Highly recommend that everyone scroll through tons of pretty screenshots and feature lists on this developers blog which will give you a way better idea of how awesome KDevelop is going to be than the summary links will.

kdevelop is great

[iplayfast]

Last week when everyone was talking about their favorite ide's I kept thinking that kdevelop should have this or has that.

It's the one IDE that I've used for Linux development (besides vi) that I've used for years. I'm looking forward to the new class browser.

Re:STL container visualization...

[Anonymous Coward]

Why can't I stuff auto_ptr's into STL objects? I always get leaks.

Watcom C++

[moon3]

I love KDevelop/GCC, but it is also nice to have some options. The massive reliance on GCC is becoming tiresome, especially if it still under performs, newest Intel's and Microsoft compilers are faster and produce better code..

The good old Watcom was rock solid compiler producing one of the best binaries at the time, also comes with good debugger and even decent IDE. It is open source now, see www.openwatcom.org. It has a stellar source base and potential to spawn another cross platform compiler to compete with GCC. It would be nice if we could swap GCC for something else.. This great and promising project needs developers badly!

Do not forget, it is Watcom that compiled and gave us Duke Nukem, Doom, Termial Velocity, Frontier and all the DOS4GW titles.

Re:Watcom C++

[ardor]

Intel's icc is a collection of special cases. If your code does not fit into this grid of special cases, it will be slow.
Your actual answer is called LLVM.

Re:Watcom C++

[Rob Riggs]

Yes, when Intel and MSFT make compilers that target UltraSPARC, Itanic, and POWER (all, not some) then I'll have a look-see again.

Open Watcom enjoys virtually no support. It is not going anywhere. It's another sucky piece of code that was no longer competitive in the marketplace. It needs developers like a fish needs a bicycle. No one in their right mind would waste time adding support for this compiler to KDevelop.

You know, the only people that I know that seriously dislike GCC are the commercial compiler venders. It's not perfect, but it has a major advantage that no other compiler has -- it frees the developer from worrying about vendor specific compiler issues when writing cross-platform code. One less thing to worry about.

Re:Watcom C++

[Kjella]

You know, the only people that I know that seriously dislike GCC are the commercial compiler venders. It's not perfect, but it has a major advantage that no other compiler has -- it frees the developer from worrying about vendor specific compiler issues when writing cross-platform code. One less thing to worry about.

To me it's basicly like this - either the compiler's performance hardly matters at all, the code's performance is restricted by user speed, network speed or whatever OR it's incredibly performance oriented. If it's incredibly performance oriented, typically someone will make an assembler library that does that as efficiently as at all possible. Compiler performance is for the inbetweens where it's sorta important but not important enough. If you hit a performance bottleneck, very often it's a higher-level code issue that's better fixed there. The number of real-world cases where you really say "the code is good, the compiler's stupid and it's important yet not too important and changing the compiler is the difference between acceptable and not acceptable" is really low. There's a million things I could take issue wtih when it comes to open source, but gcc is not one of them.

Re:Watcom C++

[d43m0n13]

Actually, KDevelop (at least version 3) has a very nice Intel C++ support, and Sun's compiler (whatever it's called nowadays) support too, I think. Even if KDevelop didn't support a particular compiler, the only thing missing would be the jump-to-error functionality.

And Watcom, is, well, irrelevant (ISO C++, anyone?).

Re:Will we get another "don't use me yet" "release

[ultrabot]

Seriously, someone needs to find who wrote the fucking memo that says you can have all the regressions you want as long as your applications use Qt4.

It's a new app, there is no such thing as a regression. Same applies to many other KDE4 progs.

That being said, C++ intelligence for KDevelop4 rocks. Too bad it's not as stable as Qt Creator yet (so I already sort of jumped the ship).

For kdevelop4, perhaps they could consider the approach taken by emacs for gdb integration as "competitive" measure- i.e. just act as all-singing, all dancing code showing frontend for gdb, with normal gdb console visible at all times. For many scenarios, dumbened frontends just can't hack it.

Re:Typical FOSS

[ultrabot]

Other than that... Nothing can match Visual Studio. Period.

It's not necessary to match Visual Studio. It's important to be good enough. Many programmers are still relying on non-IDEs, so VS level operation is far from necessary.

I don't recall having an open source linux-compatible version of Visual Studio.