On Sun, 17 Aug 2008 12:50:34 +0200
Vladimir Nadvornik <[EMAIL PROTECTED]> wrote:
> Hi,
>
> The keyword editor is still not optimal for adding keywords to multiple
> files,
> because the "Add keywords to selected files" feature is quite cumbersome.
>
> I am thinking about a different approach: user will have a possibility to
> connect favorite keywords with with file marks. Then there will be functions
> to set the mark according to presence of the given keyword and vice versa.
> This will provide an overview of selected keywords accross whole filelist. I
> am not yet sure if these function should be automatic or manually called.
>
> The mark-keyword connection will be just temporary and there should be
> an easy possibility to swith to another keyword or disable the connection
> completely and use the given mark for different purpose.
>
> The status of mark-keyword connection should be visible in Keywords bar.
>
> What do you think about this idea?
>
> Vladimir
Can you explain it a bit more ?
BTW, i think we should re-think the whole keywords thing.
Some time ago we discussed about trees of keywords, and i think we can
make the image <-> keyword association even simpler, and we can simplify
the selection of images by keyword.
Maybe we can merge collections, keywords and marks (and even (future) ratings):
- each image can be associated to one or more collections, keywords, marks or
ratings
- the user may search and select images matching a collection name, a keyword,
a mark or a rating
- marks are temporary, so no need to load/save them (but this can be a nice
option)
- keywords are stored (ideally) in image's XMP, but for fast search we still
need to use some cache
- collections are group of images, currently moving original file is not
handled by collection (collection's files are not
updated, and if move is external to geeqie, i see no simple way to keep them
in sync). If image metadata contained
collections names (as it can contain keywords) we can at least re-associated
the image to its collections when
read again.
Currently, collections cannot be organized as trees (think about three
collections named Animals, Animals -> Horses, Animals -> Dogs)
- currently, selection is limited to current directory (but for collections)
So imagine each image internally associated to following metadata (as an
example):
Keywords -> Animals -> Dogs
-> Youkie
-> People -> Me
Rating -> 7/10
Collections -> My pets -> My dogs
-> To print
-> Year 2008 -> August
Marks -> 1
-> 3
One may search and select images:
- with more than 5/10 rating and with Keyword Animals
- having mark 3 set
- from collection My Pets (meaning all images from sub collections too)
- from collection My Pets -> My dogs with keyword Youkie having mark 1 set
- ...
Obviously, we need to maintain some cache to speed up searches (per keyword,
per rating, per collection, ....)
Interface to make associations can be a simple editable tree view.
Search and select can apply to any criteria (marks, keywords, collections,
ratings with and/or/not): interface can be advanced
or simple (for keywords and collections tab completed input fields for example).
Just some thoughts...
--
Laurent MONIN aka Zas
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geeqie-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geeqie-devel
