Comments

well, right, kde 3.4 will have some goodies (altough, will it have support for hall/d-bus/udev? I am afraid that will be seriously lacking... no automagically appearing usbstick-icons on the desktop (unless the distribution does some work) and no automatically starting of k3b/cdplayer/etc when inserting media... :( thats a pitty. and what about xorg?)

but I am more waiting for KDE 4 :D
more speed, better multi-media, easier to use (I think I'm gonna love the search features) and better looks. hmmmm :D

Well, I could wait through at least two more 3.3.x bug fix releases. It would be nice if we could decide how to install the icons before 3.4.0 is released for one thing.

But about automatic playing of CD music disks.

My KDE 3.3 BRANCH install has this feature. You have to have KsCD running in the background which is optional in KDE (I presume that it isn't in Windows) and it is easy to turn on and off. There is a check box in the configure dialog for KsCD.

I still have problems playing CDs. They sound like a record that skips and nobody seems to know how to fix that. That BUG is much more important than automatic play.

Hi.
Your problem with the CDROM and playing music is a hardware problem. Cause, the KSCD frontend just triggers the CDROM (hardware) to start playing. Older CDROM's even had a button under the tray to start playing. And the music itself is routed directly from the CDROM via the audiocable to the soundcard and routed to the speaker out without anything to do for the OS. Though I think another CDROM will solf your problem.

I agree with u, it'a a very boring feature.
Only, it's possible to turn it off in Windows,
modifying a line in the system registry.
I'm not interested in this feature,
and in any case I hope that the next release
of KDE let us the possibility of leave
or turn off thi function

"well, right, kde 3.4 will have some goodies (altough, will it have support for hall/d-bus/udev? I am afraid that will be seriously lacking... no automagically appearing usbstick-icons on the desktop (unless the distribution does some work) and no automatically starting of k3b/cdplayer/etc when inserting media... :( thats a pitty.

yeah, but the way they did it isn't considdered 'properly' by the kernel dev's (submount, if I'm right, or supermount (which I use) but both aren't good enough to ever make it into the kernel - udev/hall/d-bus dont have to BE in the kernel.)

its open-source code, btw (at least supermount is) but its like, well, a hack... not "the right way(TM)". So we have to wait for d-bus/hall/udev support to have it on lets say debian and slackware, who aren't willing to add such things as a hack.

SuSEPlugger watches changes to /proc (or whatever the new one in 2.6 is called) for new devices. hotplug and coldplug monitor for new hardware, automagically insert kernel modules for it, and BAM its in proc or sysfs or whatever you use. That's how that works. SuSEPlugger then just automounts it and says "Hey, dude... you got hardware." or "hey, dude... you got media" depending on whether or not its a USB device or a CD.

The way it can tell if there's a CD is the CD drive tells the kernel its got media, and the kernel modifies one of those crazy files in proc (or sysfs, yet again). SuSEPlugger then probes the disc to see if its blank, audio, or what have you, and lets u know (and, if applicable, automounts it)

There no wrong way, to eat a reeses... i mean... probe for hardware and media.

hey, I didnt like it in windoze too, and I dont really need it, but if its configurable enough, I can put it to some use :D

for example, k3b might be started if I put a cdrw into the drive. and a musiccd might be added to the playlist in amarok. a cd with a moviefile might just start playing in kaffeine, I whoulnt mind that.

The new media:/ kioslave has a HAL Backend. If HAL is found, it will be used to list backend, hence automatically listing devices upon insersion. However, this backend seriously lakes testing, so please feel free to compile it (You only need a fairly recent HAL >= 4.0, and DBus-Qt bindings from cvs)

yes, but will a icon automatically appear on my desktop if I put in the usbstick? and if I connect my digital camera, will it start digikam?

If so, well, I dont think we need more. if not, well, there might be some work to do... I didnt use these kind'a functions under windows, but if I can fully configure it, well, I think it whould be usefull for me. and to newbies, it whould be usefull anyway...

If you plug your usb stick, it will get listed automatically by media:/. So if the desktop uses media:/ to list disk partitions (It used to relying on devices:/, but I am not sure if this has been changed to media:/), your usb stick should appear on the desktop.

If you plug you camera, it will also get listed and the media:/ entry will be mapped to the corresponding camera:/ url.

There is no "application autoplaying" by now, but this might be a good idea for KDE 4 !?

I'm kind of also waiting for the big 4 instead of any smaller update. KDE really is a great desktop environment already but it has some small missing features. One is this difficulty to use usbstick and digital cameras, not to mention still cdrom and floppy. If you compare it to Windows, My Computer should be also in KDE. system:/ is a small replacement but still far far behind...

And other thing that I hope will be fixed soon is the icons on the desktop. At the moment it's quite difficult to organise them in straight lines and the desktop is a mess really fast if you copy anything to it.

well, imho "My Computer" is a totally braindeath concept. you can easily create a KIO slave for it, considered what is there: hard disks, cdrom drives and other media, and the config screen (??? why the heck? what has that to do with media?) and network. media:/ and locations:/ are much more logical.

by the way, the way windows works with drives (c: d: etc) is stupid. in unix this is done much more elegant: you can mount your drives anywhere.

OK, I agree that My Computer is stupid name and in Linux it's not very useful to show the hard disks since everyone can view the contents in the directory tree.

But using some removeable devises can be a bit difficult. Not just CDROM and Floppy which are quite well supported but the biggest problems come with digital cameras and usbsticks. IMHO there should be easier way to access these different devices, without the need to mount the devices manually...

There might be a easier way to do this, perhaps I just haven't found it yet...

I'm not doing any sieve related work currently. I am working on bug 50997 (client side imap filtering).

I have a prototype of client side imap filtering working. I still have at least one bug to track down (in the imap code) before it will be working reliably.

After that I have to test the prototype in the wild on different imap servers, measure the performance (to compare with other mail clients) and add some fault tolerance to handle unexpectedly losing the connection with the server (currently no mail should be lost but some mails may not be filtered).

Basically it's just quite time consuming. If people want to encourage me to spend more time on it, or work faster, then please see the commercial improvement system and consider making a pledge for Client side IMAP filtering.

It says it's a planned feature for inclusion. It doesn't say that it's done. If there's no intention for it to be in KDE 3.4, then it should be moved out of kdesupport anyway. That's what kdenonbeta means.

I hope Kmail will become completely compatible with Firefox. Konq is a great file browser but it absolutely sucks as a resource robbing web browser. Setting file association to open Firefox instead of Konq is useless and I ****ing HATE the way it writes to /var/tmp/kdecache-'user' before it opens (sometimes!) Firefox. I hope 3.4 or 4.0 fixes this grave weakness.

KDE? Are you listening? Some of us HATE Konq as a browser but love it as a file browser. Please take note!

" I'm no programmer and although I love Kde, I will always hate Konq as a web browser."

You will ALWAYS hate Konqueror as a web-browser? Even if Konqueror in KDE4 would blow Firefox away? Don't make claims you cannot keep. I cannot say that "I will ALWAYS love Konqueror as a web-browser", since it's possible that Konq starts to suck in the future releases. Anything is possible.

You must not only associate mozilla-firefox with HTML, you must also tell KDE, that mozilla-firefox can handle urls. Replace the command line in the desktop file with "mozilla-firefox %u". Then mozilla will handle the url, not kio.

this is not exactly true,
i have associated Firefox as default browser for kde 3.2 and added %u in the end
but still rss feed links in kontact newfeeds open only in Konqueror,
but in KMail links contained in e-mails open in firefox fine

This post really isn't nonsense since so many people have had problems with it. Do a search on the internet for making Firefox the default browser. MozillaZine doesn't even tell you about the URL handling part. The make default browser option also does not work correctly.

Heh, yes that is a partial solution of the problem but if only that was the end of the matter! The real problem extend beyond using another browser as the default.

If you associate html with another browser, Konq no longer functions as a browser. This isn't the desired functionality! For example a web developer may associate html with an editor/browser, but also test those pages in konq. Konq isn't good at playing both the role of internet browser and file browser -> sometimes those roles conflict. It won't happen just because I say so, but konq should be split into two seperate applications.

indeed choosing firefox in the kde control center works, >except that the browser page remains behind the kmail screen until i click on the desktop task bar item for firefox. anyone had to deal with this one?

I love KDE, have done since I first started using it (KDE 2 some version). I find 331 to be rock solid, I'm dying to look at 3.4 but don't want all kinds of stability problems... if the general feeling is good for it, albeit an alpha, I'll try it but I don't want to regret putting it on if you know what I mean.

In the past i've run alphas and never had any major issues. Been doing that since 3.0 alpha 1. Heh. You could always install KDE 3.4 to a separate directory, and as a different user than you usually use. That way you can try it out without the chance of messing up your stable KDE 3.3 data.