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.
Ive tried the KDE Beta 2. And I must say... Its a very very very stable pre-release. Hats off to the KDE developres.
The only problem is that some of the older KDE apps wont run correctly with the new KDE and they must be upgraded to work with the new QT packages.
Everyone should D/L it and check it out.
I want proof that Konqueror cannot be removed from KDE without causing severe damage to the OS!
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.
Hurrah, they've provided slakpacks!
Ive been using it today, its very nice. I wasnt a fan of KDE2, and at first glance this is just kde2 with bells and whistles. However, there are subtle changes and integrations that make it much nicer to work with on a daily basis.
Konquerer is a little buggy though (crashes every time i press the Back button)
Cant wait for the final release!
"You get what you pay for after all."
-Rob Malda
How useful can KDE be?
I was pretty happy with KDE 1 and remain happy with KDE 2.0
I'm sure to get Troll -1'd into oblivion for this, but
"Provided by the management for your protection."
Anywho, the feature that I've been most looking forward to is tabbed browsing in Konqueror, due to appear in KDE 3.1. Galeon is the one constantly used app that isn't a part of KDE, and I use it because a.) it has tabbed support and b.) a smart bookmarks toolbar. Plus, it's a web browser. Nothing more, nothing less. Konqueror has various view settings (such as "file manager", "web browser", and whatnot, but in my experience, the different view settings don't always play nice. But since tabs are at the top of my wishlist, I will definitely reconsider Konqueror in the near future.
So, what are all you other KDE fans looking forward to?
I know a lot of people who were scared away from KDE2.0's unstability and bugs.
It's a marketing-thing. People tend to only try out .0 releases, so a 3.0 release that is in reality a 2.3 is the best thing that can happen to KDE :-)
The second-best feature of KDE 3.0 is the configuration of animated pics, BTW ;-)
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?
The suse packages have a few minor installation conflicts. Make sure you have the prereqs installed and just --force and it will work. They use a separate .kde dir (.kde3-testing) so that you don't lose your old kde2 environment. However they don't migrate up your old settings. You can do this by copying the .kde2/share/config and .kde2/share/apps directories into .kde3-testing/share before your launch kde after you update. kconf_update will migrate your settings forward.
/opt/kde3 and you have to log in with the kde3 session entry in kdm if you use that.
I was unable to get the lisa package or kdevelop to install due to dependency problems, and I didn't try. Make sure you install the mesaglut-devel package. It's needed.
The packages install into
Known bugs so far:
- Browser identification doesn't always work correctly.
- Greek keyboard setting is giving me Russian characters instead for some reason. (this may or may not be a bug)
Just make sure you keep KDE2 libraries around and your old KDE2 apps will still work. They just won't directly interoperate with KDE3 apps. For instance, you can't embed old modules/plugins into new applications.
I'm really looking forward to KDE 3.
No, not because of the move to QT3.
No, not because of the improvements in Konq, KFM, or any of those - not even the multi-key shortcuts.
I just want to be able to use KMail for my Maildir mailboxes. I know there are hacks, workarounds, all that - but I don't want those. I just want to be able to plug in and go. Right now I use Mutt, but sometime in the future I'd like to be able to do some of the things it doesn't - like inline HTML viewing. KMail won't be for regular use, I guarantee it, but it will certainly be a nice complement to mutt.
A very close second is the switching of desktops when dragging a window - that's on the "KDE 3 List" and it's definitely something I miss from E. I don't know if it's going to be in 3, but I also really miss the ability to "walk off the edges" of the desktop and switch to a different virtual desktop. I've got the keyboard shortcuts set up, but it just isn't the same.
KDE1 was not even close to binary compatible with KDE2. Anyways, KDE3 broken binary compatibility because Qt broke it with Qt3 so it was a good opportunity. The transition shouldn't take too long before you have all KDE 3.0 applications though. Don't worry, it won't be that painful.
Part of the job of the beta is to get people porting their apps to KDE3 too.
I haven't had any luck getting the 2.x family of KDE to build on an OpenBSD box, whether the hardware was x86 or PPC. Which sucks, because I really want to use Konq, and Mozilla won't build at all under Open.
Urg.
Anyhow, has anyone managed to build one of the 3.0 betas under OpenBSD?
--saint
Try the Font Deuglification HOWTO.
You might find a more recent copy on linuxdoc.org, but they seem to be down at the moment.
Alan
*cough*bullshit*cough*
"Red Hat" doesn't hate KDE. Bero is a big KDE advocate, and maintains daily builds here:
http://www.linux-easy.com/daily/
Red Hat probably doesn't provide packages through other channels because they aren't going to support them. The KDE people are free to use the packages that Bero's put up, and they have in the past.
Since noone else has.
Here is the secret link to the new
KDE 3.0 Beta2 screenshots
This has nothing to do with likes or dislikes of a particular desktop (you'll notice there are no RPMs for the recent GNOME 2.0 alpha either).
;) ) right is much more important (especially because next release + KDE 3.0 will be an officially supported configuration, 7.2 + KDE 3.0 isn't and probably won't be, releasing such a large errata that even breaks binary compatibility is not very likely to happen).
There will be packages for beta2 later (probably some time tomorrow); the problem is sheer lack of time. I've tried, but still haven't found a way to work more than 24 hours a day.
And generally, building alpha/beta packages for previous releases is pretty low on my priority list (if you look at rawhide, you'll see KDE 3.0 post-beta2 has been in there for a couple of days).
Getting the next release (7.3, 8.0, Linux XP or whatever it will be called
But FYI, I'm currently building the beta2 packages for 7.2 on x86, ia64 and alpha in a different tty.
kdelibs, kdebase, kdeadmin and kdemultimedia are done, kdegraphics requires some more work because of different gphoto versions, and I haven't started on the others.
This message is provided under the terms outlined at http://www.bero.org/terms.html
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