Linked by Rahul Gaitonde on Thu 15th Jan 2004 06:40 UTC
Around 3 weeks ago, I downloaded the 2nd beta of KDE 3.2 from their FTP site. I've been using this release every day since then. The purpose of my writing this piece is not to highlight KDE 3.2's new features and applications - read the Changelog at KDE's site for that - but to give you a complete picture of how it measures up to its previous versions in terms of everyday use. Does it make me more productive? Is the command line more efficient yet? Or, even better, does it make me use the command line more effectively? Read on...
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
> Under the "Peripheral" Section, there is a slight UI glitch that needs attention.
Which has been fixed in CVS already. Remember that this is a Beta and that many bugs will be fixed before 3.2 release and even after in the 3.2.x series.
> You can now right-click on a folder and "Open in New Window" or "Open in New Tab". In previous versions, this was limited to the "Web Browsing" profile, that is, for hyperlinks.
This is incorrect, KDE 3.1 supported tabs in file management mode with directories/files already.
> Tabs are now loaded by default in the background. In KDE 3.1, there was no such default
Perhaps no such default, but the option was there.
> I can't bookmark individual text/PDF/etc files in KDE's Bookmarks, only folders.
Wrong again. Open any file in Konqueror's internal viewer and call "Add Bookmark". Oder enter any URL in the bookmark editor.
> Kwrite and Kedit, though, seem to be treading on each other's feet. How is any one of them different from the other?
KEdit supports bidirectional editing, that's the only reason why is it still included. Next KDE's Kate/KWrite will support bidi, then KEdit will be dropped.
> Splash Screen does not work. [..] So I guess this is a Fedora RPM issue.
As a previous comment said, it's a local installation problem.