The Exploits of Plouj

This is documentation of how I used Yukon and Seom to video capture a Google Earth trip for a recent video project in Fedora 10. I used the official installation guide as a starting point.

Compile the Seom library

I choose to install both Seom and Yukon in a custom prefix /home/plouj/yukon, rather than the system wide /usr or /usr/local.

$ svn co https://devel.neopsis.com/svn/seom/branches/packetized-stream seom
$ cd seom
$ ./configure --prefix=/home/plouj/yukon --arch="x86" --cflags="-W -Wall" && \
make CC="gcc -m32" && make install LIBDIR="lib"

Note that “–arch=”x86″ and “-m32″ are only necessary for me because my operating system is 64bit and I need 32bit versions of seom and yukon (to work with 32bit Google Earth).

Compile and install Yukon

$ svn co https://devel.neopsis.com/svn/yukon/branches/rewrite yukon
$ cd yukon
$ ./configure --prefix=/home/plouj/yukon/ --libdir="lib" --arch="x86" && \
make CC="gcc -L/home/plouj/yukon/lib -I/home/plouj/yukon/include -m32" && \
make install

Install Google Earth for Linux

Obviously get it here: http://earth.google.com/

Modify the Google Earth startup script

Since I chose /home/plouj/bin/ as the “Binary path” for Google Earth I was editing /home/plouj/bin/googleearth. All I had to do was to add yukon/seom library and executable paths at the end of the script:

...
cd "${GOOGLEEARTH_DATA_PATH}/"
LD_LIBRARY_PATH=/home/plouj/yukon/lib/:$LD_LIBRARY_PATH \
PATH=/home/plouj/yukon/bin:$PATH exec yukon "./googleearth-bin" "$@"

instead of the original:

cd "${GOOGLEEARTH_DATA_PATH}/"
exec "./googleearth-bin" "$@"

Capture

Finally, the capture process is well documented on the Yukon website.

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.

In April I was privileged to be one of the 1125 students who got selected for the Google Summer of Code (GSoC) 2008 program. I was accepted to work on a project to implement Panorama Viewing in VLC. This summer was my last chance to participate in GSoC as a student because of my graduation date so I was very excited to have this once in a lifetime opportunity. More recently, I received an offer for a full-time “Linux Application and OS Developer” position at SOMA Networks – a company in downtown Toronto. Given the importance of a permanent job and having read the advice from previous GSoC participants, it didn’t take me long to decide to cancel the GSoC project and focus on the new job. Due to timing, however, I still managed to receive an acceptance gift from Google. The gift is a book called Beautiful Code: Leading Programmers Explain How They Think. Apart from being an interesting read, it’s a nice souvenir to keep in memory of the many hours I spent preparing for GSoC by choosing a project to apply for and writing multiple proposals.