J’ai découvert par hasard qu’on peut faire un clic droit sur le “profil” d’un périphérique dans pavucontrol pour renommer le périphérique. Or, cette fonctionnalité n’est pas disponible par défaut puisqu’il faut un module supplémentaire (sous Fedora, du moins). Pour faire un essai en temps réel:
Cleaning up my apartment today, hoping to get rid of a pile of draft papers that has been cluttering my space for six months, I’m taking the opportunity to write about what this particular pile of paper means (yes, my blogging backlog goes that far—I am draining the swamp one post at a time!)
Thanks to GNOME, we will be able to get some reinforcements for Pitivi this summer.
We’re very pleased to have Lubosz Sarnecki making a comeback! In 2011 he implemented the cairo-based clip transformation (zoom/resize/crop) feature in the viewer. Lubosz is quite experienced with OpenGL, Blender and GStreamer, as you can see on his blog and the variety of projects he contributes to.
Eventually, someone proposes a design or idea that looks interesting, and you realize that to truly realize it, you should also implement an audacious new feature: a way to visually represent an entire timeline as a thumbnail (that one is an open question, by the way; if you have some clever ideas, feel free to share them)
…and to display new feature B properly, you should also consider—ideally—being a good citizen and implementing feature C upstream, in the toolkit you use instead of doing your own thing in your corner.
This kind of serendipity and interdependence happens regularly in FLOSS applications like Pitivi where we prioritize quality over “meeting shareholders’ deadlines and objectives”, which is why we sometimes take more time to flesh out a solution to a problem: we aim for the best user experience possible, all while negotiating and working with the greater software ecosystem we live in, instead of silently piling up hacks in our application… and we depend on the involvement of everyone for things to progress.
Since my previous technical update in January, I haven’t had time to touch Pitivi’s code. Thankfully though, Alexandru Băluț has been filling the gap with a ton of refactoring work: around 150 commits! That took a fair amount of time to review and merge, believe me. Besides code cleanup, he also finished the port of the viewer to a cluttersink, fixed fonts and theme colors detection for the timeline (so it looks fine even if you’re not using the Adwaita GNOME theme).
Alexandru took the opportunity to not only fix some bugs, but also do some visual refinements on the timeline ruler: it now shows hours and miliseconds only when needed (depending on the zoom level) and subtly grays out units that did not change from one “tick” to another, so your eyes can focus on what actually changed:
Besides catching a cold and shovelling snow, this holiday season I spent some time scratching itches in Pitivi. For starters, thumbnails generation: if you’ve been using the new Pitivi, you certainly ran into this:
Some of you may be familiar with the good old “fix it twice” adage: fix the problem and then ensure it never happens again.
Last year, when I made Pitivi’s automatic backup feature work, I requested someone to write extensive automated tests for it (with Dogtail), so that I could feel confident about this feature never being broken again, even if it underwent massive refactoring or if everything else changed around it.
In 2005, I had a crazy idea upon which I started the Specto project. Initially, I thought I’d call my revolutionary piece of software WhileYouWereOut (continuing the world’s tradition of ill-chosen project names), because it really was about solving a core “want” in my life: to leave my computer alone and catch up with events when I’d come back in front of it.
The core feature was to watch webpages for updates: back then, I did not know about syndication feeds, and I was sick of refreshing ifolder.com every single day hoping for a release of the peer-to-peer version of iFolder (for which we still have no equivalent today).
It is fashionable these days, especially for the Slashdot crowd, bloggers, kernel hackers and other people depending on “feature X that has not fully polished”, to throw mud at the efforts that have been made towards redesigning the Fedora Linux installer.
With some help from luisbg, I finally reworked and merged a 2-years-old patch of mine. It turned out to be less trivial than expected, because we had to change the settings backend to allow loading/reading configuration files at runtime for our dynamically-generated tab components. So, what the heck does this mean to you? Automatically saving and restoring the state of our dynamic detachable tabs/components. This is a nice improvement for those of you who want to spread the PiTiVi UI across multiple displays:
Here’s a tricky usability question: how would you represent the actions of grouping and ungrouping clips on a timeline? (Un)grouping is used for changing the way selections affect a set of clips. It allows you, among other things, to separate and remove the audio from the video of a clip.
It is very hard to find any relevant prior art that could guide me for this metaphor (most applications don’t have icons for these, they are only available through menu items). Inkscape can get away with icons that show “drag handles”, but we don’t have those in Pitivi. (un)grouping is quite an abstract concept, given that it does not visually change the clips in any way, it just changes the way they react to selections.
A question has been bugging me for some time: what’s the reasoning behind the dconf hierarchy/naming scheme as can be seen in dconf-editor?
org.gnome.*, org.gtk.*, ca.desrt.*, org.freedesktop.* … okay, I get that those are meant to look like reversed URLs, that part makes sense… but not as much when you have desktop.gnome.*, desktop.gstreamer.*, apps.*, a11y.*
So, since it seems everybody’s been talking about startup time these days, I’ll admit I tend to secretly obsess over that too. Well, it’s not so secret given that I’ve blogged about profiling work on Specto and PiTiVi before… anyway.
I believe you should provide your developers with the fastest computers to do the development, and five years old computers to do the testing. I therefore do my benchmarks on three computers: Continue reading “Pitivi’s startup time”
In the same vein as my don’t make me scroll post, I sent a couple of patches Richardwards to, among other things, solve one of the biggest itches I had with gpk: the fact that I had to care about sizing it up constantly on my 1920×1200 24″ monitor. Before, if you started gpk-application (or the update manager, or various other windows), it showed up like this:
I have been attending the Desktop Summit since the opening on Saturday, and it’s been a great experience reconnecting with familiar faces and meeting new ones. Tomorrow, the PiTiVi and GES hackfest officially begins, in room “1.308/2” (the building is at 24 Dorotheen Straße). Come join us at any time of the day (and since we’re slightly insane, we might also end up continuing hacking during the evenings too). This lasts until Friday.
Although the hackfest officially starts tomorrow, we obviously could not resist the temptation to get started in the past two days.
Okay, so GNOME/GTK+ doesn’t show icons on buttons anymore unless they are part of a toolbar or you specifically request that they show up. The problem is that because of this, PiTiVi’s play/pause button would end up not showing anything at all. Thus, back then Alessandro inserted this piece of code to force displaying icons on all buttons in PiTiVi.
It just occured to me that since I’m on Planet GNOME, I can shamelessly bribe people into fixing bugs in exchange for beer and cheese and whatnot. Wanna get drunk at the Desktop Summit this year? Then please fix these trivial-yet-infuriating usability issues that have been preventing me from using Evolution‘s calendar for years: