Re: [darktable-dev] Plugin-SDK

2018-11-06 Thread Jan Ingwer Baer
Of course lost authors and code-rot can be a problem. But i think if 
anyone creates a IOP-modul with general interest it will find the way to 
the DT-codebase and will maintained from the DT-crew.


My idea is to create github-project for the the SDK. And anyone who has 
interest in developing a custom modul can fork it and publish all his 
work on github.


A SDK would be a big help for experiments with IOP-modules. Yes there is 
the useless-IOP as an example, but it is only a minimal example. The 
documentation of the internals of IOPs and pixel-pipeline is very poor.


And yes, i miss some things:

A 3D-CLUT-Modul like RT for finishing/effects. I should exist near the 
end of the pixel-pipeline where the pipeline works in RGB-colorspace. 
There was a try for this, but in my opinion it existed at a wrong place 
in the pixel-pipeline. And the DT-crew denied the integration in favor 
to the new color-look-up-table for color-correction.


A modul with RGB-Curves.

And the RT-Noise-removal

Jan
On 06-Nov-18 09:11, johannes hanika wrote:

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




___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org



Re: [darktable-dev] Plugin-SDK

2018-11-06 Thread sturmflut
Hi,

On 06.11.18 09:11, johannes hanika wrote:

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

this is literally my number one reason for using darktable. If I wanted
to live in a world where I can only open old pictures if I manage a host
of maybe outdated external plugins of dubious quality, I would use
Lightroom.

Just remember what happened to the Nik Plugins. First they were
maintained by a company, then Google bought them, distributed them for
free and ceased development. It's just sheer luck that DxO bought them
from Google and maintains them again. Also you can't be sure that you
will be able to run an older Lightroom version in a VM should the need
arise.

kind regards,
Simon
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org



Re: [darktable-dev] Plugin-SDK

2018-11-06 Thread johannes hanika
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  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



Re: [darktable-dev] Plugin-SDK

2018-11-05 Thread Per Inge Oestmoen

Heiko Bauke wrote:


But note that dt has already plenty of powerful modules. Imho

> dt would probably benefit more from enhanced performance and

user experience than from new modules. High-quality
documentation demonstrating whole workflows and how
 modules interact is also rare.


In my opinion, the key to accomplishing an increase in the number of 
Darktable users is precisely documentation. Dumbing down the program 
would be the worst possible choice. Many want a powerful program and 
many who are today novices will soon progress and learn more.


More and improved documentation is needed. That is the obvious solution.

--
Noise Reduction is just another word for Image Destruction.

Per Inge Oestmoen, Norway
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org



Re: [darktable-dev] Plugin-SDK

2018-11-05 Thread Heiko Bauke
Hi Jan,

Am Montag, 5. November 2018 schrieb Jan Ingwer Baer:
> 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

if I remember correctly, there is a useless.c module which serves currently as 
a blueprint for new modules. 

But note that dt has already plenty of powerful modules. Imho dt would probably 
benefit more from enhanced performance and user experience than from new 
modules. High-quality documentation demonstrating whole workflows and how 
modules interact is also rare.

Heiko 

-- 
-- Number Crunch Blog @ https://www.numbercrunch.de
--  Cluster Computing @ https://www.clustercomputing.de
--  Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.or

[darktable-dev] Plugin-SDK

2018-11-05 Thread Jan Ingwer Baer
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