Re: [Gimp-developer] Of Palettes and Plug-ins
- From: "Joao S. O. Bueno" <gwidion mpc com br>
- To: Chris Mohler <cr33dog gmail com>
- Cc: Graphical Geniuses <gimp-developer-list gnome org>
- Subject: Re: [Gimp-developer] Of Palettes and Plug-ins
- Date: Fri, 6 Sep 2013 15:20:40 -0300
Hi -
Yes, the paramerter PF_PALETTE is passed around as a string - but that
string is teh palette name in GIMP- teh palette is them usable with
all palette -related PDB functions
There is no higher level Palette object on the Python side - and it
makes little sens implementing one with the bindigns as they are now
(it would require writting the pallete functionality in low-level C)
But having the string passed around between plug-ins works as nicely
as it can be - I had written some palette creating/exporting a few
years ago.
On 6 September 2013 14:11, Chris Mohler <cr33dog gmail com> wrote:
On Thu, Sep 5, 2013 at 11:30 PM, Warren Turkal <wt penguintechs org> wrote:
Just so you all know, this actually started with my wife wanting to import
*.ase palettes in .
Same here, but I just wanted to use Kuler palettes. Adobe claims the
.ase specs are in the PS SDK, but if they are I never found them.
That's about as far down the rabbit hole as I got - I didn't feel like
reverse-engineering the PS palette format.
Back to your main question: unless I'm out of touch, I believe all of
the file loader plugins need to be written in C. I could well be
wrong though. It's been quite some time since I touched anything
having to do with GIMP besides the occasional plug-in in Python.
Chris
_______________________________________________
gimp-developer-list mailing list
List address: gimp-developer-list gnome org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]