Hello R C-R,
I understand that point to not reveal internal functioning of the apps/file formats and thats definetely true.
On the other hand I think it is possible to provide an "integration API" and make it able to be used for non-commercial pupose only by licency and design.
This will not reveal too much on one hand but give people the possibillity for better integration on the other hand.
Lets be true; the current possibillity to integrate AP into Lightroom and Capture One are far from being nice and usable.
Being a professional software developer I was looking for a possibillity to create a better integration by building my own Lightroom plugin. Thats what I wanted to use the API for.
Revealing some startup parameters / startup arguments would not reveal sooo much of the business critical internals/formats.
I also understand that Serif might release a Lightroom compeditor in the future and wants to keep the integration part for their Image-Catalouge but on the other I can not imagine that people who have >50.000 Images on Lightroom will switch. I was sadly using Aperture before :(
Even this could be solved by using the action-file pattern. (see below).
What do you think?
Thanks to all for the open discussion.
---------------------------------
The action file is basically a simple XML file that specifies:
- Action to be executed: HDR, EDIT, FILE_CONVERT, STITCH_PANORAMA, OPEN_AS_LAYERS, ...
- Source-File(s)
- export file(s) (optional)
Format could be like this:
<affinity-action>
<action>HDR</action>
<parameters>
</param key="output-format" value="TIFF">
</parameters>
<source-file-set>
<source-file>xxx/yyy.raw</source-file>
<source-file>xxx/zzz.raw</source-file>
</source-file-set>
<target-file-set>
<target-file>xxx/xxx_hdr.tiff</target-file>
</target-file-set>
</affinity-action>