Why not have them available by default? Do these make loading Colors much
slower?
On Tuesday, November 24, 2015, Tom Breloff <t...@breloff.com> wrote:
> Single package preferred, and if possible it would be great to be fully
> compatible with Colors.jl. It might be ideal if it was part of Colors.jl,
> but loaded on demand, perhaps by calling:
>
> function i_am_feeling_wacky_today()
> @eval include("wacky.jl")
> end
>
> or some similar trickery...
>
> On Tue, Nov 24, 2015 at 5:27 PM, Gabriel Gellner <gabrielgell...@gmail.com
> <javascript:_e(%7B%7D,'cvml','gabrielgell...@gmail.com');>> wrote:
>
>> As an end user that would love this, I would prefer a single package. Put
>> all them tasty, wacky colors in one place!
>>
>>
>> On Tuesday, 24 November 2015 14:08:35 UTC-8, Randy Zwitch wrote:
>>>
>>> Since the Julia ecosystem is getting bigger, I figured I'd propose this
>>> here first and see what people think is the right way forward (instead of
>>> wasting people's time at METADATA)
>>>
>>> In the R community, they've created two packages of novelty color
>>> schemes: Wes Anderson <https://github.com/karthik/wesanderson> and
>>> Beyonce <https://github.com/dill/beyonce>. While humorous, these color
>>> palettes are interesting to me and I'd like to make them available in
>>> Vega.jl (and Julia more broadly). Should I:
>>>
>>> 1) Not do it at all....because this is a serious, scientific community!
>>> 2) Do two separate packages, mimicking R
>>> 3) Create a single NoveltyColors.jl package, in case there are other
>>> palettes that come up in the future
>>> 4) Make a feature request at Colors.jl (really not my favorite choice,
>>> since there is so much cited research behind the palettes)
>>>
>>> I neglected to mention ColorBrewer.jl (which Vega.jl uses), since
>>> ColorBrewer is a known entity in the plotting community.
>>>
>>> What do people think? Note, I'm not looking for anyone to do the work
>>> (I'll do it), just looking for packaging input.
>>>
>>
>
