In this week's KDE Commit-Digest: Plasma continues to mature, with improvements to the Twitter applet (and the creation of a complementary data engine), and the adoption of a common visual style for Plasmoids, and the integration of support for SuperKaramba applets through the creation of the SuperKaramba Plasmoid. More work on the re-implementation of the Magnatune interface within the new music store framework, and integration of the recent Plasma work for Amarok 2. More work on KBlocks, whilst KMines and KLines become the first KDE applications to take advantage of the recently-developed KPixmapCache. More work on colour mixing in Krita. Import of Habitat, a realistic interaction environment, to playground/edu. A return to work on Cokoon, a framework for widget and window decoration creation. RSIBreak, KCall, and the Kickoff menu start to be ported to KDE 4. KDE 4.0 Beta 1 is tagged for release.
Comments
I apologize for my language. It's the internet. It's how people talk. But, I apologize nonetheless.
I still think that it's a step backwards. Spacing is a BIG problem I find in styles on Linux. It simply does not make good use of screen real estate. GTK is especially guilty of this, but Qt/KDE styles aren't innocent either. Windows and Mac are both much better about making good use of screen real estate.
"I apologize for my language. It's the internet. It's how people talk. But, I apologize nonetheless."
It's the internet?? it's how people talk??
Maybe lamers on slashdot/digg talk like this, but it's not *the internet* for sure.
I retract all my comments :(.
Better not to air an opinion on this holy cow of a subject. (You are not alone)
Just wait for the avalanche of styles coming for KDE4 on www.kde-look.org.
Even QT4 have an CSS style tweakability now, so I have heard.
The new arrows are beautiful, and I was a fan of the old ones O_o
I think this looks great for a Beta, actually really good for a beta. Thanks goes out to all the developers, I know you guys are trying your best and I can't wait to test the Beta when it's official. You haven't let me down yet and I'm sure you won't in this release. May the wind be always at your Back!
Thank you for posting these!
thanks Emmanuel for the screenshots, i would like to make a formal apologize for my trolling about the kicker.
you rock guys, i think many people are just jealous about the progress made to kde.
So kicker will be out of kde4? Not that it's a bad thing... I think plasma would be a really good substitute for it. Just need to build a start menu in plasma and it should work...
IMHO the oxygen theme doesn't really have as much OOMP as the default kde3 theme. There's just something lacking. Hopefully the artist will be able to bring it together in later versions...
ben
The koffice website http://www.koffice.org is down.
(DNS) problems; fixed now.
I wonder if KDE4 will improve the settings saving policy. Currently I can hardly use KDE in heterogenious networks since different KDE version destroy the desktop settings.
In our network, each workstation has access to the same home directory containing the KDE settings in ~/.kde
When using different KDE versions, older KDE versions do not support certain settings and overwrite them such that the desktop looks odd when logging in with the original (newer) KDE version again. The problem with the settings is more dramatical when using different distributions in the same network. Among openSUSE workstations it at least "works", but when logging in from a Fedora box, they use their own widget style, their own specific desktop icons, their own KDE menu side image, etc. Kicker's panel configuration at least breaks (applets, alignment, menu bar on top...)
Do I just miss a point, such that I can KDE prevent doing this or will situation improve in KDE4?
I don't know how this actually works, but I haven't seen any references of anyone working on it. So if you want to do something about it, you should try to figure out what goes wrong (not necessarily a coding thing, btw), and try to create a detailed bugreport. Of course, attaching a patch to that bugreport is the fastest way to get this fixed...