Am 13.02.2015 14:26, schrieb Dennis Gnad: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 13.02.2015 13:05, Tobias Ellinghaus wrote: >> After thinking about that I came to the conclusion that this would >> be best done with Lua. Everyone has their own (albeit similar) >> wishes there so a set of a few Lua scripts (or one with a few >> config switches) would be the best way to go. > > Outsourcing some of the C functionality to lua might be fine, but > 'normal users' should not need to get into writing lua scripts for > rather simple options, I hope? > >> Currently darktable allows to register a callback that is run >> after an import, so it would already be possible to remove images >> from the db that are not wanted. However, that would still waste a >> lot of time since these images get imported first, might get a >> sidecar file and maybe even a thumbnail created. To make this more >> useful we are currently discussing the idea of a list filter for >> import and also export that could remove (or add) images to the >> list of to-be imported/exported images. This won't land in the 1.6 >> series though, > > I just shortly rebased what I had. I can still change the gui, but I > guess it also won't come to 1.6, as it is a new feature? A more > sophisticated/generic list filter (whatever you mean exactly) for > after 1.6 sounds better anyway.
I guess a list based import would require some more user interaction such as selecting single images from the list. If there are filters it may work, if filter presets can be stored. Anyway, what I think about is way less complex and exactly what you describe below. Maybe an option about dt-generated files could be added, but IMO it is not necessary, and not importing these should be the default (assuming proper documentation, e.g. hover and/or user manual). Maybe comparison of the exif dates would be a good addition. > Here it is, rebased on master: > https://github.com/bluesceada/darktable/tree/jpeg-solitary-import-rebase > > Here two screenshots to see how it looks: > http://xorn.org/darktable/import_jpg_new1.png > http://xorn.org/darktable/import_jpg_new2.png > >> so if anyone feels bored, a script that removes unwanted files >> from the imported film would be worthwhile for the time being. To >> get you started, the important callback is post-import-film >> (http://darktable.org/redmine/projects/darktable/wiki/LuaAPI#post-import-film). > > This >> > would take me longer to do just now than the rebase took me. But > maybe Chris is interested... Hm, since you already implemented the required functionality in an IMHO much saner way than modifying the database after the import sounds for me, I hope that the main developers can be convinced that it is a good idea, what It actually really is ;-) Almost every DSLR, MILC, DSLM or whatsoever photographer will stumble upon the raw+jpeg option and so this option will be familiar for most of them. What would be interesting is the confirmation that all manufacturers use the same naming scheme (i.e. using the same basename as the raw but .jp(e)g extension), otherwise the different naming schemes should be recognized by the option. Best regards Chris ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
