--- Joerg Lehmann <[EMAIL PROTECTED]> wrote: > When posting my initial scheme, this was also obvious to me. On the > other hand, it's not what a color palette usually means: an ordered > collection of a finite number of colors. But we could reconcile > these two pictures of a palette as described in my other mail, but > considering the trivial mapping > [[c11], [c21, c22], [c31, c32, c33], ...] -> > [c11, c21, c22, c31, c32, c33, ...]
I don't really see why the second one is better than the first. The first has the advantage of being able to identify several different palettes, one for each number-of-colors, while the second one it's much harder to do that. > This is something which has to be discussed (try import this and look > at line number four, counting empty lines). The needed input would > be: > - how many variants does a given scheme typically have? > - can the fall-back behaviour in the case of a variant not > exisiting for the given total number of colors be well defined, i.e. > how implicit would the choice be? I apologize, I'm not sure what you mean by "import this and look at line number four". To answer your questions: - A named scheme (in colorbrewer) usually ranges from 3 to 10 total-number-of-colors (I appended one in my last message). - Fallback could be either done by the user or by PyX. It'd be nice if PyX had a default fallback (and I would advocate if too few colors, take the first n colors of the variant with the smallest number of colors; if too many colors, do a gradient between the first and last colors of the variant with the most colors), and that the user could override the default if he/she chooses. JDO __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ PyX-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyx-devel
