| 1 |
Dale writes: |
| 2 |
|
| 3 |
> Alex Schuster wrote: |
| 4 |
> > Dale, you brave, brave man, are you really using KDE4 now? |
| 5 |
|
| 6 |
> I am in KDE4. I still have KDE3 installed tho. Thing is, I'm still |
| 7 |
> using the same programs I was in KDE3. Dolphin looks nice and all but |
| 8 |
> I can't use it as root at all. |
| 9 |
|
| 10 |
Huh? No problem here. |
| 11 |
|
| 12 |
OT: does anyone know about dolphin somehow accessing all files it shows? I |
| 13 |
see this on a system that uses dolphin to browse remote files via the fish |
| 14 |
protocol. Previews are not enabled, but all the files are accessed, which |
| 15 |
means it takes about one hour until the directory is shown, because all |
| 16 |
files are being retrieved from a SAM-FS server. Maybe it is reading the |
| 17 |
magic number for each file? I will try konqueror now. |
| 18 |
|
| 19 |
> So, I went back to Konqueror to edit |
| 20 |
> config files and such. I don't use some of the programs that you are |
| 21 |
> using so I don't have the same issues. I use smplayer to do movies or |
| 22 |
> CDs. It doesn't care what DE you use. |
| 23 |
|
| 24 |
Ah, smplayer. Did not think about that. It was not important anyway - I |
| 25 |
had ripped a CD with K3b, and wondered why two tracks were swapped. BTW, |
| 26 |
what do you use for ripping? K3b is okay, but it does not remember changes |
| 27 |
like output path or file naming, I have to set this again for every CD. |
| 28 |
But smplayer does not recognise the CD either. I wonder why I do not have |
| 29 |
a /dev/cdrom device - only /dev/cdrom3, /dev/cdrw3, /dev/dvd3 and |
| 30 |
/dev/dvdrw3, all symlinking to /dev/sr0. |
| 31 |
|
| 32 |
|
| 33 |
> I do like the looks of KDE4. I still think they dropped KDE3 to soon. |
| 34 |
> KDE4 will get there but it is still having issues many months after |
| 35 |
> dropping KDE3. Bad thing is, I don't think they care about the users |
| 36 |
> they left hanging in the wind. |
| 37 |
|
| 38 |
I also think KDE3 was dropped too soon. While KDE4 is usable now for most |
| 39 |
things, it still has too many bugs, and a while ago it had many many more, |
| 40 |
while development and bug fixing of KDE3 was already stopped. |
| 41 |
On the other hand, manpower is limited, and I understand the decision to |
| 42 |
focus on the new project rather than doing stuff for the old one that soon |
| 43 |
noone will be using. KDE 3.5 is still there. I don't know about the |
| 44 |
security issues, would it be unsafe now to use KDE 3.5? I remember |
| 45 |
something about kpfd being masked due to security holes. |
| 46 |
|
| 47 |
Wonko |
Archives