heya, with an open SDK there is the problem of backward compatibility. how would you deal with that? don't offer support? what if the plugin author disappears and the code rots? you'd be making old history stacks useless. i like how we are committed to keeping old image edits alive.
is there anything in particular that you're missing? or you just want to mess around with the code and try some things? as heiko pointed out, for this we've got useless.c. cheers, jo On Mon, Nov 5, 2018 at 8:03 PM Jan Ingwer Baer <jib...@web.de> wrote: > > It would be nice to have a thing like a 'Plugin-SDK' to enable more > users to create their own IOP-Modules. To make the development of > IOP-modules much more easy it should contain : > - all the needed headers and libraries > - some documentation: IOP-Interface, description of pixel-pipeline > - some sample IOPs > - cmake-files > > ___________________________________________________________________________ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
