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 c
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
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 anyt
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 opinio
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
> - som
