[KimDaBa] Re: Next release one week, then what?!

Benny Rochwerger benny.rochwerger at gmail.com
Mon May 9 00:11:56 CEST 2005


On Sun, 2005-05-08 at 14:48 +0200, Jesper K. Pedersen wrote:
> | 3. Flexible support for batching operations, for example send the
> | selected set to a shell script (dragging the selected images to a shell
> | kind of enables this, but is not as intuitive as to right click and
> | select a "Send to command"  menuitem. The result of the script anywhere
> | in the filesystem (i.e., do not necesarily get added to the image
> | database).
> Do you have KIPI plugins installed with kimdaba, that does many of those 
> things.
> 

Yes but it is limited to KIPI plugins, hence limited to whatever KIPI
developers put in the package.  Passing a set of images to a shell
script enables people to very easily do all kinds of interesting batch
processing.

> | 4. Support for a special "State" category that enables images to be
> | assigned to a single member. This category can then be used as the
> | driver for the workflow by moving images from one member (state) to
> | another.  If this is not possible, then at least I think the capability
> | of "uncategorizing" a set of images together is a must (I used category
> | members to mark state, and although I can add many images to a category
> | member with a single command, but I have to remove them from the
> | temporary (state) category one by one)
> I simply have the keyword OK set on images that I have categorized. To find 
> those not categorized, I search for !OK.
> 

How do I search for !OK ? In the search window I can't type a keyword
not in the list and in the quick search, it does nothing.
Having a keyword that separates categorized images from uncategorized is
definitely a great feature. But this only enables two states, ideally I
would like to have a more flexible image state.



More information about the KimDaBa mailing list