1 |
Alex Schuster wrote: |
2 |
> Dale writes: |
3 |
> |
4 |
> |
5 |
>> Alex Schuster wrote: |
6 |
>> |
7 |
>>> Dale, you brave, brave man, are you really using KDE4 now? |
8 |
>>> |
9 |
> |
10 |
>> I am in KDE4. I still have KDE3 installed tho. Thing is, I'm still |
11 |
>> using the same programs I was in KDE3. Dolphin looks nice and all but |
12 |
>> I can't use it as root at all. |
13 |
>> |
14 |
> Huh? No problem here. |
15 |
> |
16 |
> OT: does anyone know about dolphin somehow accessing all files it shows? I |
17 |
> see this on a system that uses dolphin to browse remote files via the fish |
18 |
> protocol. Previews are not enabled, but all the files are accessed, which |
19 |
> means it takes about one hour until the directory is shown, because all |
20 |
> files are being retrieved from a SAM-FS server. Maybe it is reading the |
21 |
> magic number for each file? I will try konqueror now. |
22 |
> |
23 |
> |
24 |
|
25 |
This is what I am talking about. Dolphin will browse through |
26 |
directories but as soon as I click to open a text file, it gives a |
27 |
error. I have discussed this on the kde list and it is a known |
28 |
problem. One even said the code was written to prevent that but others |
29 |
say it is just not fixed yet. So, I still use Konqueror just like I did |
30 |
in KDE 3. |
31 |
|
32 |
|
33 |
>> So, I went back to Konqueror to edit |
34 |
>> config files and such. I don't use some of the programs that you are |
35 |
>> using so I don't have the same issues. I use smplayer to do movies or |
36 |
>> CDs. It doesn't care what DE you use. |
37 |
>> |
38 |
> Ah, smplayer. Did not think about that. It was not important anyway - I |
39 |
> had ripped a CD with K3b, and wondered why two tracks were swapped. BTW, |
40 |
> what do you use for ripping? K3b is okay, but it does not remember changes |
41 |
> like output path or file naming, I have to set this again for every CD. |
42 |
> But smplayer does not recognise the CD either. I wonder why I do not have |
43 |
> a /dev/cdrom device - only /dev/cdrom3, /dev/cdrw3, /dev/dvd3 and |
44 |
> /dev/dvdrw3, all symlinking to /dev/sr0. |
45 |
> |
46 |
> |
47 |
> |
48 |
|
49 |
I have used tkdvd to burn a DVD. It ain't pretty but it worked. ;-) |
50 |
|
51 |
>> I do like the looks of KDE4. I still think they dropped KDE3 to soon. |
52 |
>> KDE4 will get there but it is still having issues many months after |
53 |
>> dropping KDE3. Bad thing is, I don't think they care about the users |
54 |
>> they left hanging in the wind. |
55 |
>> |
56 |
> I also think KDE3 was dropped too soon. While KDE4 is usable now for most |
57 |
> things, it still has too many bugs, and a while ago it had many many more, |
58 |
> while development and bug fixing of KDE3 was already stopped. |
59 |
> On the other hand, manpower is limited, and I understand the decision to |
60 |
> focus on the new project rather than doing stuff for the old one that soon |
61 |
> noone will be using. KDE 3.5 is still there. I don't know about the |
62 |
> security issues, would it be unsafe now to use KDE 3.5? I remember |
63 |
> something about kpfd being masked due to security holes. |
64 |
> |
65 |
> Wonko |
66 |
> |
67 |
> |
68 |
|
69 |
I understand the second hand but it still leaves the users out in the |
70 |
cold. I'm hoping the release of KDE 5 will be handled better but I'm |
71 |
not holding my breath. |
72 |
|
73 |
Dale |
74 |
|
75 |
:-) :-) |