hey, i think i like the direction where this is going.
some random thoughts on it: single click feels a little faster, typing + enter still works, and speed seems to be okay on my 10k image db. now when you click something it somehow feels unexpected that you go up to the top in the list again and the filter changes. maybe we need to do this all the way then and keep the scroll and everything and maintain the selection in the list as well as the filter string in the entry box? not sure how that would work with the collection serialization required by the recent collect module for example. i guess in first iteration it could just ignore the filter string. also unsure how to handle switching back and forth between multiple collection rules in that case. and how to handle wildcards in the query if all you can do is select one from the list. so maybe a better idea than that would be actually introducing a second entry box just for the filter and keep the current one as the query box? i guess that has the potential to waste some screen space.. -jo On Fri, Feb 1, 2013 at 11:19 AM, Gaspard Jankowiak <[email protected]> wrote: > Hey everyone, > > I'm not very happy with the collect module from the usability point of > view, and it seems a few people on #darktable feel somewhat the same. > > It's currently quite slow and cumbersome to work with it: when selecting > an entry the whole list goes away, and comes back only at the cost of > clearing the textbox or resetting the module. And as far as I > understand, for this very reason, the selection requires a double click > to avoid the list going away by mistake (more disappointment). > > A more friendly behaviour would be to have the entire list shown, with > filtered out entries standing out, preferably floated to the top of the > list. I have a more or less working patchset in my collect_ui branch: > http://github.com/gapato/darktable/tree/collect_ui > The question is, good or bad idea, should I finish it? It seems to work > when combining filters (no extensive testing done). There also might be > some performance problems with big databases (no testing done, I'm not a > prolific photog). Nothing serious if given time and care, I think. > > I've also a small fix for the collect module, i.e. make the 'date' > filter actually work by date, and create a dedicated 'time' filter for > those who need that. The associated bug report and (rather small) PR > might need some love. > > What do you think? Thank you for the feedback! > > Also, thank you for the clean code and the good mood on #darktable, it > makes it easy to try and contribute :) > > Cheers, > Gaspard > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_jan > _______________________________________________ > darktable-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/darktable-devel ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
