On 2013-03-11 18:39, Torsten Bronger wrote: > Hallöchen! Groetjes :).
>> 1) display both the string reported by exiv2 and the string from >> lensfun it loosely matches > > I can understand the desire for input in case something doesn't work > out of the box with the Lens module. But what you suggest would be > displaying debugging data in my opinion. Hmm, I don't know. Debugging data is about picking up potential errors in the code. When you're talking about picking up quality of error-prone search results, users are accustomed to viewing and assessing the quality of results. For example, with google search autocomplete, you get a list of options, not just its best guess - and you get to see those guesses and your own input. It doesn't rudely overwrite your input with its best guess. Secondly, once you submit a Google query, it may come back with a "did you mean.... ?" response, and may even return some search results for that query, clearly labelled as such. The point is, at all times, the user is aware of what automagic wizardry has gone on, and has the option to accept or decline. (Yeah - they also get to be part of Google's global mass surveillance database... let's not go there.) > Tschö, Doeg! (Jeetjes - ik zou heel graag ooit willen teruggaan...) Russell ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
