Slashdot Mirror
KDE 4 Promises Large Changes
HatofPig writes "As the dust settles from aKademy 2005, the annual KDE conference, it's a good time to take a look at what the KDE developers are working on. Though KDE 3.5 isn't even out yet, developers are already working on KDE 4. Plenty of work has already gone into porting existing code to Qt4, the GUI toolkit upon which KDE is based, and KDE developers are working on projects that could radically change how the world's most popular free desktop looks and works."
I don't think that it is a major killer for KDE to be slightly less responsive. I think if linux wants to be taken more seriously by non-geek people, it has to drastically imporve the artwork in the GUI. Even the hard-core developers and internet geeks, as soon as screen shots are out... they hammer down servers to look out for the eye candy. A generic user does not even notice the slightly slower response time, but he will notice if Windows Vista looks better than KDE 4. So ... my two c.. I think KDE is taking a very good direction. Better art-work, means better eye-candy, and more attracting generic users. (I am making an enormous assumption that a generic user will still be able to run popular household applications on the Linux box ...)
Albeit, Slashdot isn't quite the place to be pushing KDE and *nix if you want it to get seen by Joe Sixpack.
Actually, a friend at school was messing around on my laptop, and was amazed with all the stuff that KDE 3.4 could do and it's bundled apps. His jaw dropped at Amarok (auto lyric downloading, Wiki entry on the band, smart playlist, native iPod support, etc.) and was even more amazed when I told him about stuff like K3b's built in DVD ripping, KAudioCreator CD ripping, Kopete supporting all those protocals in one window, and plenty of other stuff. It's worth showing to people.
-Clinton
Silicon & Charybdis McLuhan Kildall Papert Kay
In Windows I use TortoiseCVS/SVN. It absolutely rocks. Using Cervisia after using Tortoise is anything but pleasant. I don't want to offend the Cervisia devs with this, but I would be glad if a new Cervisia release would integrate in Konqueror like Tortoise does with Explorer.
This sig does not contain any SCO code.
The overall memory usage is not that high. On my system a huge part of the used memory is cache. Even if it shows that my memory is almost full I can easely run a game that takes up atleast half of my RAM without problems.
I can run alot more applications at the same time on my machine when im in KDE, than I can when im in winxp.
And yet the #1 reason lots of other people won't use KDE is because it doesn't work exactly like Windows. The KDE developers are stuck in a catch-22 situation - if KDE resembles Windows in any manner, people flame them for just copying a poor desktop, and if they try and do something new, people flame them for doing things differently to Windows. Either way, they can't win. Even the compromise they have now - default to Windows-like and offer the ability to configure it differently - isn't enough for some people.
Bogtha Bogtha Bogtha
Please not. GTK is horrible. Right now, I am writing some classes that astract the same behaviour for GTK and KDE
n ew(),"text", i,NULL);e _new(),"active", i,NULL); //Dangerous cast!h eckBox),this);
Here is the KDE version for adding the columns to a table widget:
table->insertColumns(0,cols.size());
QStringList names;
for(size_t i=0;isetColumnLabels(names);
Short,nice,readable,whatever you want. If I make a mistake, the compiler will tell me.
Here is the GTK version:
for(size_t i=0;icols.size();i++){
GtkTreeViewColumn *col=0;
GtkCellRenderer *ren;
switch(cols[i].type){
case ListBox::ColumnDef::StaticText:
col=gtk_tree_view_column_new_with_attributes
(cols[i].name.c_str(),ren=gtk_cell_renderer_text_
break;
case ListBox::ColumnDef::CheckBox:
col=gtk_tree_view_column_new_with_attributes
(cols[i].name.c_str(),ren=gtk_cell_renderer_toggl
g_object_set_data(G_OBJECT(ren),columnkey,(void *)i);
g_signal_connect(ren,"toggled",G_CALLBACK(toggleC
break;
}
gtk_tree_view_append_column (treeview,col);
}
It is twice as long, is not type safe, checkboxes won't toggle aunless you add a callback, and the documentation is very twisted: Look at example for "active": "active" gboolean : Read / Write
The toggle state of the button.
Default value: FALSE
If you read that, do you understand that you have to set "active" to the column number of the checkbox column? On the PARENT of the cellrenderer object?
Notice how the KDE version does not mention what the column contains. The GTK version does. In both cases, I have to specify it later, when I set the column data. Why do I need to tell it twice to GTK?
And this is not an unfortunate choice, but the general case. FOr QT/KDE, I read the docs, and I implement. For GTK, I read the docs, delve trough examples until I find something similar, crash atthe first trys because all the casts make compiler typechecking useless, and the resulting code is in general twice as long.
Please, kill the ugly beast that is GTK.
1) is correct, but also pretty ironic, given that there are so much zealots who say exactly this (too much prefs stuff in the control center) and then say "edit bla.conf" when anyone asks how to get sound working (provided the zealots don't quit with a "RTFM"). The advanced options shouldn't disappear completely (like GNOME did). Instead, they should be hidden behind an "Advanced options...." button. For example, the Windows desktop settings behave this way; the most common options are visible immediately, but for editing graphics driver options or setting the monitor refresh rate etc. one has to go to the Advanced Options part.
2) There is already something for GNOME/KDE integration: a GTK theme engine based on Qt. Thus, GTK apps look like Qt/KDE ones. Of course, its only useful if you use KDE...
This sig does not contain any SCO code.
And yet the #1 reason lots of other people won't use KDE is because it doesn't work exactly like Windows.
Yes, you have a point there. If you copy something, then any difference to the real thing will be noticed more, the closer you copy. Essentially, you can make a 100% clone, or you can make your own thing, anything inbetween will be perceived as bad.
The way KDE does it, nobody is really happy with it. I figure it's "good enough" for a large share of people, and since many of them are ex-windos users and have grown up to live with "good enough" being all they should ever expect - it kinda works.
5 years ago, there was much hope for the Linux desktop. Today, even I seriously consider buying myself a Mac. And that's after my main machine has been a Linux machine for over 10 years now.
Either way, they can't win.
Learn a lesson from the real leader in computer desktop UI. Copy the Mac or come up with your own alternative. Do things because they are good things and not because windos does them.
Ah crap, I tried convincing the Gnome UI group when it was formed (and I was an early member) and couldn't. Now we have two badly copied windos-like UIs for Linux. And we all pretend to be surprised that it's not making as much progress taking over the desktop world.
Hello? You can't overtake anyone if all you ever do is drive slipstream.
Assorted stuff I do sometimes: Lemuria.org
And I'm not exactly sure how more "eye-candy" is going to attract anyone, since windows is already the ugliest desktop around. I think being pre-installed on 99% of hardware wouldn't hurt the chances of people using Linux. But until it is they're just going to go "I won't want Linux, I just want something that's easy to use for email and web and ebay." Which Linux is already far better for than windows since you don't need to know ANYTHING about it do to those things (if the system is pre-installed) and it'll definitely run a lot smoother, and at least for the time being more securely.