The KDevelop team would like to announce the availability of KDevelop 3.0 Alpha 1 (also known as Gideon). This represents a complete redesign of KDevelop and includes tons of new features, and a new interface. Available through KDE ftp mirrors, the KDevelop web site and CVS, Gideon brings out the best in what an Integrated Development Environment should be. Users of KDevelop 2.x will notice substantial improvements, while new users will be amazed at the flexibility and extensibility put into this program. Improvements include: pluggable parts, rewritten Automake/Makefile.am support, support for more programming languages (Java, C, PHP, Perl, etc.), better code completion support, source code control integration, and more! Users wishing to experiment with these new features are encouraged to download this version and report bugs. Of course, the team is always looking for help. Screenshots: (1,2,3).

Comments

I must have gone to some weird inverted dimension where everyone has long hair in the neck and the Keramik style is the ideal all UI-designers strive for :)
I really don't mean to offense the author, or start a flamewar, but this has been bothering me since I first saw a screenshot of this style. Is Keramik still planned to become the default style for KDE 3.1(style and decoration)?
I haven't really said anything about Keramik before because I didn't really want to offend anyone, I just switched to GNOME when I first heard that Keramik would become default, and figured the end is nigh for the KDE project. (I'm now a happy KDE user again) But if everyone just sits and pretends that everything is fine, the project wont evolve, so even if my opinion is useless, It still had to be said, and the screenshots of KDevelop 3.0 just happened to remind me. However, Keramik really seems to be popular among the majority of KDE users, and I guess that's all that really matters.
Btw, the nicest window decoration I've seen ever (IMHO), is this one: http://kde-look.org/content/show.php?content=2865&PHPSESSID=44c18ce5f7c4...
I really hope this one get's included in future KDE releases.

I didn't really think that the end was nigh :) I just got a bit carried away in the post, and as for GNOME, I just needed to try something different for a while.
Perhaps I went a bit over the top, Keramik isn't really THAT bad, it just clashes real bad with my taste.
Since the Crystal icon theme has begun to look really good, I guess there's still time for some improvement's on the Keramik style.

I must add, despite looking really XP-ish, the Connectiva Crystal Icon theme have really begun to shape up, I used to hate it, but now It's becoming very very nice :), just take a look at some of the "new" device icons, and the kscd and noatun icons for some examples of some beautiful icons (Crystal 0.7).

hi,
last week i started teaching linux in an class. how should i teach these windowsonly users linux?
of course we began with history, licence, harddiscpartitions etc after installing suse linux and playing araound a little bit i wanted to go to the console. no, i didnt start with vi. first motivate these people!
ok. teaching console handling plus tar, unzip,, rpm, cp, rm etc but how: with boring archives?
ok going to www.kde-look.de downloading styles (yes even the kde-xp style) and doing this stuff with the; Whoo. thats like we are used to do!

and YES: a cool looking desktop is IMPORTANT for newbies (and for me too).
every linuxguro can easely switch to a clean style, but the normal user wants this.

AND: i like it very much. yes one important reason to compiling kde 3.1beta was the keramik style.

Yeah, the new push towards highly prettified user interfaces is a real problem IMHO. Exactly what do transparent menus achieve, apart from making them harder to read? What do the great bloblike buttons achieve except take up more real-estate and introduce extra graphics that distract the eye?

Uh....
I believe KDE will continue to
deliver simple styles like the 'light style' or the .NET-style
There is a whole bunch of simple styles available. All of them
do not contain 'overload' like transparency and this stuff...
This means: By making the gui style a plugin, KDE has choosen a
very flexible way in handling user preferences.
If you choose a light style, this 'overload' (in your opinion) gets
not only deactivated. Better: The style-plugin you choose will be
faster and less memory-consuming. So it's up to the user...

Actually, speed isn't the best reason to choose a style. .NET is pretty fast, but from what I've seen (assuming you have enough RAM to run KDE comfortably) Keramik is just as fast. It's slightly faster than even Qinx.

I really like keramic. The only "not so good" stuff of the theme are the buttons, which are a bit too proeminent, and the window decoration. I wish the window dec was somewhat less complex. I've replaced it with MKUltra (similar to web window dec) which is ok, but not perfect.

Holy crow, dude. It's not like you can't CHANGE the default back to something less fancy. Calm down!

GNOME has a lot of good points that KDE can learn from... for one, I much prefer the way GNOME puts disk icons on the desktop only when they're mounted, instead of having those silly mounted/unmounted icons on the KDE desktop. Nautilus also starts up and runs a lot faster than Konqueror. But you know what else? GNOME2 is sooo much less configurable than 1.4 was, and common dialogs like the fileselector aren't nearly as easy to use as the KDE dialogs. So, KDE is still the best in my opinion.

I must admit that I haven't looked at Gideon yet, but if you want to see some really impressive OpenSource IDE (for Java), look at Eclipe. You can find it at www.eclipse.org. It suppports fun stuff like real-time parsing of the code for very intelligent code completion and error detection, or refactoring support that can do things like re-naming functions (in the class that implements it AND all code that uses it).

They are working on supporting C/C++, but I doubt that they will be able to implement all the features that the Java mode has. The advantage of a small, limited and very restrictive language is that parsing is fast and relatively easy.

I must admit that I haven't looked at Together for over a year, but I dont like UML or other graphical representations.
They fail when the system gets more complex. Who needs a graphical representation when you would need a 200 inch screen to see everything? I much prefer to use text. You can read it top down, you can easily search without getting lost, you can display the differences between two versions and so on...

During this summer I was in front of more than 600 classes in C++, it was not a problem for Together.
And really, with 600 classes you like very much Together, especially if most of them are not yours and you have to understand them. It's faster to understand an UML diagram than simple text.

You don't need a big screen to see everything because you simply don't want (and don't need to)
You are a good designer and you split your "big" project in small ones that you can work on it (module).
The argument is also bad because with you text editor you can't see everything either.

If your are lost in an UML representation, i can do nothing for you. UML is here to represent in a more human way an program and we haven't find a better way to do it.

I would strongly advise to change your mind about UML. For example, nobody would really want to create a complex electric circuit without a wiring diagram. But for sure you have to organize your diagrams and split them into useful amounts of information.

We use Rational Rose in our company to model all software designs that are more complex than a simple one week hack. And I never want to go back to text only.

First of all, since the older (non-Gideon) version of KDevelop is the one shipping with kde 3.1, why is Gideon in the HEAD branch? It's pretty confusing to have to come up with some weird branch name to get the currently-shipping version of the program...

I am really interested in trying out Gideon, and was wondering if users who are familiar with it could post their impressions about its usability and stability. I know it's been in development for quite a while now; can useful development be done with Gideon, or is it really only alpha-quality?

I know there's an import function for translating *.kdevprj files to the new *.kdevelop format; is it also possible to go from *.kdevelop back to *.kdevprj?

It is pretty normal to have the development version in HEAD, because that's where the development takes place. Almost every sane person does this... after all, the CVS is intended for developers.
(And BTW the rest of KDE does this as well, development is in HEAD and the releases are currently in the KDE_3_0_BRANCH)

Yes, of course I know that development takes place in HEAD. However, for the rest of KDE, the stuff in HEAD is the stuff that will be released with KDE 3.1. This is not the case with Gideon/KDevelop. That's what I meant, sorry it wasn't clear.

Now when I run gideon it only popups a very small window, with three menus:
File, Help and Window, The only one with reason to click on is File-Open or File->Quit.
Also in the toolbar there is a single open-icon.

KDE somehow failed to register the KDevelop plugins. What you see is just the naked main program. So please, check why your KDE didn't be able to register KParts-based plugins; probably run a kbuildsyccoca manually.

I figured out gideon installed into /user/local/kde.
It's in my PATH, so I could run it, but the main program coudln't find the plugins, cause they were in /usr/local/kde/...something...

I simply reconfigured with --prefix=$KDEDIR [1], and now everyting is so overwhelming I wanna pass out. :-)

[1]: Actually, root doesn't use X, so therefor KDEDIR didn't exist while I reconfigured.
Instead I did it with --prefix=/opt/kde3. Since i failed to run efter su -c "make install", I logged in as root, but under normal circumstances $KDEDIR would have been enough, I guess.

What you see is the naked main program; somehow KDE failed to register the KDevelop plugins which plug their user interface in. Try if a manual run of KDE's kbuildsyccoca helps, otherwise there's something wrong with your KDE installation in general.