On 07/04/14 23:10, Tobias Ellinghaus wrote:
Hi!
[...]
>>> would go away, too. That is all just slow and bloat. That tool isn't
>>> meant to be a remote control of darktable (using --core --library
>>> ~/.config/darktable/library.db you could even import images from the
>>> command line without having a running dt around)
>> What is bad about this? This can could in quite handy... IMHO there is
>> no need to strip this entirely.
>
> It is slow.
Probably, the flexibility bought that way is worth it. Thinking e.g. of
a migration of a larger collection I can well imagine that one prefers a
slightly slower cli to do it over night in batch than click trough it by
hand. (E.g. if you have to do other fancy stuff like renaming / sorting
of files etc.) There's also at least one guy on the list processing his
fieldwork. There a workflow could be to dump your card some time and
processing is probably essentially the same for tons of images so its
more automatic an less art.
As Kevin mentioned at 3 in the morning it is usually not that importat
if it takes an hour or an hour and a half.
If it is a real issue I'd at least consider to have something like the
current cli and another tool like dt-convert that doesn't need the db.
--
Kind regards, / War is Peace.
| Freedom is Slavery.
Alexander Wagner | Ignorance is Strength.
|
| Theory : G. Orwell, "1984"
/ In practice: USA, since 2001
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel
