not that i'm using tagging a lot, but i think what you say makes perfect
sense. so i'd vote to delete the keyword module and not allow that
reorganisation.
j.
On Tue, Oct 29, 2013 at 12:36 PM, AlicVB <alic...@gmail.com> wrote:
> Hi all,
> a quick update :
> - tag collect is now integrated in the collect module, with tree display
> of hierarchical tags
> - keywords module has been move to the right panel and its "collect"
> functionality has been dropped
>
> Now it would be great to delete keyword module completely, but it still
> has an "unique" functionality : it permit tag reorganization.
> But here, I'm not sure we have to keep it at all because it can be
> really confusing, imho : imagine you have some images tagged
> "wildlife|macros|bee" and then you move "bee" to "animals|bee" what
> happens to the image tags ? In the actual behavior,
> "wildlife|macros|bee" is replaced by "animals|bee" but not just in
> selected image : in the whole collection !
>
> For me, there is 2 different approaches about the "hierarchical tags"
> concept :
> 1- either the hierarchy is just a convenient way to select/apply tags to
> images. In that case, it should be the responsibility of dt to handle
> them, but it shouldn't be saved in images. Just the last keyword should
> be saved.
> 2- either the hierarchy is a way to tag image in more precisely. In that
> case changing hierarchy is like changing any keywords : it should
> eventually be applied to selected image, but not to all images !
>
> Guess what : I prefer the second approach. And if we go that way, we
> don't need the keyword module anymore, we can just use the tagging
> module to manually edit tags.
>
> What do you think ?
> Aldric
>
> PS : for reference, code is in the tag_explorer branch from the main repo
>
>
> ------------------------------------------------------------------------------
> Android is increasing in popularity, but the open development platform that
> developers love is also attractive to malware creators. Download this white
> paper to learn more about secure code signing practices that can help keep
> Android apps secure.
> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
> _______________________________________________
> darktable-devel mailing list
> darktable-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/darktable-devel
>
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel
