Ubuntu Hardy - Worse Photo Import Than Before

I like f-spot a lot, but it has a few things that really bug me. I guess I should stop complaining and get involved, but then I'd have to learn C#. I don't know if I can bring myself to do that ;-) Anyway, here is what I used to see when I connected my digital camera to my Ubuntu 7.10 machine:

Now that I have Ubuntu 8.04, when I plug in my camera I first see this:

Yes, that's two confusing choices for one camera. Choosing either gets the same results:

Yup, it's offering to download some xml files and some other non-image files, and more room is devoted to showing you the full path to the files (that you really don't care about) than to showing you the actual thumbnail image. The option to delete from the camera what you just downloaded is gone too. Oh, and no videos will actually show up in F-spot, the program that is now doing this importing. Was anyone who uses a digital camera consulted on this move? I'm not alone in not liking this change.

Comments

danielpoe said…
Hi,

just as an information, the first import dialog (from 7.10) looks suspiciously like the gthumb import dialog, so if you want to have the old dialog back you could change this in the default application for photo import. And I agree the f-spot dialog really needs some love. Strange for an application which cares so much about user interaction to have such a strange dialog. I guess they didn't focused on this to much so far ...

Rgds,
Daniel
June 9, 2008 at 12:14 AM
Bryan said…
Daniel, that's true and I should have pointed out that it changed from gthumb to f-spot. The thead I linked to is all about changing the default from f-spot to gthumb. Problem is, I really like f-spot and I do want my photos imported into it.
June 9, 2008 at 9:37 AM
Post a Comment

Popular posts from this blog

SystemVerilog Fork Disable "Gotchas"

This is a long post with a lot of SystemVerilog code. The purpose of this entry is to hopefully save you from beating your head against the wall trying to figure out some of the subtleties of SystemVerilog processes (basically, threads). Subtleties like these are commonly referred to in the industry as "Gotchas" which makes them sound so playful and fun, but they really aren't either. I encourage you to run these examples with your simulator (if you have access to one) so that a) you can see the results first hand and better internalize what's going on, and b) you can tell me in the comments if this code works fine for you and I'll know I should go complain to my simulator vendor. OK, I'll start with a warm-up that everyone who writes any Verilog or SystemVerilog at all should be aware of, tasks are static by default. If you do this: module top; task do_stuff ( int wait_time); #wait_time $display ( "waited %0d, then did stuff" , wa
Read more

'git revert' Is Not Equivalent To 'svn revert'

I just learned that if you have some changes in your working tree that you want to get rid of, you don't type 'git revert' like you might guess. No, that's what cvs, subversion, mercurial, and bazaar (to name a few) use revert to mean, but not git. With git, revert is used to undo actual commits. Thankfully, you can undo your revert with another 'git revert', I just learned. So let me repeat to be clear, if you have changes to your working files that you want to abandon, DO NOT do this: git revert HEAD That will undo your last commit. Do this instead: git reset --hard HEAD I'm glad I have that straightened out now. I'm wondering if /etc was really a good place for me to start out playing with git. UPDATE: Nearly two years later and I'm still getting comments on this. I'm glad I've been able to help people out this way. The discussion in the comments is good, and one thing I'd like to point out is that I now always use
Read more

Git Rebase Explained

Image
Introduction Rebase is a helpful git command that can be used to turn a branchy two-headed version history into an easy to follow linear one. A linear history is much easier for a human eye to follow and a human brain to understand. Rebase is a very safe command to use, despite some fear that people have about it. This post should explain how rebase works and clear up any misunderstandings about it. Rebase Basics The short summary of rebase is that it cuts commits out of the git history and reconnects them somewhere else. Let's say the common scenario comes up: you commit a change to the main branch of a repository, you then run  git fetch , and in come a couple changes that other people made on the main branch. If your commit is version 46f and the others that just came in on the fetch are versions ef9 and 4a2, your version history might look like this: The main branch now has two heads, 46f and 4a2. You can run  git rebase  to disconnect your commit from version d88 and connect i
Read more