On Fri, 22 Feb 2008 10:04:33 +0100 Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
> Jean-Marc Lasgouttes wrote: > > Martin Vermeer <[EMAIL PROTECTED]> writes: > > > >>> or we > >>> need ColorSet::ColorSet() to include the hex values directly. Or else we > >>> need to hardcode the hex values where they're wanted. > >> Rather not. The ColorSet list should be able to contain official X11 names > >> at that position. > > > > I am not sure that using official X11 color names still make sense now > > that LyX is not a unix/x11 thing only anymore and that we have a color > > picker (and no way to see the names in the interface anyway). > > Qt understand X11 color names but we should probably go toward a cross > platform definition indeed. Qt docs recommend the SVG color names: > > http://www.w3.org/TR/SVG/types.html#ColorKeywords > > void QColor::setNamedColor ( const QString & name ) > Sets the RGB value of this QColor to name, which may be in one of these > formats: > #RGB (each of R, G, and B is a single hex digit) > #RRGGBB > #RRRGGGBBB > #RRRRGGGGBBBB > A name from the list of colors defined in the list of SVG color keyword > names provided by the World Wide Web Consortium; for example, > "steelblue" or "gainsboro". These color names work on all platforms. > transparent - representing the absence of a color. > X11 only: If allowX11ColorNames() returns true, any valid X11 color > name. See the documentation for XParseColor() for information about > valid X11 color names. > > Abdel. Sounds like a plan. And it seems that these SVG colours actually include the X colours. - Martin
