The Exploits of Plouj

This is a quick, biased, un-authoritative and incomplete evaluation of Google’s photo manager Picasa. In total, I’ve spent no more than a couple of hours using Picasa. I’ve already chosen to use Digikam as my photo manager so I was going to blatantly ignore its many faults and ruthlessly criticise Picasa. Don’t read this post to learn about Picasa. Download it yourself or look for more comprehensive reviews elsewhere on the ‘net. I’m writing this because I promised a friend at work to look at Picasa and later I decided to put my observations in writing. You’ve been warned.

What I liked

• importing images into the gallery using a separate and (seemingly) lower priority thread makes  the UI usable right from the start.
• it hasn’t crashed on me while importing 11,000+ pictures into the gallery
• cute, but useless timeline display application:
  
• Google provided an RPM repository which makes installing, upgrading and un-installing very easy for me

What I disliked

• simplified colour tuning controls. They might be OK for beginners, but they don’t appeal to someone like me who has used colour curves before.
  
• at first launch, Picasa started to import images from my whole home directory, which is huge and has tonnes of pictures. This only made me realize just how many images I have (mostly application icons and game project textures) that really don’t belong in a photo catalogue. I also couldn’t find a way to tell Picasa to stop and only look in certain directories.
• Picasa froze when I first tried the “tools > folder manager”. It worked on the second attempt, and I realized that this is the tool used to tell Picasa exactly what directories to include when searching for images.
• the “Tools > Experimental > show duplicate pictures” function was indeed experimental. It seemed to just give me a list of images without indicating what the duplicate pairs (or groups) were.
• the search results for the “show duplicate pictures” also showed a strange status bar at the top of the main window. I never figured out the meaning of the constantly changing seconds value or what GPixel was referring to.
  
• the “importing indicator”, although neat (it showed what picture was being imported in real time), was rather useless. Most importantly, it did not show the total progress percentage. When I tried to close it, it seemed to just re-appear in a different location along the side of the main Picasa window. Then it simply started sliding up and down without explanation.
• after a lot of clicking, I managed to loose the album list view in the left pane and had to re-start Picasa
• ugly dithered splash screen image – c’mon, we’re not in the 1990’s anymore!
• the scrollbar in the main view controls the view scroll speed, not the actual movement of the view – annoying and misleading. It didn’t let me get near the bottom right away, and I got dizzy every time I scrolled. However, I think the search result view actually changed the scroll bar function to the usual scroll bar for reasons beyond me. [Edit: after more use I realized that the way the scroll bar behaves in Picasa (combined with really smooth scrolling) helps with showing many photographs to other people looking at your screen. You can just drag the scrollbar just a bit to achieve a nice steady scroll speed and discuss the pictures instead of having to continually "pull" the images up or down with the mouse.]
• I somehow totally failed to find the familiar timeline/calendar view of my photos. Does Picasa really not have a way to organize photos in this manner?
  
• this is proprietary software from Google. I actually like a lot of stuff that comes from Google, but when it comes to software licensing, I don’t play favourites. I simply try to avoid non-Free Software as much as I can.

What I ignored

• uploading to and syncing with various web services
• ordering prints
• printing to a local/personal printer
• picture backup feature – rsync is fine for me
• passport photo function – This made me realize that I’m definitely not the intended audience of Picasa
• the ability to store video flies, which I consider to be outside of the scope of this program
• anything else I haven’t mentioned, obviously

Final thoughts

In conclusion, I’ve used my experience with Picasa to re-inforced my decision to stick with Digikam – a Free/OpenSource Software photo manager.

The other day I needed to setup bridged networking for a Qemu virtual machine. Although I found a rather well written generic TAP interfaces guide on Wikibooks. It only explained how to configure a network bridge on a host machine with a static IP. I wanted to do this on a host that used DHCP. Plus I wanted to keep all configuration in Fedora specific places. Having discovered a good way to do this through experimentation after a few fruitless Google searches I thought it would be useful for myself and others to have the configuration documented here.

ifcfg-eth0

First, I changed the host’s (auto-generated) /etc/sysconfig/network-scripts/ifcfg-eth0 script from this:

# Attansic Technology Corp. L1 Gigabit Ethernet Adapter
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:1D:60:35:A7:64
ONBOOT=yes

to this:

# Attansic Technology Corp. L1 Gigabit Ethernet Adapter
DEVICE=eth0
TYPE=Ethernet
BRIDGE=br0
ONBOOT=yes

This turns off DHCP on the physical Ethernet device and just specifies that it will be connected to or a part of a bridge.

ifcfg-br0

Second, I created /etc/sysconfig/network-scripts/ifcfg-br0, which will be called to setup a bridge device:

DEVICE=br0
TYPE=Bridge
BOOTPROTO=dhcp
HWADDR=00:1D:60:35:A7:64
ONBOOT=yes
DELAY=0
STP=off

As you can see, most of this configuration is copied from eth0 plus the bridge configuration as per the Qemu Wikibook.

qemu-ifup/down

Third, I shortened the /etc/qemu-ifup and /etc/qemu-ifdown from Wikibooks to get this:

/etc/qemu-ifup:

#!/bin/sh
USER=$(id -un)
sudo /usr/sbin/openvpn --mktun --dev $1 --user "$USER"
sudo /sbin/ifconfig $1 0.0.0.0 promisc up
sudo /usr/sbin/brctl addif br0 $1

/etc/qemu-ifdown:

#!/bin/sh
sudo /sbin/ifconfig $1 down
sudo /usr/sbin/brctl delif br0 $1
sudo /usr/sbin/openvpn --rmtun --dev $1

Here I basically removed all of the configuration that is taken care of in the sysconfig scripts. I also made explicit use of sudo simply because that is my preference.

Final steps

Now I can simply run /etc/qemu-ifup tap0 once to create a TAP device, and use something like: qemu-kvm -hda /virtual-machines/fedora9.disk -m 512 -net nic -net tap,ifname=tap0,script=no to start a virtual machine. When I’m done running the virtual machine, I can run /etc/qemu-ifdown tap0 to remove the TAP device.

All this sounds simple now that it’s working, but initially it took a lot of guessing on my part so I’m documenting it here for the future.

I would appreciate it if someone can point me to the official Redhat/Fedora documentation on editing /etc/sysconfig/network-scripts/ scripts.