KDE Commit-Digest for 1st May 2011

Friday, 6 May 2011  |  Vladislavb

In this week's KDE Commit-Digest:

  • Calligra sees improvements to PPT and DOC support and work on SVM support and specifications amongst further bugfixing
  • Initial GSOC work on OpenStreetMap (OSM) rendering in Marble
  • NetworkManagement sees much bugfixing, support for Bluetooth tethering and a KAuth implementation
  • Solid's NetworkManager device interface updated to NM-0.8.2
  • Work throughout Plasma and Plasma-Mobile including QML Bindings for Plasma::ToolTips, a CLI tool allowing the addition of remote plasmoids and a small Remote Widgets browser along with much bugfixing
  • KWin now supports shadows with XRender and sees a slew of further bugfixing and optimization
  • Continued work on Skrooge
  • Kaffeine switches from Xine to VLC
  • Rekonq implements Opera-like feature to load favorites with Ctrl+Number
  • Work on QtRuby 3.0
  • Klipper now uses Prison for barcodes
  • Work on Oxygen icons
  • Middle mouse button on tab now changes the highlight color in Kate
  • Further work on the PublicTransport plasmoid
  • New Brazilian keyboard layout and bugfixing in KTouch
  • Android-Qt now has JIT support
  • Bugfixing and optimization of DrKonqi
  • Bugfixing in Digikam, KPhotoAlbum, KIO, KDE-PIM and Kile

Read the rest of the Digest here.

Comments:

Commit access - vdboor - 2011-05-08

Thanks for the digest, awesome read! I also liked to click through to some commits, to see how certain features (the KWin optimalisations) were actually implemented. Could the links to projects.kde.org be restored? I'd love to see these back!

OSM rendreing? - hmmm - 2011-05-08

How is it different than the currently available rendering? What's the plan? any chance that we are getting vector rendering? 3D?

Re: OSM rendering? - majewsky - 2011-05-15

While the current OSM support downloads pre-rendered graphics from OSM's Mapnik servers, the new OSM rendering just fetches the path data (i.e. where streets are located, how they are called and classified etc.) and creates the visual representation of this data by itself. While, given the current X11-based implementation, this requires more computational power on the computer running Marble, this approach is much better for OpenGL-based rendering, and the path data is much smaller on your disk than the pre-rendered images.