Slashdot Mirror
KDE 3.0 Beta 2 is out
Subject says all - the next beta of KDE 3.0 is out, after a short delay. You can find the downloads at this announcement. Click below to read more details about this version.
One of the most important things that the Konqueror teams wants from people are test cases of your regulary visited pages, where Konqueror either fails to render or render things incorrectly, and submit it using KDE's Bug Tracking system. URL's will not be helpful as it takes lots of time to strip a page from all the HTML code in order to find the actual problematic part of the web page.
Just to save the search for some people: Mandrake, SuSE, Slackware and Tru-64 binary packages are available now. Others will be available soon. Source code is of course available also.
It turns out that a large silent number of
people are running KDE (and GNOME) desktops
under not *linux, but under FreeBSD. It would
be nice if more FreeBSD binary packages were
built.
This applies to KDE as well as Gnome.
...).
These two environments tend to come with huge packages (e.g. gnome-applets, kdenetwork, kdemultimedia, kdegraphics, koffice,
Sometimes, you just need one or two in the packages, and you are forced to install the whole jumbo packages. Why? Why can't we pick and choose?
E.g. I use Kword sometimes for simple word processing, but I never use the spreadsheet and the presentation app. Same for kdenetwork. I use KMail and KNode, but I don't need korn,ktalkd,ksirc,.... And kdemultimedia, I don't do MIDI stuff, and I don't want to waste 10MB for timidity++ and other junks.
Oh yeah, same for Gnome. Why do I need to install the whole gnome-applet package if I only need one applet? Same for other jumbo packages.
I'm on RPM-based distro. How about apt-get-based?
I don't know the internal details of the code, but isn't there a way to separate them out?
Good point.
But that actually raises another concern. Why didnt they make KDE3 backward compatible with KDE2? KDE2 is compatible with KDE.
I have alot of KDE2 applications running and I know it will be difficult to maintain both sets and remember which works with which set of libraries. Its sort of like the whoel GLIB problem (e.g., 2.2)
However, such a study doesn't improve usability on it's own, it just states that it has to be improved. You can tell a crappy UI coder that he is just that over and over, he won't get better just because of this.
KDE also has Usability page, but there seem to be more active KDE subprojects...
(Note that I don't want to imply that Gnome has more crappy UI coders than KDE. Both have their share, and both have great ones.)
Programming can be fun again. Film at 11.
You wanted "clear simply instructions on how to have the kde call openBrowser(url) open in something other then Konq". That's what you got. Clear simple instructions on how to have the browser of your choice called in place of konqueror. No, it's not a perfect scheme, but then again, nothing in life is perfect.
But I'll let you in on a little secret just so you can sleep better at night. The file associations are used by the file manager to associate file types with applications. Something else handles URLs. And you know what that is? The file manager itself. The name of that file manager is Konqueror. And that's the reason why the file manager doesn't need to be told which URL scheme goes with which URL handler. The file manager IS the URL handler.
A Government Is a Body of People, Usually Notably Ungoverned
One of the reasons, I believe, for RH to sport such an aggressive testing strategy is, that the next RH release will be build entirely with the GCC 3.x compiler
That, and the fact that I don't think it makes sense to leave a version with known bugs in there for too long. A week from now, most of the commonly noticed problems with beta2 will be fixed in CVS, while possibly introducing new ones. Those new ones are the ones we need to know about. (We aren't planning to ship anything official with beta2 - so bugs specific to that version don't matter much - getting bug reports about things that are already fixed is not very useful).
If KDE 3.0 is stable when RH 8.0* hits the market, you can be sure they will include it.
That's the plan (no comment on the version number though). We generally don't throw stuff into rawhide that we aren't planning to ship.
And yes! cups (www.cups.org) look like it is going in too.
It's going in, and Qt, KDE and wine are built with cups support.
This message is provided under the terms outlined at http://www.bero.org/terms.html
> and Tru-64 binary packages are available now
I run KDE2 on Tru64 and it absolutely owns
Windows sucks compared to this!