Paul Kocialkowski's coding blog

As I am doing software development that sometimes requires a lot of resources (mainly when building Android/Replicant), I recently decided to get myself some new hardware. I was previously running with a dual-core Pentium 4 running at 3.00Ghz, along with 4G RAM (the motherboard chipset is limited to 4G), two Hard Drive Disks and an nVidia graphical card. All was running under Trisquel 5.0, with the nouveau driver for nvidia cards, that didn't permit outstanding hardware acceleration (though it was fairly good enough to play 720p videos).

Finally I decided to get an Intel i3 CPU, dual core at 3.30Ghz and an adequate motherboard, both coming with SandyBridge support. I ended up buying 8G of DDR3 RAM, which is fairly enough for Android/Replicant build to stay on RAM (it finished on SWAP with my old hardware). I'm particularly amazed of SandyBridge, that technology that permits the CPU to hold an Intel GPU that can be used with an appropriate motherboard. It is very-well supported by Linux (and by Linux-libre as well), Xorg and Mesa (compared to all of what I've tested with Linux-libre). I was able to play Nexuiz at 1280x800 with nice effects, 0 A.D. with shades and water reflection disabled and a few other ones (Mania Drive, OpenArea, etc).
All that came with a 60GB SSD used as rootfs. It really speeds up the boot process alot! (The BIOS is actually taking longer than grub up to gdm)

On the software side, I stick to distributions promoting and distributing only free software. I thought about getting to Debian as I mostly agree with their decision to distribute a kernel free of firmwares, but that will load them when present (which is what we do in Replicant too). Though, I'm using Trisquel since a year now, and I kinda got used to it. As usual, it is very usable, ready and nice-looking! As I have no hardware requiring non-free software to be loaded, I'm totally fine with Linux-libre, even though I agree more with the Debian way of things regarding the kernel.

Let's cut-off the long and boring text and get to serious matters. Trisquel decided to stick with gnome-panel while Gnome 3 features the new gnome-shell interface. I'm very pleased with that decision, as I already tried gnome-shell and find it less usable than good-old gnome-panel, mainly because there is no really quick way to have the windows listed, to switch from one to another and to reduce them.
When I first ran into Gnome "fallback" experience (that is what gnome-panel is called now), I got very disappointed by the unavailability of right click on bars to customize them (move stuff, add widgets, etc). I though it was the end of the gnome-panel era and sincerely thought that this fallback experience was just a quick hack, with no possible customization. Thankfully, I was wrong. You can actually do the very same changed in that GTK3 gnome-panel by holding the Alt key while doing right-click on a panel. After discovering that, I quickly got back into my old setup, with some adjustments.
The main bummer I faced is that Trisquel theme was apparently not designed to be used with the "menu bar" applet, that holds Apps and Places. It was really ugly-looking, so I strongly recommend you to use this css layout (in /usr/share/themes/Trisquel/gtk-3.0/apps/): gnome-panel.css

As you can see on the screenshot up there, I am using conky to display time, date and various infos about the system. Here is the conkyrc, designed (with absolute values) for a 1680x1050 screen: conkyrc, draw_bg.lua.
Also, if it turns out conky won't stop flickering, even if you're using double buffer and all, make sure that maximum_width is greater than the actual width conky uses. If you didn't define maximum_width anywhere and conky won't stop flickering, that may very well be the reason. Define it with an appropriate size and it may help to sort things out. That's one problem I had while doing that conkyrc.

As for an icon theme, I'm using elementary, with the Trisquel logo on top. It has a huge benefit: the icon that shows up when changing the volume will no longer be ugly as it's obviously resized from a non-vectorial image. It'll show a nice and clean white speaker icon. When I was doing that conkyrc, I also turned on metacity compositing, that is a very unknown feature but permits some nice stuff while remaining simple (no outrageous effect that will slow you down). For instance, it gives that volume popup clean round edges, instead of the sharp ones, as well as some nice transparency. If your GPU can handle it, I strongly advise to turn metacity compositing on. That's just one gconf key to set: gconftool-2 -s '/apps/metacity/general/compositing_manager' --type bool true

So, I decided to start out a new dev blog, focused on software (and sometime hardware) development I'm doing. Currently, it mostly takes place in the Replicant project, a fully free Android derivate. I'm hoping I'll get to Coreboot development soon, even though it seems quite hard at first sight.

I used to write on http://blog.paulk.fr, but that was in french and so did limit a lot the scope of people able to read my posts. I'll probably keep writing there sometimes, but probably for non-technical stuff (there is a wide range of subjects that I'd be interested to talk about).

For this blog, I decided, for a change, to use a non-mysql blog engine. I would gladely have used heavy engines as Dotclear or Wordpress, if any of these supported sqlite (which is way easier to handle for personal-use blogs as mine). Anyway, I got to PluXml and gave it a try. It's apparently written by a bunch of frenchies (the comments on the code are in french). I had to do a couple of personal modifications to make it fit my expectations.

First thing is about the theme: the default one is IMO kinda ugly. As I didn't want to spend the crazy amount of time that creating a theme from scratch requires, I just picked a good-looking one and did a few changes. The theme is called Mystique. I think it was designed for Wordpress (as it's used on coreboot blog) but then got ported to PluXml. After small changes (that I won't list there, because I already forgot about half of them), I came up with something good enough for my daily use on this blog. The result is available for download at: http://download.paulk.fr/pluxml/mystique.tar.gz and should be GPLv2-licensed.

About PluXml code changes, I made a diff from someone's code that I found on a forum (the author is given in the source code). It permits to have a tags cloud. It's available there: http://download.paulk.fr/pluxml/tagArtsList.diff. Last change I did is a new function to list the articles taged with a particular tag. The code is used to show selected posts on the top bar of the blog. It's available as well: http://download.paulk.fr/pluxml/artTagsCloud.diff under the GPLv2+ license.