On 07/04/14 06:15, Kevin wrote:

Hi!

>> 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.
>>
> 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>]

This sounds good, indeed :)


> 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:

Due to this it might be helpful to allow some --db parameter, which 
allows to specify a database to use. Worst case would then be to just 
make a copy of dt's database before running the cli. Alternatively, 
given one has those guys in files exported from the GUI one could 
probably read them from the resulting file(s)?

BTW: isn't this yet another good reason to have styles and profiles to 
live outside the db in the first place?

[...]
> The gui presents other parameters that are dependant on the output file type,
> e.g., JPG quality. These probably should also be included here

%'<,'>/probably should/must/

;)

> as it appears
> that the cli export uses the value that was last used in a gui export.

IMHO this is a clear vote for having them available. I think those are 
also the ones Torsten referred to. At least those were the ones that 
came to my mind from Torstens comment.

> This is "not recommended" (tm).

Agree.

> Comments? Objections? Suggestions?

Hope to see it in master soon :)

-- 

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

Reply via email to