GUADEC 2014 is almost upon us, and we are talking to the three keynote speakers who are lined up for this year’s conference. Nathan Wills – LWN editor, typeface designer and author – is one of these keynote speakers. His talk, titled Should We Teach The Robot To Kill, addresses issues relating to Free Software and the automative industry. We caught up with him to find out a bit more about this fascinating subject, as well as his views on Free Software conferences.
Karen Sandler is a veteran of the free and open source software world. Having completed an engineering degree, she has worked as a lawyer for the Software Freedom Law Center, was Executive Director of the GNOME Foundation, and recently accepted a position as Executive Director of the Software Freedom Conservancy. I interviewed Karen via email to ask her about her background and insight into various issues in the free and open source world.
When I'm enjoying the sun/wind/rain on the balcony, I tend to use my XO-1.75 for duties where most people would use a tablet. Reading/writing emails, browsing the internet, bug triaging or writing small fixes, release notes and all can be done fine on a small screen. My preference goes definitely towards physical keyboards, and less to their onscreen variants. Even when the keyboard is small, I like the typing on it much more than using a touchscreen for it. Of course, the space saving of not needing to display a keyboard helps too. But well, that aside..
The Tracker 1.1.1 release brings a brand new extractor, improves the extraction of content from ODT files by omitting line breaks and embedded tabs, and adds previously untranslated strings to the control component of Tracker.
Furthermore, the --watch command-line option has been added in order to allow the user to watch for database changes, language, author, and copyright information can now be extracted from ISO images, and AppData with screenshots for application stores has been added.
The colouring process was improved and sped up quite a bit when I bought an inexpensive USB Wacom graphire tablet a few years ago; I moved away from “cell shading” and achieved smoother results, quicker. Why Wacom? They’re the industry standard, their stylus/pen uses electromagnetic induction (no batteries required), and their hardware works out of the box with GNU/Linux and GNOME.
The mission: use GNOME Shell as the primary desktop for an entire week. Do I choose to accept it? Yes. It's easy enough to try something for a short time and discard it in a negative manner, which has been the case for me with GNOME Shell in the past, but perhaps it can be fun to challenge yourself to try something properly and for a longer time. Or perhaps you're a masochist! Either way, feel free to join me...
Also: In praise of Jim Hall
Orca works with applications and toolkits that support the Assistive Technology Service Provider Interface (AT-SPI), which is the primary assistive technology infrastructure for Linux and Solaris.
The developers are making some very big changes to Orca and it looks like GNOME 3.14 will feature several important new features. This is the second major overhaul done by the Orca devs, but they are not stopping here.
The GNOME Control Center allows users to configure various components of their system using a vast collection of tools. It's the hub for all the major settings that can be done in a GNOME environment, so it's easy to see why any update for it might be considered important.
In fact, the GNOME Control Center didn't see many changes in the previous GNOME 3.12 release, besides the regular updates and new features. Some changes have been made, but nothing really stood out.
As someone that has dabbled from time to time making small GTK applications for Fedora, one of the pain points when making an interface was just figuring out what specific icons were named, and what they looked like. My previous workflow was to open up /usr/share/icons/ in Files, and search for the icon and the icon name.
This is the second update for GNOME Shell in the current 3.13.x development cycle, and it looks like some interesting changes have been made, although there is no major feature to be observed.
According to the changelog, closing windows with attached modals is no longer allowed, GNOME Shell is no longer self-restarting on OpenBSD, and the behavior of window buttons with compositor menus has been improved.
Also, a workaround has been implemented for an atspi-related performance regression, numerous smaller bugs have been fixed, and a handful of translations have been updated...
The issue we had to solve is that GTK+ 2 and GTK+ 3 cannot be loaded in the same address space. Moving Firefox from GTK+ 2 to GTK+ 3 isn’t a problem, as only GTK+ 3 gets loaded in its address space, and everything is fine. The problem comes when you load a plugin that links to GTK+ 2, e.g. Flash. Then, GTK+ 2 and GTK+ 3 get both loaded, GTK+ detects that, and aborts to avoid bigger problems.