[KPhotoAlbum] Breaking changes in file layout

[Robert Krawitz]

On Mon, 06 Apr 2020 01:06:02 +0200, Johannes Zarl-Zierl wrote:
> Am Montag, 6. April 2020, 00:22:30 CEST schrieb Robert Krawitz:
>> On Sun, 05 Apr 2020 23:50:29 +0200, Johannes Zarl-Zierl wrote:
>> > Am Sonntag, 5. April 2020, 22:49:32 CEST schrieb Robert Krawitz:
>> >> On Sun, 05 Apr 2020 21:48:30 +0200, Johannes Zarl-Zierl wrote:
>> >> I hate hashes like that; it's impossible to reverse them to figure out
>> >> what they refer to.  I'd prefer some kind of fairly transparent
>> >> encoding of the path; maybe it could even be the path (which yes,
>> >> would mean the files might be nested somewhat deeply.  Or replace the
>> >> / with a | (which isn't often used in paths).  It doesn't have to be
>> >> perfect, just good enough to be distinguished.
>> > 
>> > I get your point, but I'm not a big fan of constructs like "/home/
>> > johannes/.cache/kphotoalbum/home/johannes/Pictures" either.
>> 
>> Yeah, that's ugly; maybe if it were
>> 
>> /home/johannes/.cache/kphotoalbum/home|johannes|Pictures
>> 
>> or some such it would be easier.
>
> I guess I can live with that. From a scripting point of view it
> still is a one-way trip, though.

Yes, but at least it's human-readable.

>> > * Privacy Settings (i.e. which images should be hidden)
>> 
>> I think that should be part of the index file.  That is a property of
>> the collection of images, and it's easy to see how it would be
>> represented:
>> 
>> <value value="H" id="8" hidden="true"/>
>> 
>> That would also allow multiple hidden tags, if someone wanted to do
>> that.
>
> Currently, this can be an arbitrary ImageSearchInfo. I'm not opposed
> to simplifying this towards your approach, though.

How is that be done?  Searching on the image name, or complex conditions?

>> > These settings seem noteworthy to me, but I currently think they are
>> > better of in kphotoalbumrc:
>> > 
>> > * untaggedImagesTagVisible
>> > -> this is a user preference
>> 
>> What exactly does this do?
>
> It determines whether the untagged tag is shown as a normal tag or
> is hidden from the viewer.

Yes, that sounds like a user preference.

-- 
Robert Krawitz                                     <rlk at alum.mit.edu>

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --    http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton