Linux 4.2 May Finish Fixing Up Radeon Audio Support
Since the Linux 4.0 kernel there has been DisplayPort audio support for the open-source Radeon driver. That DP audio handling came after a big rework to the audio code in the Radeon DRM kernel driver. A half-year later it looks like all the audio code is now cleaned up and ready.
Also: Radeon Gallium3D Tackles A Bit More, OpenGL 4.1 Patches Pending
NVIDIA 352.30 GPU Driver For Linux Has Been Released
LibreOffice 5.0 Right Around the Corner, Guided Tour of LibreOffice
Major release LibreOffice 5.0 is due next Wednesday with a lot of new features. Italo Vignoli today posted The Road to LibreOffice 5.0 in which he looks back at all the added features since January 2015 with version 3.3. Today's summary shows "the impressive amount of new features added to LibreOffice since version 3.3."
LibreOffice 3.3 was released in January 2011. This release was significant in that the development and management of LibreOffice had come together in a short time and put out a release that brought several new features. SVG support, easier title and page formatting and numbering, improved ergonomics in Calc, and Microsoft Works support were among the newest features added by The Document Foundation.
I have been using LibreOffice since it was called Star Office and all documents opened in a tabbed interface, as in most modern spreadsheet applications (anyone remember those days?). From those early days until now, I have considered Star Office/OpenOffice.org/LibreOffice to be an excellent, if not superior, tool compared to many on the market.
CoreOS CEO: Security is fundamental
In an interview, CEO Alex Polvi claims his company invented the cloud-native OS category and discusses how CoreOS's update strategy differs from the likes of Red Hat
KDE and Akademy
Many of you already know that FISL (The International Free Software Forum) is one of the biggest FLOSS conferences in the world. From 8 to 11 July 2015, 5281 free software passionate people met in Porto Alegre (South Brazil) for the 16th FISL edition, enjoying activities such as talks, panels, hackathons, workshops, and community meetings. All kinds of FLOSS-related topics were in place: development, translation, artwork, education, robotics, entrepreneurship, audio-visual, women and gender, politics, academia and research ... Phew! that's tiring :) KDE has a long and memorable history at FISL and it wasn't different this year.
The beginning of the day was reading some social media in the morning with breakfast catching up with the times. While going though my Google+ feed I saw a post that I seen before about the a bug with a krunner plugin. The plugin in question was this which Riddell, Dan and I debugged to find some more info about the bug such as that is effects Kubuntu, Arch and openSUSE so it is upstream related.
The organising team have done a fantastic job: we’ve had free busses running from our accommodation to the venue, video recording of talks (which I’m sure someone will post about soon), easy to access food, two parties and people always on-hand to provide information.
KDE Activities are multiple desktops. While easy to understand, they open up the possibility of new methods of workspace organization as well as new ways to layout the desktop. They deserve to be recognized as an innovation as important as tabbed browsing, and should be a part of every desktop environment, yet most users have only vaguely heard of them, and even fewer have tried them.
When a feature so elegant is ignored, something has clearly gone wrong -- but what, exactly?
One thing is certain: Activities are one of the least unpublicized features on any desktop. From their introduction in KDE 4.0 to their implementation in Plasma 5, Activities have never had any online help. If you go to the desktop toolkit, you can click on Activities, but nothing suggests why you should bother. How to create an Activity is reasonably obvious with a little exploration, but why you would want to is never explained.
While FOSS Force gave you a look at setting up KDE Plasma on the desktop in Don Parris’ article last week, KDE recently jumped into the mobile fray by announcing KDE Plasma Mobile at their Akademy conference this week in Spain.
While it joins an already crowded field, with the likes of Android, Ubuntu Touch, Firefox OS and others already in the mobile OS space, Plasma Mobile “offers a free — as in freedom and beer — user-friendly, privacy-enabling, customizable platform for mobile devices,” wrote Sebastian Kugler, a lead architect, on KDE’s website. “Plasma Mobile is currently under development with a prototype available providing basic functions to run on a smartphone.”
The original plan was to allow an extension to handle the more crazy form-factors, but as I was blueprinting the APIs on paper I quickly found the tab-bar becoming a nightmarish monster which would have made custom tab extensions painful. Ultimately as a shortcut until a nice API can be made (and many more critical APIs can be rolled out) I’ll be adding sidebar tabs as a native feature. I may look at some sort of button form-factor as well, such as the ones commonly seen in mobile browsers.
During Akademy I hold a session about porting applications to Wayland. I collected some of the general problems I saw in various KDE projects and want to highlight them in this blog post, too.