document color specification #1374
Comments
|
The documents of Colors.jl provide the named color charts. However, there is currently an issue regarding whether the color names with spaces (e.g. "old lace") are valid. (cf. #1368, JuliaGraphics/Colors.jl#386, JuliaGraphics/Colors.jl#388) |
|
thanks! i had noticed mention of `Colors.jl, but wasn't sure which ones were suitable to use as the single point of truth. the document behind the link is exactly what i was looking for; i only wish the Gadfly docs had made it more evident where to look. |
|
On new Colors.jl (i.e. v0.10 or later), the color names with spaces are not recommended. (cf. #1368 (comment)) |
|
i think this is a fairly minor, low-priority change; it would be nice to have, but could easily wait. |
|
@ben-schulz care to make a PR pointing to GiovineItalia/Compose.jl#380 (comment) ? |
|
@bjarthur : i have a patch, but i seem to be having some trouble building the docs, so i haven't made a PR yet. is there somewhere i could check the status of the doc build, or are there special instructions for building the docs of this project? i'm getting a ton of warnings from the code blocks, ending in an uncaught error that appears to originate outside of the modified text. this is my first time building the docs ( following the generic instructions for Documenter ), so i may very well be doing something wrong -- though i admit that i'm unsure what. |
|
see the gadfly specific instructions. shouldn't be much different the the generic ones though. did you do this in a clean environment? if not, perhaps you're got incompatible packages installed. |
|
@bjarthur : thanks for the pointer! unfortunately, i've tried it, and still running into the same issue. more explicitly, running the Julia 1.3.1 binary for Linux/x86, i did the following: i'm totally willing to admit that i might be making some noob mistake somewhere in here -- but the commands above look to me like they should clean the existing Julia packages and instantiate the environment specified in the does Julia stash package artifacts anywhere besides the |
This seems to be a potential bug on the 32-bit version. function Table(m::Integer, n::Integer, y_focus::UnitRange{Int}, x_focus::UnitRange{Int};
y_prop=nothing, x_prop=nothing,
aspect_ratio=nothing,
units=nothing, order=0, withjs=false, withoutjs=false,
fixed_configs=Any[]) |
|
thanks for advising; i'll try building from source, and also open an issue on Compose.jl, since this seems like an unexpected platform-specific behavior. |
add hyperlink to color table in `Colors.jl`, and reference as the source for permissible color names.
add hyperlink to color table in `Colors.jl`, and reference that library as the point-of-truth.
add hyperlink to table in `Colors.jl`, and note that library as the point-of-truth. incorporate revision suggested by @Mattriks.
it would be helpful if the docs at http://gadflyjl.org listed the allowed color values e.g. as a table, so that it would be evident whether a usage is valid.
e.g. is there a reference i could use to check whether
Theme( default_color="foo" )orScale.lab_gradient("foo", "bar", "baz")produces a valid style element?i saw that a related issue (#254) had been opened and closed back in 2014. i also noticed this mention in the tutorial:
which gives a hint of where i might look -- but it felt like a circuitous path to take just to find out whether, for example,
"cyan"or"darkred"were recognizable values.The text was updated successfully, but these errors were encountered: