Subject: Should import gqview preferences when migrating from gqview -> geeqie
Date: Tue, 03 Nov 2009 11:45:50 -0200
Package: geeqie
Version: 1:1.0~beta2-5
Severity: wishlist
Hi!
Now that geeqie is replacing gqview, it should also import the user preferences
from gqview on the first run (like how thumbnails are generated and displayed,
how the image is zoomed or not, etc).
Thank you!
Best regards,
Nelson
Acknowledgement sent
to The Wanderer <[email protected]>:
Extra info received and forwarded to list. Copy sent to Michal Čihař <[email protected]>.
(Mon, 14 Dec 2009 03:39:03 GMT) (full text, mbox, link).
Subject: Re: Bug #554163: Should import gqview preferences when migrating
from gqview -> geeqie
Date: Sun, 13 Dec 2009 22:38:12 -0500
Consider this seconded.
I would also prefer if it could pick up the same window-manager settings
as used by gqview (size, ___location, desktop, et cetera), but that's both
significantly easier to re-set by hand and probably much harder to have
happen automatically.
It was mentioned in passing in bug 553920 that there is a menu entry in
geeqie for migrating GQView "metadata". From the context of that
mention, it seems that this menu entry should perform exactly the
migration being requested by this bug; it just doesn't do it by default
on first run. I can see its being arguable that in fact it should not.
However, I have not yet been able to confirm whether or not this menu
entry actually does that migration. I would not expect it from the name
("metadata" to me refers to things like size tags and "what program
created this file" and "where I was when I took this picture"
information, and is per-file not per-program; I would expect the
~/.gqview/ information to be called "configuration"), and as far as I
can tell, the geeqie Help manual does not even mention this menu item,
much less explain what it does.
Acknowledgement sent
to Michal Čihař <[email protected]>:
Extra info received and forwarded to list.
(Mon, 14 Dec 2009 09:12:02 GMT) (full text, mbox, link).
Hi
Dne Sun, 13 Dec 2009 22:38:12 -0500
The Wanderer <[email protected]> napsal(a):
> However, I have not yet been able to confirm whether or not this menu
> entry actually does that migration. I would not expect it from the name
> ("metadata" to me refers to things like size tags and "what program
> created this file" and "where I was when I took this picture"
> information, and is per-file not per-program; I would expect the
> ~/.gqview/ information to be called "configuration"), and as far as I
> can tell, the geeqie Help manual does not even mention this menu item,
> much less explain what it does.
Yes it's really just for metadata not for configuration.
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
Acknowledgement sent
to The Wanderer <[email protected]>:
Extra info received and forwarded to list. Copy sent to Michal Čihař <[email protected]>.
(Mon, 14 Dec 2009 12:54:03 GMT) (full text, mbox, link).
Subject: Re: Bug#554163: Bug #554163: Should import gqview preferences when
migrating from gqview -> geeqie
Date: Mon, 14 Dec 2009 07:51:32 -0500
On 12/14/2009 04:09 AM, Michal Čihař wrote:
> Hi
>
> Dne Sun, 13 Dec 2009 22:38:12 -0500 The Wanderer
> <[email protected]> napsal(a):
>
>> However, I have not yet been able to confirm whether or not this
>> menu entry actually does that migration. I would not expect it from
>> the name ("metadata" to me refers to things like size tags and
>> "what program created this file" and "where I was when I took this
>> picture" information, and is per-file not per-program; I would
>> expect the ~/.gqview/ information to be called "configuration"),
>> and as far as I can tell, the geeqie Help manual does not even
>> mention this menu item, much less explain what it does.
>
> Yes it's really just for metadata not for configuration.
That doesn't make any sense. AFAIK GQView never tagged files with
anything, and even if it did, a program which can understand such data
should read it automatically from the image file instead of needing to
explicitly "import" it; it might make sense to need to re-write the
metadata in a new format, but that isn't what "import" would mean.
I therefore now have no idea what this menu entry does, and am still
looking for a way to migrate configuration (as would be necessary for
geeqie to be considered a proper single-line-of-descent replacement for
gqview).
(...also, completely off the topic, why does the Debian BTS mail
notification not set the reply-related headers sensibly? It's almost
never going to be appropriate to reply just to the person who wrote the
comment, rather than to the bug, and if you're replying to the bug then
the person who wrote the comment is almost certainly going to be getting
a copy anyway.)
--
The Wanderer
Warning: Simply because I argue an issue does not mean I agree with any
side of it.
Secrecy is the beginning of tyranny.
Acknowledgement sent
to Michal Čihař <[email protected]>:
Extra info received and forwarded to list.
(Fri, 18 Dec 2009 10:06:07 GMT) (full text, mbox, link).
Hi
Dne Mon, 14 Dec 2009 07:51:32 -0500
The Wanderer <[email protected]> napsal(a):
> That doesn't make any sense. AFAIK GQView never tagged files with
> anything, and even if it did, a program which can understand such data
> should read it automatically from the image file instead of needing to
> explicitly "import" it; it might make sense to need to re-write the
> metadata in a new format, but that isn't what "import" would mean.
GQView did have support for keywords and comments and it stored them
separately.
> I therefore now have no idea what this menu entry does, and am still
> looking for a way to migrate configuration (as would be necessary for
> geeqie to be considered a proper single-line-of-descent replacement for
> gqview).
You're right this should be handled.
> (...also, completely off the topic, why does the Debian BTS mail
> notification not set the reply-related headers sensibly? It's almost
> never going to be appropriate to reply just to the person who wrote the
> comment, rather than to the bug, and if you're replying to the bug then
> the person who wrote the comment is almost certainly going to be getting
> a copy anyway.)
I guess the problem is that you don't get the mail from bts but from me
directly because it is how it set's reply headers for me.
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
Acknowledgement sent
to The Wanderer <[email protected]>:
Extra info received and forwarded to list. Copy sent to Michal Čihař <[email protected]>.
(Fri, 18 Dec 2009 13:54:03 GMT) (full text, mbox, link).
Subject: Re: Bug#554163: Bug #554163: Should import gqview preferences when
migrating from gqview -> geeqie
Date: Fri, 18 Dec 2009 08:51:31 -0500
On 12/18/2009 05:01 AM, Michal Čihař wrote:
> Hi
>
> Dne Mon, 14 Dec 2009 07:51:32 -0500 The Wanderer
> <[email protected]> napsal(a):
>
>> That doesn't make any sense. AFAIK GQView never tagged files with
>> anything, and even if it did, a program which can understand such
>> data should read it automatically from the image file instead of
>> needing to explicitly "import" it; it might make sense to need to
>> re-write the metadata in a new format, but that isn't what "import"
>> would mean.
>
> GQView did have support for keywords and comments and it stored them
> separately.
..you mean "separately" as in, in a separate file?
That seems bizarre (for at least the reason that I've never heard of
this practice before, at least not for image files), but at least it
does let the menu entry make sense; thank you.
Acknowledgement sent
to Michal Čihař <[email protected]>:
Extra info received and forwarded to list.
(Fri, 18 Dec 2009 14:09:07 GMT) (full text, mbox, link).
Hi
Dne Fri, 18 Dec 2009 08:51:31 -0500
The Wanderer <[email protected]> napsal(a):
> On 12/18/2009 05:01 AM, Michal Čihař wrote:
>
> > Hi
> >
> > Dne Mon, 14 Dec 2009 07:51:32 -0500 The Wanderer
> > <[email protected]> napsal(a):
> >
> >> That doesn't make any sense. AFAIK GQView never tagged files with
> >> anything, and even if it did, a program which can understand such
> >> data should read it automatically from the image file instead of
> >> needing to explicitly "import" it; it might make sense to need to
> >> re-write the metadata in a new format, but that isn't what "import"
> >> would mean.
> >
> > GQView did have support for keywords and comments and it stored them
> > separately.
>
> ..you mean "separately" as in, in a separate file?
Yes, that's exactly how it was implemented (and I'm not sure if it is
still not default in Geeqie).
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.