Future of Shiva, lack of future of OpenGTL
Cyrille Berger Skott
cberger at cberger.net
Sat Nov 30 13:19:17 UTC 2013
On Saturday 30 November 2013 12:46:38 Lukast dev wrote:
> > The main reason for abandoning OpenGTL is that it relies on llvm and
that
> > still requires quiet a high maintenance on the library as new version of
> > llvm appear, and there are many incompatibilities (like with mesa open
> > source driver). Also, now the CTL color spaces are gone, so Shiva was
the
> > remaining useful bit.
>
> Does this mean also end for OpenRijn?
Yes, well it never really was finished. And openrijn does not make any
sense without being "interpreted", so without llvm, it is sort of pointless.
And I think using javascript (using something like V8) would fit the intended
purpose of openrijn quiet well, and be performing fast enough.
> > === On the third day, Shiva came back
>
> Did you consider to use GMIC? http://gmic.sourceforge.net/
> I integrated it into Krita recently.
Yes, I did.
> It provides:
> o CPU backend
Actually, as far as I can see it is an interpreter. So while it technically run
on the CPU, it is quiet different from being compiled to the CPU, at least, in
term of speed.
And the existence of a roadmap to running on GPU as
OpenCL/RenderScript is a requirement. And from looking at the code, it
might be difficult to separate the parser from the interpreter, requiring to
start from scratch, and I don't personally want to do that because of the
next point:
> o language for writing filters (limited high-level language)
I will admit that it is very subjective, but to me, as a potential developer,
the actual syntax of a programming language is really important, and that
is where gmic fails: <troll>Closer to brainfuck than anything I would want
to code with myself :)</troll>. So as a "user" of gmic, it probably does not
matter.
> o syntax for describing filters
Actually lacking an important bit, which is to know which part of the image
is affected for each change. Which makes it impossible to use in a
processing graph, unless you reprocess the whole image. Which is I guess
why you didn't integrate gmic as a KisFilter but as an extension plugin ?
> o there are already many filters available
That is indeed the biggest and greatest point of gmic. And that is also
maybe why, Shiva for Krita might not be important until Krita can benefit
from OpenCL (and Shiva has a converter for it).
--
Cyrille Berger Skott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kimageshop/attachments/20131130/58fc9843/attachment.html>
More information about the kimageshop
mailing list