Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stable gimp-darktable calling interface #16193

Merged
merged 1 commit into from
Feb 2, 2024

Commits on Feb 2, 2024

  1. Stable gimp-darktable calling interface

    As we want to support darktable as a gimp plugin in the best possible way we put the
    burden of "how to do so" on the dt dev team instead of having that on the gimp side as
    we likely know better to achieve this.
    
    Summary of currently implemented darktable features
    - always use default resources
    - don't print any logs
    - while being in darkroom ignore any requests to change view
    
    **************************************************************************************
    The GIMP support cli API 
    
    Added --gimp <mode> option to the cli interface. <mode> is always a string, can be
    "version" "file" "thumb"
    
    Whenever we call 'darktable --gimp' the result is a string <res> written to stdout.
    Also the returncode is 0.
    
    In case of errors <res> is "error" and returncode will be 1
    
    As darktable makes use of external libraries <ret> might be preceeded by other text,
    the <res> is always the last written line string (eol before and after)
    
    version            Returns the current API version (for initial commit will be 1)
    file <path>        Starts darktable in darkroom mode using image defined by <path>.
                       When closing the darkroom window the file is exported as an
                       xcf file to a temporary location.
                       The full path of the exported file is returned as <res>
    thumb <path> <dim> Write a thumbnail jpg file to a temporary location.
                       <path> is the image file
                       <dim> (in pixels) is used for the greater of width/height and ratio is kept.
                       The returned <res> has the following format:
                       * The full path of the exported file on the first line
                       * The width and height as space-separated integers on the second line.
                         These dimensions are informational and may not be accurate.
                         For raw files this is sensor size containing valid data.
    jenshannoschwalm committed Feb 2, 2024
    Configuration menu
    Copy the full SHA
    0d3a77e View commit details
    Browse the repository at this point in the history