Hi Jon,

Thanks a lot for your answer. It helps a lot :-)

> For some background on the current state of the MyPaint brush
> library, please see the first part of this recent email:

Very interesting thread ! Seems the Andrew  and I, have some common
concern and faced the same issue.

> There is no LGPL code in current MyPaint. Please let us know where you
saw that
> so we can fix it. libmypaint, that is the things under brushlib/, is
licenced ISC and
> the rest of MyPaint GPLv2+.

Regarding the term LGPL, that's my mistake. (I should have read ISC and
replaced it in my head by a more permissive license than GPL : the
Lesser GPL).
My point was rather about what is GPL and what is ISC. For an example,
the /brushes directory contains all brushes and if they are GPL, using
libmypaint without the brushes seems quite difficult. Recreate them
would automatically lead to find again some neighbor settings from the
GPL ones and this could be border-line...
But the pointer you gave me helped a lot !
 
> scons is about as horrible as all the other build systems out there.
But what do you
> want to achieve with replacing it? [...]

I was thinking of having 2 separated scons project (one for libmypaint
and another for mypaint), so it is easier for anyone who want to use
it's own build system to extract the information from the simpliest
libmypaint scons script and rewrite its own script. But, don't worry,
that was just the expression of some frustration :-).
I guess that the way to go for me -as you pointed it out- is use scons
for each new release (as it call python and re-generate all the
necessary files) and just take the necessary .h/.cpp files and put them
in my repository.
(actually, my build system is quite complicated because we build on
Linux/Windows/Mac and each one start some automatic tests on several
computers and adding scons in the build process would mean to add it on
all platforms and computers and would increase the complexity of the
general build (there is already CMake/Perl script/Qmake...). So I will
use scons only on my dev computer and put the resulting C++ files to the
general repository)

Regarding json-c, my first test have shown that it doesn't link
correctly when build on win32/win64 with msvc 2005/2008/2010. The
following define is required in json_util.c (microsoft doesn't support
snprintf) :
#ifdef _MSC_VER
  #define snprintf  _snprintf
#endif
Seems that I am the first guy who is using it on windows and not using
Cygwin ;-)

> Am I right that you want to use libmypaint to paint onto the
surface/canvas you
>already have in your existing application?

Yes. I started to rewrite from scratch a full graphic pipeline few month
ago. The one I was using before was too limited (QGraphicsScene/View was
missing the color matching feature and was not handling the repeat)
I considered seriously GEGL but that was too much a work in progress
code for a production software. Gimp folks just switched to GEGL and the
lib is not mature enough (and I'm not speaking of the documentation ;-)
But you are very well aware of that considering the various and very
interesting blog entries I read in your personal blog !
So using GEGL is certainly something I'll use in the future but for now,
I'm using a simple QImage 8 / 32 bpp per layer.

Yesterday I wrote quickly a test application which is parsing the brush
library, display them to the user and wait for the user to draw on the
surface... The code to draw on the surface is not done yet but that's my
today job. I'll see if I can have something nice so I could give it to
you (ISC licence too). That could be a good starting point for a basic
example of how to use libmypaint.
(as long as my call to libmypaint are not completely wrong ;-) I will
let you know if I need more help on specific stuff.
Doing that in Qt 4 is interesting too, as it is a strong signal for
potential users that this lib is for anyone !

Thanks again for your reply, Jon.

Best regards

Sebastien

_______________________________________________
Mypaint-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/mypaint-discuss

Reply via email to