On Aug 26, 2014 9:54 AM, "Michael Catanzaro" <mcatanzaro(a)gnome.org>
wrote:
On Tue, 2014-08-26 at 01:10 -0400, Liam wrote:
> What's the use case? What functionality are the target users expecting
> from an image viewer? My experience is I only ever use such apps for
> rather quick assessments of images. For more than that I open a
> dedicated editor.
> Does a image viewer need to do more than just show an image (possibly
> along with metadata)?
With eog you can look at multiple images in multiple windows. I guess
sushi could do this too but you'd need to open a new nautilus window
each time. Then don't ever hit space.
This is a good point, as a don't tend to view multiple images at once very
often. Still, seems odd to keep an app installed for that specific use case.
We could also drop totem and evince if we're planning to use
sushi as
the only means for previewing files. Doesn't seem like a good idea to
me.
I actually I do tend to use sushi more than evince/totem for quick work,
but I wasn't suggesting the above, yet. There's a few issues with sushi, as
you've mentioned, that would need to be worked out first (discoverability,
performance, metadata display, etc).
It's also not discoverable at all. You wouldn't know it's
there unless
someone told you. And the theme is currently a broken mess. :(
This was my big concern (not the theme but discoverability). That's why I
mentioned the way dolphin (which, IMHO, is the best file manager on Linux,
and I don't even use KDE) handles things. Having a larger preview in the
right panel, along with metadata, and a way of full screening the file is a
very nice way to quickly assess things.
Once again, I think this is a longer term project, but I wanted to mention
it since I find sushi incredibly handy, and no one had mentioned it yet.
In the meantime, I'd drop shotwell and go with either eog or gthumb, but
with the proviso that this whole issue should be reexamined at some point.
Best/Liam