[Tuxpaint-devel] Magic tools ported; comments requested

[Bill K. <nb...@so...>]

Due to an admittedly sad circumstance yesterday, there were some major
train delays in my multi-hour commute home, causing it to take about 6-7hrs.
The good news is, this gave me a long, solid chunk of time alone with
my laptop.

Tux Paint in CVS now has had all Magic tools[*] converted into external
plugins.  Some plugin objects contain multiple tools, but they are simply
exposed within Tux Paint as separate buttons, like they were before.

(e.g., Block, Chalk and Drip were fairly similar, so they're all in the
same '.so' file.)

I've began documenting the API -- it's a bit rough, so I'd love some
comments on it.  (And Albert, if you can think of a way to, alternatively,
build Tux Paint so that these separate Magic plugin C files are compiled
as normal objects and connected to Tux Paint at link time, that'd make
SE Linux users happy, I imagine :^) )

Docs are visible here, in CVS:

  http://tuxpaint.cvs.sourceforge.net/*checkout*/tuxpaint/tuxpaint/magic/docs/html/README.html

And an example plugin is here:

  http://tuxpaint.cvs.sourceforge.net/*checkout*/tuxpaint/tuxpaint/magic/docs/tp_magic_example.c

And the API header file is here:

  http://tuxpaint.cvs.sourceforge.net/*checkout*/tuxpaint/tuxpaint/src/tp_magic_api.h


I've already asked John P. and Martin F. to look into how this all
affects Win32 and OSX builds (I'm guessing low-impact).  As they provide
details on how the plugins can be built on those platforms, I'll update
the API's REAMDE docs.

Thanks in advance!

[*] Except 'Sparkles', which, except for its sound effect, was easily
    replaced with an animated/randomized paint brush.

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/