KDevelop 3.0 beta 1 42
e8johan writes "The
KDevelop team has released the first beta of
KDevelop 3.0 a.k.a. Gideon (download
here). The GUI has been completely rewritten, support has been added for more languages, auto-completion, etc. Plus a bundle of improvements, the change overview can be found
here. Judging from the screenshots (
1,
2 and
3) it looks even more promissing than I dared to hope for!"
Error (Score:5, Informative)
Re:Error (Score:2)
I hope that I haven't caused to much inconvinience. But you must admit, it does look good!
Re:Error (Score:1)
Rick
Holy crap (Score:2, Interesting)
Gack! (Score:1, Interesting)
Sure, it may look more complete than before. But that is awful looking! Why would any developer use such an ugly look. I assume you can change the 'bubbley-ness' to the look with a different theme, but to put out screen shots that look like that?
It reminds me of winxp my sister-in-law uses. That look is not clean. I like defined lines! I like squared edges on buttons. I don't like bubbles. I do not lick my desktop.
Make it go away!
Re:Gack! (Score:3, Informative)
Re:Gack! (Score:5, Informative)
The last time KDE had a new default style was KDE 2.0. It came out [kde.org] in October 23, 2000.
Anyways, keramik is not exactly the default style. It's just one of the options that comes upon running kpersonalizer, which is run automatically when the user runs KDE for the first time.
Your math isn't exactly adding up.
> I have to agree with bubbles, looks good on OS X , but leave it there.
I don't like keramik either, but I support giving the user the right to chose whatever they want. Besides, keramik reminds me more of Mozilla's old modern theme than Aqua, anyways.
Re:Gack! (Score:2)
It wasn't supposed to, I was being extremely sarcastic. (it's monday for christ sake).
> I don't like keramik either, but I support giving the user the right to chose whatever they want. Besides, keramik reminds me more of Mozilla's old modern theme than Aqua, anyways.
I like choice, as much as anyone. But, I must admit.. I do believe that there is a point where less is more.
This isn't meant to spawn a flame thread, but your response was interesting and I would be interested to know what you think about the moving philosophy of simplifying gnome , in a less-is-more fashion. Redhat has definately done that with redhat 8.0, and I must say (after using it for 3-4 days) I -REALLY- like it.
I wish KDE would take that initive as well, though again I like what Redhat has done to 'cripple' KDE as well. (though, I find myself using gnome now exclusively).
Cheers
Re:Gack! (Score:2, Insightful)
Multi Language IDE (Score:2, Interesting)
This is extremely exciting stuff, I am not aware of any other IDE that let you develop in multiple languages AND multiple toolkits...if they are fully supporting those other languages and toolkits like they do with C++ and QT.....wow....I'm going to be using this for everything I do from now on.....
Re:Multi Language IDE (Score:5, Interesting)
On Linux maybe. You are aware that KDevelop is (more or less closely) tracking the Visual Studio IDE from Microsoft? It used to look A LOT like VC++, and with version 3 it's adopting the new VS.NET look and functionality, including the New Project dialog and the code expansion and collapsing features (the tree gadgets on the left of the code). Not that that's a bad thing, the VS.NET has some pretty neat features.
Re:Multi Language IDE (Score:5, Informative)
How about Eclipse [eclipse.org]?
The Java suppor is mature; the C/C++ [eclipse.org] tools are due for a release by the end of the month; and a Cobol [eclipse.org] tools project just got underway. "Unofficial" tools projects include Python [sourceforge.net], C# [improve-technologies.com], AspectJ [sourceforge.net], Eiffel [sourceforge.net], Ruby [sourceforge.net], and others [2y.net]
Re:Multi Language IDE (Score:1, Insightful)
the argument is that there are no other IDEs that let you develop in multiple languages and toolkits.
your response, Eclipse, and your explanation contradict each other. you even say it yourself: Java support is mature. C and C++ tools are not ready, Cobol tools just got started, and Python, C#, Aspect, Eiffel, and Ruby are all 3rd-party add-ons and not officially supported.
don't get me wrong, i like eclipse. I've used it periodically, but to say that it can handle multiple languages and toolkits is a bid misleading
Re:Multi Language IDE (Score:3, Interesting)
Ummm... it can handle multiple languages and toolkits. I'm using it for Java, C, and C++ development (multiple languages), and for testing cross-platform development. I've used it to compile a Linux kernel, build a couple of GNU utilities, and compile GUI apps using GTK and QT.
Languages support is better in some instances than in others. C/C++ is more than usable; I haven't used any other language features, but I've seen messages from folks actively developing those features and using those languages.
As for "Python, C#, Aspect, Eiffel, and Ruby are all 3rd-party add-ons and not officially supported"... Eclipse is an open source project under IBM's CPL. The only difference, AFAICT, between "supported" and "unsupported" projects is that "supported" projects have Eclipse consortium members devoting resources to them.
Other than that, everyone has the same code, everyone uses the same APIs, and the Eclipse core team is just as likely to take a patch from a Python feature developer as a CDT or Cobol team developer. Eclipse is usable for developing in multiple languages and toolkits now, and that level of support and usablity is only going to increase as time goes by.
Re:Multi Language IDE (Score:1)
In this case, Python parsing support is popping up, while Cocoa has enticed me away. So of course, there is only ONE SINGLE EDITOR on the planet (to my knowledge) that has parsing features for Objective-C (as in code completion and symbol information): CodeWarrior. Sigh.
Re:Multi Language IDE (Score:1, Insightful)
And if you don't think XEmacs is an IDE, then I can't help you.
Re:Multi Language IDE (Score:2)
How about some more bug fixes? (Score:4, Insightful)
Re:How about some more bug fixes? (Score:1, Informative)
Re:How about some more bug fixes? (Score:5, Informative)
Really, I'm not trying to flame, but this is Open Source, and I will repeat the thing that has been said several times: We do this in our spare time. Please don't complain about what we do in our spare time.
This isn't to say that you can't get the bug fixed.
Report it!: (Too many people don't realize that reporting bugs [kde.org] is important and valued!)
Fix it yourself: Hey, that's what this is all about! This is the developers section, and a thread about a development tool. You've got the source, go for it!
Pay someone to fix it: Seriously. Everyone thinks this a catch all, but many of the KDE developers, myself included would be willing to fix bugs for a modest price. Put EUR/$ 50 behind your request, and it's likely to happen! Hell, send a 6 pack of beer and you're likely to have a new friend.
I'm just trying to put this in perspective. The KDE devopers specifically, and most OSS developers in general do this for fun in their spare time. And here's another little secret: there aren't many of us. I would guess that 90% of the Open Source software that currently being worked on is developed by less than 500 people (That's just developers; there are a lot of wonderful translators and documentors out there too.).
We really try to produce great software, and in fact I think we succeed, but if you care about the stuff, please, help out! Donate something: time, money, hardware, whatever. It will be infinitely more appreciated and fruitful than complaining on Slashdot.
Re:How about some more bug fixes? (Score:2)
Well, it comes down to inertia. The thought of pouring over endless lines of someone else's code to understand its design and find the bug(s) would usually put me off doing what you suggest, but I might just do it anyway if I download Gideon and see that my pet bugs are still there. Even though that would mean interrupting a project to fix a tool, but what the heck.
Re:How about some more bug fixes? (Score:1)
Browsing through a top down/bottom up design hierarchy should make fixing the bug easy, and you'll know exactly how wrote the code in the first place if you need a hand!
almost and example:
project node Kdevelop
/ \
sub levels GUI Makefile
/ \
more sublevels.....
finally the class's at the bottom with there pendants and dependants
Class CheckSpelling{
private:
}
And the function you want
checkWord(...)
Designed by Bill, Haray and Bob
Written by Sally , Haray and Bob
Reviewed by Johna and Bill
Bugs todate 10
Parent Class CheckSpelling
Pendants...
Status...
Notes..
etc..
Debug Builds.. (Score:1)
e.g. Manrdakes packages KDE betas/alhpas never produce stack traces, even the ones from kde unstable.
If the distributions built unstable projectes with debug turned on then you'd get more, better bug reports.
Re:How about some more bug fixes? (Score:1)
How about some simple but nice additions like Go To Declaration, jump between declaration and definition, etc? Plus, it would be great to have some sort of macro capabilities inside the IDE, on a per-project basis.
You are aware that these paragraphs negate each other? What point were you trying to make besides, "I wish the developers would fix all the bugs I personally notice and still add all the features I personally want"? Well, join the crowd..
Usability? (Score:1)
At least I did that with screenshot 2 in my Win 98 (looks nice near TortoiseCVS)
Screenshots (Score:1)
Looking at the screenshots just now though (I know
Migration to/from IDEs? (Score:1)
Plug-In Editors? (Score:1)
That way all those former Windows developers could use a VS style editor and I could use a vi style editor and not worry about having my muscle memory taking over ;)
What Irony (Score:2)
lol
but what about.... (Score:1)
Re:but what about.... (Score:1)
Hmm Python support in the crystal ball? (Score:2)