> I'm skeptical: I found some terrible phrases in the archives as "KDE3 > IS Technically obsolete..." that I do not understand and "Instead of > accusing me of trolling here..." that I understand all too well. > I feel a little cold. Regarding KDE3 being obsolete, that is in reference to the last officially released version of KDE3, which is 3.5.10 and was released 08/26/2008, almost three years ago. As there have been new official releases of KDE since then (the 4.x series), it can be said that KDE3.5.10 is obsolete ***from the point of view of KDE e.V.***. That being said, the KDE3 codebase lives on in the Trinity project, and I hardly consider the forked codebase to be obsolete. > > As a user, I thought that KDE 3.5.11 would have restored the "rule" > graphic screen and the "magnifying glass" screen, and would have > provided a program for cleaning temporary files and other such > utilities... In short, a work of "finishing" more than "inovating". The > software still need more power to operate. This way of thinking, which > is not limited to software, pushed to the ecological disaster and death > ... This is exactly what we are doing. If you look in the release notes for 3.5.11, 3.5.12 you will see that new features have been added to extend the desktop and add ways to do things via the GUI that previously required hand-editing configuration files or using the terminal. I am unfamiliar with the ""magnifying glass" screen" personally, can you provide a link to a screenshot or similar? We do have kmag in the archives, is this what you were looking for? I encourage users/testers/developers to file enhancement request bugs on http://bugs.pearsoncomputing.net, and if you see an existing enancement bug you want to see fixed, please say so on the bug report. This will help us know what our users want to see. That being said, this is still a volunteer project, so the developers here will probably fix bugs that affect them personally first, before moving on to bugs that they do not routinely experience. I hope this clears up some of the confusion. :-) Thanks!