"b) Improve metadata editor (bigger space for description field with multiple lines)."
I agree with this idea completely. Lightroom has the same problem. I add a lot of cutline information to my images and one short line is not enough. Riley On 15-04-19 01:16 PM, Halgeir Kjønås Rennehvammen wrote: > Agree. Raw+Jpg groups are good enough. > > There are other ways to make the lighttable better workflow better to > identify images faster: > > a) Better hierarchical tag module. > > b) Improve metadata editor (bigger space for description field with > multiple lines). > > c) Show more custom info values (can be setup in settings) on top of > every small image in lighttable (not only in zoom mode): > Shutter, Aperture, ISO, Exposure comp value (-1, 0, +2) when image > overlay is enabled. > > d) The focus mask function is great. But it will be even greater if it > can be optionally viewed on every image also. > Then it will be very easy to identify images not in focus. > > )-|algeir > > > Den 19. april 2015 16:41, skrev Torsten Bronger: >> Hallöchen! >> >> Stefan Klinger writes: >> >>> [...] >>> >>>>> Maybe one can allow tags to carry (primitive) information (maybe >>>>> it's possible already, but I did not see this), or, allow the >>>>> user to add image properties just as tags can be added. Via >>>>> this, grouping could be implemented as a special case of >>>>> tagging: >>>>> >>>>> * On Importing, tag `grouping|shot` should be set to the same value >>>>> for all images recognised as coming from the same shot (maybe, >>>>> just as now, the image_id of the raw). That's what the default >>>>> grouping is doing right now for raw and jpeg. >>>>> >>>>> * It would also be possible to have different groups in parallel. >>>>> The tag `grouping|burst` might be set to a common value for all >>>>> images shot within a very short timespan. >>>>> >>>>> Then the “collapse groups” switch would turn into “collapse >>>>> by tag”. Collapsing by the tag `grouping|shot` would do >>>>> what happens now >>>>> >>>>> Is that a feasible perspective? >>>> It is rather complex and convoluted. >>> What is convoluted? Is it making tags carry values? >> Yes, it introduces an intermediate step, it is more difficult to >> explain, it exposes internal database IDs to the user, and it >> optimizes rare cases. Besides, how do you handle ID clashs? >> >> The audience of DT is rather technophile I suspect, but still I >> personally like as it is now, keeping it simple and stupid: If DT >> detects something that should become a group -- only RAW+JPEG so far >> AFAICS -- it makes them a group. The user can group the remaining >> cases manually. >> >> Tschö, >> Torsten. >> > > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > _______________________________________________ > Darktable-users mailing list > Darktable-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/darktable-users ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
