KDE 3.0 Beta 2 is out 341
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.
KDE - Beta is stable (Score:5, Interesting)
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.
Re:KDE - Beta is stable (Score:3, Informative)
Re:KDE - Beta is stable (Score:2, Insightful)
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)
Re:KDE - Beta is stable (Score:3, Informative)
Part of the job of the beta is to get people porting their apps to KDE3 too.
Re:KDE - Beta is stable (Score:2)
You can have KDE-1, KDE 2.X & KDE 3.x - all on the same machine, all of them running on the same X without a single problem...
Try the same thing with Windows 9x - they "fixed" this problem on XP if I'm not mistaken..
Re:KDE - Beta is stable (Score:2, Interesting)
an ancient dos tool *might* wont run on win2000 but that's usually because it's hitting the metal - which I find is a *very* good reasong for win2k not to let it run. dos runs on old 8088/8086 CPU's, Linux wont run on anything less than a 386.
True though you can run old KDE apps with th eold libs - mind you aint that fussed about upgrading - since all apps I got are free anyway it wont cost me a penny, plus it gives me a good excuse to sit down and tinker with my boxen!
Re:KDE - Beta is stable (Score:2)
As I recall from earlier stories (PLEASE correct me if I'm wrong here, it's been a while) the KDE folks were looking at binary incompatibility no matter what due to a new gcc that was due out. I don't pretend to understand the mechanics, but apparently everything was going to require a recompile anyway.
Probably mentioned in some mailing list archive someplace. They figgered that if ever there was a good time to break compatibility, now was that time. The long term game plan is to have the underlying architecture of KDE 3.0 support new versions for the next 3 years or so.
I've seen it mentioned a number of times exactly how aware the KDE crew is to this breakage. Heck, there's still KDE 1.2 apps that haven't been bumped up yet! Hopefully, this will be the last of these kinds of upgrades for a while... assuming the game plan works out that is. 3 years is a darn long time for KDE.
I demand to see the source! (Score:5, Funny)
Re:I demand to see the source! (Score:5, Funny)
Re:I demand to see the source! (Score:5, Interesting)
Re:I demand to see the source! (Score:5, Informative)
Actually what I would like is clear simply instructions on how to have the kde call openBrowser(url) open in something other then Konq.
Ok, your wish is granted.
Each user to his own browser. Just how I like it. Very easy to change.
Simple enough? I think so.
What peope don't seem to realize is that kde is more customizable than any other DE/WM. It's also scriptable. Type dcop in a term.
Re:I demand to see the source! (Score:2)
No... or at least it hasn't come across the list. There *was* some talk about redesigning it to use the setting from the control center by default. What precisely are you talking about?
--
Evan
Re:I demand to see the source! (Score:2)
If you feel that functionality is missing from openBrowser(), you should still use it and fix openBrowser(). By not using it you give out a sign of unwillingness to adopt to KDE standards. You'd rather ignore the standards than fix them.
If you want your application to ship as part of KDE you're no longer a third party developer, you'd be a KDE developer and you'll have to think of a picture bigger than just your application.
Even more important however: I do not think KDE should replace shipped applications (there is a functional AIM client already) every time an alternative comes along, even if the alternative is better. That'd be inconsistent.
Re:I demand to see the source! (Score:2)
Re:I demand to see the source! (Score:3, Insightful)
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.
Re:I demand to see the source! (Score:2)
Actually, for KDE applications that is not a problem because they (should) all use the KIO technology which makes network file access completely transparent, whether it is http, imap, sftp, smb, whatever. As long as there is a KIO slave, any KDE application should be able to perform any request transparently.
But I still agree that openBrowser() should be configurable in KControl, just like the preferred mail and console applications are.
Re:I demand to see the source! (Score:2)
Re:I demand to see the source! (Score:2)
Which, let's be honest, is just a case of leaving it running and going to bed.
what about FreeBSD binaries? (Score:5, Insightful)
people are running KDE (and GNOME) desktops
under not *linux, but under FreeBSD. It would
be nice if more FreeBSD binary packages were
built.
Re:what about FreeBSD binaries? (Score:2, Insightful)
I get a nice, warm, fuzzy feeling knowing that everything on my computer was built from source by my computer.
You have to do something with all those spare cycles and I could really care less about finding alien signals from noise, cracking the latest DES, or factoring the largest mersine (sic) primes.
Viva la source!!!!
--InfinityEdge
Re:what about FreeBSD binaries? (Score:3, Funny)
Where did you get your compiler? It could be putting in a trojan every time you compile. Have you checked your binaries?
Re:what about FreeBSD binaries? (Score:2)
Re:what about FreeBSD binaries? (Score:2)
Re:what about FreeBSD binaries? (Score:5, Insightful)
KDE does not produce any binaries.
Let me say that again: KDE DOES NOT PRODUCE BINARIES... they ONLY release source. Any binaries that are available at a version release were created by the distros themselves. It's in just about every single FAQ that KDE produces.
KDE aims for portability against just about every X and *nix out there, including AIX, Solaris, BSD and Linux. I mention those in particular because there are KDE developers who use each as their primary platform. About the only drawback to the "source only" policy is the occasional distro that releases a binary with all the debugging turned on, or gif support turned off, etc. But that has gotten more rare with better documentation.
--
Evan
Re:what about FreeBSD binaries? (Score:2)
Well, why not read what the debian binary packager has to say on the subject... from dot.kde.org [kde.org]:
" I hope to have the .deb's out soon, but remember: I have a life, too. I have school, work, and more. I also have a gf 220km away, which will take up most of my weekend except for Saturday, because I didn't see her today.
"You'll get the debs when I have time. In the meantime, deal with KDE2.2."
So, that's the reason. There's probably a very human volunteer behind the FreeBSD binaries who is trying to balance a life and doing the packaging - very precision work on a very large package with long compile time. Why don't *you* do it, eh?
--
Evan
Re:what about FreeBSD binaries? (Score:2)
Okay... one last time. KDE does not provide any binaries. Period. End of story. The KDE developers only offer source. No more.
When a release is planned, some distros, *not* KDE developers, make binary packages. In cases like SuSE, they are made by paid employees. In cases like debian or Tru64 (Compaq's Unix), they are made by someone who voluntered to do so. Just before the announcement, anybody who wants can tell KDE "Hey, I made a package for my OS or my distro. It's located at this ftp site". Thus, *anybody* who wants can have their binaries listed in the announcement. KDE even goes so far as to mirror the binaries. But they do not provide them. Anybody who has a binary done by the announcement can have it listed in the official announcement. The people who create the Red Hat, debian Solaris and AIX packages didn't get theirs done in time. SuSE, Slackware, Mandrake and Tru64 did.
Is that answer clear enough? KDE mirrors and puts links to the binaries in the annoucements. They don't even check to see if they work - and in the past, there have been cases where the packages didn't. It's not KDE's position to test the binaries, as they don't have anything to do with them other than providing handy pointers to where they are. The only product of the KDE Team is source. End of story.
It's a bit like asking the kernel maintainers: "Why do you only release kernel versions for some distros and not others?" Again, all they do is release source, not binaries. It's up to the distros to compile for whatever target platform they choose to support, and package it however they wish.
--
Evan
Re:what about FreeBSD binaries? (Score:2)
Let me check...
...hmmmmm....
Oh, look here! ftp://ftp.kde.org/pub/kde/stable/2.2.2/ provides binaries for SEVEN different operating systems and distros! These aren't links to those respective systems, but bonafide binaries on the actual genuine KDE site!
Re:what about FreeBSD binaries? (Score:2)
If your distro isn't there, and you REALLY think it should be, and if you feel that strong about it, then why don't you add to the collection?
Re:what about FreeBSD binaries? (Score:2)
It is still true that we do not make the binaries. Distributors do. Those binaries are placed there for your convenience, but it is still the responsibility of the packager to create them.
I guess we could remove all those binaries from the site though, if that'd make you happy.
Slackware support! (Score:3, Interesting)
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!
As CmdrTaco says... (Score:5, Funny)
-Rob Malda [slashdot.org]
How useful can KDE be?
Re:As CmdrTaco says... (Score:3, Funny)
Re:As CmdrTaco says... (Score:2)
Who Really Needs 3.0? (Score:3, Interesting)
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
Better, faster, higher (Score:2)
Re:Who Really Needs 3.0? (Score:2)
Dave
Re:Who Really Needs 3.0? (Score:5, Informative)
First of all, the major reason for KDE3 is QT3. QT3 has several advantages over QT2 for developers, and the KDE project want to use these to their advantage. As an end user, you probably won't be aware immediately of the changes, but developers will, which means that better programs will be coming your way.
Also, look at http://developer.kde.org/development-versions/kde
:Peter
Re:Who Really Needs 3.0? (Score:5, Informative)
this is very much an evolutionary release as opposed to a revolutionary one (as KDE2.0 was), but the changes are quite noticeable. they make the general kde experience smoother and more useful IMO. one nice thing about it being evolutionary is that it is immediately stable and familiar ...
Learn C++ (Score:2)
I see theres no programmers here
Better programs is why you should use 3.0
What I'm looking forward to... (Score:4, Interesting)
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?
Re:What I'm looking forward to... (Score:2)
Waiting to see how short of a time span it is for my current download to timeout because of being posted on the
Re:What I'm looking forward to... (Score:5, Informative)
I agree with the tabbed browsing, I can't wait for t to appear in 3.1. But the smart bookmarks toolbar; I find that vastly inferior to Konqueror's web shortcuts feature, mainly because it is so much simpler to use. Why do I need a bulky toolbar cluttering up my screen when I can just type "php:fopen" to search the php manual, or "rf:gaim" to search freshmeat? It's very cool. if you've never tried this feature, go into your konqueror settings under "Enhanced Browsing". It's very easy to add your own sites.
Re:What I'm looking forward to... (Score:3)
I just thought I'd make a correction for people who are not familiar with this (totally freakin' awesome) feature.
rf:gaim - The "rf" is for searching RPMFind.net [rpmfind.net]
fm:gaim - The "fm" is for searching FreshMeat [freshmeat.net]
You can see many more things available to you by going to:
Control Center --> Web Browsing --> Enhanced Browsing
Very cool stuff...
Re:What I'm looking forward to... (Score:2)
The improved javascript support. It's the one place where I still occasionally run into problems using Konqueror, but so far the KDE3 CVS snapshots have been looking much improved over KDE2 in this department...
UI Design (Score:5, Interesting)
My opinion of the KDE overall user experience is that it's rather "blah". Now, I will admit that going from KDE 1 to KDE 2 was a huge step up, I just think that it needs to become cleaner, lighter, and less cluttered.
For example, the default setting for the Kicker is 2 buttons high. This is just too tall. The new Konquerer is really too cluttered, with the big sidebar, etc.
Going to the extreme, I wish KDE would become more like BlackBox with its basic design. BlackBox actually makes 1024x768 seem like a higher resolution than that. KDE makes 1024x768 seem like 800x600 or maybe even less.
So anyway, those are my thoughts.
Re:UI Design (Score:5, Informative)
If you think KDE is rather "blah", check out http://kde-look.org [kde-look.org] and look over the icons and themes. Ignore the wallpapers, though, must of them are not worth your time. KDE-look has taken the place of kde.themes.org [themes.org], so if you want to add spice, go there.
Secondly, if you're able to use Blackbox, you are able to spend the two minutes it takes to customize KDE to your liking. If you don't like the default height of Kicker, right click on it and you can change it immediately. Plus, if you really want that Blackbox look and feel, you have the choice of using Blackbox themes in KDE (I'm not sure if this is included by default with KDE; if not, go to kde-look.org), or use BlackBox as the window manager instead of kwin. Google is your friend if you don't know how to do this.
:Peter
Re:UI Design (Score:3, Funny)
The Spider-Sense for geeks.
Re:UI Design (Score:3, Informative)
Or you can use the kbox window decoration, which even loads BlackBox themes.
Or, you can do like I used to and use use BlackBox or FluxBox instead of kwin. KDE runs just fine under both, with FluxBox even handling docked apps perfectly (there's a patch for BlackBox to do that as well).
--
Evan
Re:UI Design (Score:2)
Course, take my opinon with a grain of salt, since my desktop isn't exactly normal:
http://turbogeek.org/screencaps/jmd-20011021.png [turbogeek.org]
I still think the default mode of both of these environments should be more lean. Power users can always add on what they want. All Windows has is a 10px high "start bar", consisting only of 1 button, and a clock. And most users love it. Keep in mind it's been through a lot of usability testing... feed off that, since we can't afford our own.
Re:UI Design (Score:4, Insightful)
So turn the sidebar off, and make the kicker 1 button high. Big whoop, takes all of 10 seconds in kcontrol.
These things are set this way for a reason. The sidebar makes browsing a folder tree MUCH easier for people used to windows explorer, and I , a non-windows user, also find it a very powerful tool, where I can access my bookmarks and FTP sites in a cinch. As for the kicker, I prefer it two buttons high, not for the sake of the buttons so much as the clock and the launcher icons. I think having them large gives it a more polished look. Not to mention the Run Command kApplet won't fit in a kicker under two buttons. If you feel like the desktop is cramped, why not make your kicker transparent using TeaX [kdelook.org], I think this is very slick.
Anyway, my point is just because you like it one way doesn't mean everyone else does. That's why kde and gnome are so customizeable. So customize them already!
Re:UI Design (Score:2, Insightful)
Highly-configurable UIs like Gnome and KDE tend to show off by turning all the stupid options ON by default. The fact that they are highly configurable allows users to fix this on their own, but the first impressions are still "flashy, cluttered, slow" instead of something more utilitarian and, well, usable. This hurts in reviews, gaining non-techie converts, etc.
The other issue is that Gnome and KDE both borrow BAD UI ideas from Windows because people are used to sucky UIs, rather than aiming a bit higher. Again, you can configure your way into a good UI, but, by default, you're looking at some bad UI design. Both KDE and Gnome have menus that cascade down from a menubar, EXCEPT for the desktop itself, where the menus launch out of the bottom of the screen! What planet does this make sense on? If you want menus coming out of the bottom of the screen, at least make them do that for your applications too for consistency! And then there's the "close window" button up in the upper-right corner, with all the other buttons that control window behavior. Why not put the potentially destructive button in one of the other corners AWAY from the benign ones? That's the way everybody handled it until Win95 came out and made it so much easier to close windows accidentally.
Yes, these are silly rants. All of these errors can be fixed. The question is: why do WE have to fix them?
_constructive_ (Score:4, Funny)
enlist volunteers to help find elusive and platform-specific bugs, and to provide constructive feedback through the KDE bugs database prior to the developer meeting later this month
At first glance, I missed why this even needed inclusion in the announcement. Most users are more than willing to provide feedback when Konqueror or KDE doesn't work right. Then I re-read the word "constructive."
So, for further edification, constructive feedback doesn't typically contain the words "suckers" "bastards" "morons" or "jerks." That kills 99% of the feedback they would be getting.
The greatest feature about KDE3... (Score:4, Informative)
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 ;-)
Re:The greatest feature about KDE3... (Score:3, Informative)
No, it's a "we may change the API and ABI in major releases" thing.
One of the main points of KDE 3.0 is the switch to Qt 3.0, which brings many advantages, but also breaks the existing ABI (and to a small extent, API).
Re:The greatest feature about KDE3... (Score:2)
Of course I know that it's binary incompatible with KDE2, but that's irrelevant for somebody who tries KDE for the first time. (And KDE 3.0 will get *A LOT* of first-time triers, a lot more than a KDE 2.x would get.)
Redhat? (Score:2, Interesting)
Re:Redhat? (Score:2)
Re:Redhat? (Score:2)
Don't you remember the times when RedHat refused to ship the opensource-but-not-GPL (the HORROR) Qt, but did ship the then closed-source and commercial Netscape?
RedHat simply had to ship KDE because it is wanted by the users.
But obviously Bob Young is still using Gnome [slashdot.org].
Re:Redhat? (Score:2)
Note that this situation was not resolved by Red Hat bending to their users requests, but by Trolltech's licensing QT under the GPL.
Netscape may have been closed-source and commercial, but its license allowed Red Hat to distribute it, and no GPL'd applications linked against its closed-source libraries.
Re:Redhat? (Score:2)
AFAIR RedHat was shipping KDE before the change of Qt's license, so obviously the license-issues weren't that important for RedHat anyway.
Oh yeah, I remember quite well when debian was the only distro not shipping KDE....
Re:Redhat? (Score:5, Interesting)
"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.
Re:Redhat? (Score:2)
Nevertheless, the rest of RedHat doesn't give it very much support (just like you said):
Red Hat probably doesn't provide packages through other channels because they aren't going to support them.
Re:Sorry, it is not bull. (Score:2)
It's fixed for real in the current tree (qt3/kde3), the fix can't be backported easily, and I don't have more than 24 hours a day, so this simply has to wait until I have a lot of spare time (getting this right isn't exactly easy for someone like myself who doesn't have the slightest clue about Japanese input methods), or until someone else attaches a patch that fixes both.
Re:This is laughable. (Score:2)
I regularily use German characters (if only to get the weird ä character in my last name right), and it works.
The problem is just using deadkeys, which isn't that widely used,
and AFAIK can easily be worked around using Compose
(e.g. Try pressing Alt Gr+Shift, then
French c character, or Alt Gr+Shift, then "a to get ä).
Re:Redhat? (Score:2)
Come on! KDE has been a part of RH distroes since RH 5.2 (?)
Bero (maintainer of the RH KDE rpms) from RH is working very hard on KDE.
He even has a home page with automatically build rpms from daily cvs snapshots.
Their testing style is different, though, and probably more agressive:
KDE 3.0 is found in Red Hats Raw Hide dir. But instead of releasing a whole KDE 3.0 beta 1, then a beta 2, etc, they release batches of incremental improved rpms, often from daily KDE 3 cvs snapshots.
So generaly speaking, RH KDE 3 rpms are much more recent, than those builds found from other vendors on ftp.kde.org.
The upside from this strategy is, that eg. a showstopper bug reported to bugzilla, can be eradicated quickly. The downside is, that a new batch of eg, KDE-networking rpms may break everything, and that everything goes so fast . (eg . I reported a bug known from the changelog, because of that).
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. KDE 3.0 (alpha and first beta at least) couldn't be build with gcc 3.x, and a lot of fixes were probably necessary.
If KDE 3.0 is stable when RH 8.0* hits the market, you can be sure they will include it.
* I think they are going to bump up the version, since an entire distro build around gcc 3.x, is a major step. (compat gcc for all the 2.7x,
And yes! cups (www.cups.org) look like it is going in too. A very, very cool printing system. IBM's JFS is going in too, and of course, KDE 3.0
Regards
Re:Redhat? (Score:2)
Re:Redhat? (Score:3, Insightful)
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.
Re:Redhat? (Score:5, Informative)
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.
No jumbo packages please (Score:5, Insightful)
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?
Re:No jumbo packages please (Score:2)
I don't know if any other distribution does this, but Conectiva (www.conectiva.com) has per-application rpms in most cases. So, if you want just the CD player in kdemultimedia, you has to install only kdemultimedia-kscd.
It's really nice, and I hope more dists would do this. SuSE has something similiar, but not for the base packages (e.g., kdemultimedia comes in a big package, but "3rd-party" applications not included in the distribution have their own package and can be installed individually.)
Re:No jumbo packages please (Score:3, Informative)
Granted, you get a small amount of bloat if you just want KWord (compared to a more standalone wordprocessor), but it beats the RPM distributions easily. The quality and ease with which KDE is handled in Debian was one of the major deciding factors in me switching to Debian from Red Hat.
Re:No jumbo packages please (Score:2)
Not necessarily.
Take a look at Raw Hide [redhat.com] to see what the KDE packages are likely to look like in the next Red Hat Linux release.
I've decided to split up most of them.
Re:No jumbo packages please (Score:2)
Apt-get isn't a packaging system. I presume you probably mean Debian. My office has been using apt-get to maintain our Red Hat boxes for a few months now, and it works quite well. Regardless, the release of KDE 3 marks a good time for the KDE webmasters to save users a bit of time when fetching the latest release my making the packages for Red Hat, SuSE, etc into an APT repository. Its quite easy (we're already doing the same with KDE 2.2.2 at work) and I might volunteer myself if I have the time.
Tips for SuSE users (Score:5, Informative)
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)
Re:Tips for SuSE users (Score:5, Funny)
looks again
Crap... Oh, mesaglut... well, I guess it's back to autopr0n [autopr0on.com]...
Anyone for Usability? (Score:2, Interesting)
-Webwiz.....
Re:Anyone for Usability? (Score:2, Insightful)
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 [kde.org], 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.)
Re:Anyone for Usability? (Score:2)
Re:Anyone for Usability? (Score:2, Informative)
KDE 3 (Score:4, Interesting)
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" [kde.org] 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.
Re:KDE 3 (Score:2)
KDE 3.0 (Score:3, Interesting)
Urg.
Anyhow, has anyone managed to build one of the 3.0 betas under OpenBSD?
--saint
Re:KDE 3.0 (Score:2)
I do indeed. Unfortunately, when I do the standard cd
For whatever reason, I didn't think to try to precompiled binaries ; I'll give that a shot tonight. But now I am curious about the port problem.
(Not that being in the ports is a guarantee that the software will work; mozilla is in the ports as well, but its a documented fact that it won't run under OpenBSD.)
--saint
Re:KDE 3.0 (Score:2)
I know, replying to my own post is bad form, but the precompiled binaries do work fine; at last, a browser that _isn't_ netscape running in linux emulation mode! Konq and konsole alone are worth the disk space for the whole KDE bundle.
--saint
No tabbed browsing? (Score:2, Interesting)
As a side note, how much obsolete and legacy code is in KDE right now? I mean, Windows contains lots of legacy code for DOS support. Any thoughts?
Re:No tabbed browsing? (Score:2, Informative)
Screenshot (Score:5, Informative)
Here is the secret link to the new [kde.org]
KDE 3.0 Beta2 screenshots
Re:Screenshot (Score:3, Funny)
Damn, it's harder to keep a secret in KDE CVS / Dot / Slashdot than in a high school full of giggling Olsen twins.
My ONE complaint... (Score:2)
I'm downloading and compiling the beta as I type this...
I've been playing with CVS snapshots off and on recently, and I must say they're looking promising. The appearance is similar to 2.2, but with a bit more 'beautification' and eye-candy effects available, and certainly, Javascript support is MUCH improved (though I still haven't been able to view things on Atomfilms for some time in Konqueror...). The ONE complaint I have that keeps driving me back to 2.2 is the apparently broken focus handling in KDE3...
I haven't been able to tab between fields in a form, for example, though this isn't a BIG problem. The BIG problem is that while entering text in textareas (such as this form right here on slashdot), hitting 'enter' to drop to a new line will frequently...do something. Not actually submit the form, but the page seems to re(?)load. The back button brings the form back up, sans all the text that was entered in these cases. I haven't been able to figure out EXACTLY what it's doing yet.
This is the only problem I've run into, but I spend enough time on web forums that it kills me...anybody already tried the beta out know whether or not this has been fixed yet? I DO recall reading that the focus problem, in general, was due to be fixed before the final release...
KDE 3.1 Preview (Score:2)
Please note that some of the planned items still might not make it and that it is very likely that several items are not yet planned but will pop up in time for the 3.1 freeze which is several months away.
Re:KDE 3.0 (Score:2)
Don't jump to 3.0 just yet. It IS beta and you may wish to read this article:
Re:KDE Clipboard (Score:2, Informative)
I can't find it now, but I swear that I've read it.
Or maybe you are just a troll.
Re:KDE Clipboard (Score:2)
Your wish is granted - the default behavior of the clipboard has changed in KDE3 (much to MY annoyance, I LIKE being able to highlight to copy).
Fortunately, this is configurable. If you want the old copy-on-highlight behavior, click the "synchronise clipboard on highlight" option in the preferences...
Re:KDE Clipboard (Score:2)
Bear in mind I'm quoting this option from memory, so the exact phrase may be a little different. You're right, though, the phrase they used was slightly cryptic, though since it's exactly what I was looking for, I recognized it when I saw it...
Why not "Copy text to clipboard when highlighted"?Good question...except maybe that didn't sound as 'cool' as "synchronise" :-). Perhaps this (the text of the option) would make a good patch for some non-programmer who wants to help to submit...
Re:KDE Clipboard (Score:2)
(1) This is by no means a bug and has been standard Unix behavior for some time. Just because it doesn't work the same in Windows, doesn't mean it's a bug.
(2) If your programming, why the hell would you be using the mouse to copy stuff??? Wouldn't you be using C-k or C-xrk like a normal person? Sheesh, my only compliant about KDE is that it encourages people to use lesser tools (KDeveloper) when better tools exist (Emacs). One would think that FS projects would borrow code from each other...
Even if your not using Emacs, if your a programmer and your stuck to a mouse, your productivity has to be hurting... Even on Windows, I still use the keyboard to copy and paste.
Re:3.0 (Score:2)
*yawn* Yep, that was a zinger alright. You don't understand open source, so it must be bad. Ooh. Harmful.
Re:FONTS!!!! (Score:3, Informative)
You might find a more recent copy on linuxdoc.org, but they seem to be down at the moment.
Alan
Re:Ugly. (Score:2)
shot 1 [dhs.org]
shot 2 [dhs.org]
shot 3 [dhs.org]
shot 4 [dhs.org]
Re:trolltech's QT (Score:2)
On the contrary. KDE wouldn't be anywhere near where it is now if it were using anything else.
The default look of Qt may be boring in some people's tastes, but its programming interface beats all other toolkits out there by far.
Try it for yourself: Read the tutorials for, say, Qt, GTK, Motif and Win32. Then implement a simple application in each of them. You'll almost certainly notice you can do it much quicker with Qt.
And Qt 3.0 adds the possibility to load styles as plugins, so you can change the look much better than earlier.
OT: your sig (Score:2)