Re: Breaking changes in file layout

Am 06. Apr. 2020 schrieb Johannes Zarl-Zierl:

> 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.  

Just an idea: what about an encoding like many news-sites or
stackoverflow.com use, a mix of hash + title. The hash-part makes the
entry unique, the title part makes it readable for humans.

For the example above, the result would be something like

/home/johannes/.cache/kphotoalbum/<hashCode>-home_johannes_Pictures

Or maybe just the last part of the complete path (the filename), to
reduce length? 

/home/johannes/.cache/kphotoalbum/<hashCode>-Pictures


Just my 2 cents,
- martin

_______________________________________________
KPhotoAlbum mailing list
[email protected]
https://mail.kdab.com/mailman/listinfo/kphotoalbum

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAl6LAlwACgkQYJf22JPx7tkrYACeLW0c/NHqXet0s5T2hnkFhCDS
N5oAoKVjYWKkxOA5419IVfS4AYk17OTN
=8EIQ
-----END PGP SIGNATURE-----