On Thu, 3 Apr 2014 14:27:47 Torsten Bronger wrote:
> Hallöchen!
> 
> Thank you!  As a DT_CLI user, I appreciate this.  How difficult is
> it to add all other options of DT's "export" module to the CLI?
> Since the "export" module parameters cannot be in the XMP file, this
> is highly practical I think.
> 
> Tschö,
> Torsten.

I've done some more work in this area - see attached patch.

The major changes are:

1) A complete revamp of the way parameters are specified. This is best shown by 
the output of the "--help":

** start**
usage: darktable-cli -i|--input <input file>
                     -o|--output <output file>
                    [-b|--bpp <bpp>]
                    [-c|--core <darktable options>]
                    [-H|--height <max height>]
                    [-h|--help]
                    [-I|--intent <intent name>]
                    [-q|--hq <0|1|true|false>]
                    [-O|--overwrite]
                    [-p|--profile <profile name>]
                    [-s|--style <style name>]
                    [-v|--verbose]
                    [-V|--version]
                    [-W|--width <max width>]
                    [-x|--xmp <xmp file>]

note: if used, "--core" must be last
intent names: image settings, perceptual, relative colorimetric, saturation, 
absolute colorimetric
** end **

2) As can be seen from the above, there are three new parameters: --intent, --
profile and --style. The last of these requires the actual dt database to be 
used so that following warning is displayed if that parameter is used:

**** --style specified - dt database will be used.
**** cli will fail if gui active or gui will not
**** start while this instance of cli is running.

I understand that removing the file path positional parameters will break 
existing scripts. But, given that users of the cli are probably more computer-
savvy that most users, this will not present much of a chore - I hope. (The 
reason I removed these positional parameters is that I think such things are 
inherently evil.)

The gui presents other parameters that are dependant on the output file type, 
e.g., JPG quality. These probably should also be included here as it appears 
that the cli export uses the value that was last used in a gui export. This is 
"not recommended" (tm).

Comments? Objections? Suggestions?

Cheers,
Kevin

Attachment: dt.patch.tar.gz
Description: application/compressed-tar

------------------------------------------------------------------------------
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_APR
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel

Reply via email to