Hello John,
On 16.06.06, John Owens wrote:
> So first, I don't really have a strong opinion on this. But, when I think
> "palette", I usually think of a discrete one, as the artist's palette with a
> number of paint spots on it, rather than a linear one, which I would regard
> more as a color ramp. I don't have a strong enough opinion to argue
> forcefully for what is appropriate for PyX though, and will be happy to
> defer to the developers on this.
I'd would like to suggest to use
- color.gradient for the continuous version and
- color.palette for the discrete version
AFAIR, this is the notation used by Gimp and I remember to have prefered
the name "gradient" already quite some time ago ;-)
> That being said, though, I'd like to put the schemes in the code, and
> would like to know how I could do this.
>
> - First I need to make attr.changelists with names, not a problem.
> - Then I need to get permission, which I'm working on. It appears that
> the way we'd like to go is for the author of the schemes to license the
> schemes to PyX under the GPL; is that acceptable?
This is ok.
> - Next, how would you like them integrated? Separate file or at the
> end of color.py?
I'd suggest to put it into color.py (if it's not too big). The hierarchy
should be something like (in the above proposed naming scheme):
color.palette.namexyz
> And should I email them to you?
The prefered way would be to submit them as a patch via SF,
alternatively you can also mail them to us.
> - Finally, documentation ... how should these be exposed?
Maybe something similar to the way the manual documents
the current palettes:
http://pyx.sourceforge.net/manual/palettename.html
In other words, you might want to write a PyX file which produces a
sample with all the different palettes. You might want to have a look
into the manual subdirectory in the Subversion repository for how to do
this.
Jörg
_______________________________________________
PyX-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyx-user
