Andre Wobst <wobsta <at> users.sourceforge.net> writes:

> I would suggest to use a changeable attribute iterating over a list of
> colors:

Perfect. Yes, of course, that's what I want.

> First of all I think some good color schemes are very useful. They
> could be used by many PyX users and its a good idea to include some
> handy defaults in the PyX core. However, I don't like the wording. At
> the moment palettes are *not* just changeable attributes and are *not*
> discrete (by definition). Maybe we're using the wrong wording and your
> discrete palettes is what palettes really should be (since people
> expect that). We need a second word here and I want to make that being
> related to discrete color spaces as we can (and will) add support for
> discrete color spaces on PostScript and PDF level later on. Sure we
> could start to use continuouspalette and discretepalette, but maybe
> we could come up with some better wording (even containing "index"
> somehow). For example, a palette could get a indexed method which
> takes an argument (how many discrete colors should be taken from the
> palette) and it then returns an "indexedcolorspace". The
> "indexedcolorspace" could be a changeable attribute at the same time
> but with a fixed number of colors (instead of a variable number for
> palettes).

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.

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?

- Next, how would you like them integrated? Separate file or at the
end of color.py? And should I email them to you?

- Finally, documentation ... how should these be exposed? 

JDO



_______________________________________________
PyX-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyx-user

Reply via email to