It was a precompilation thing that was breaking, but it may have been related to another package, as they were installing a few. But fair enough, it is easier to develop outside of base. Carry on.
On Thursday, March 10, 2016 at 12:23:17 PM UTC-5, Tom Breloff wrote: > > > > On Thu, Mar 10, 2016 at 12:08 PM, j verzani <[email protected] > <javascript:>> wrote: > >> As someone who has watched his calculus students struggle with what >> should be a trivial task -- the installation of `Plots` on `juliabox`, I've >> wished it were part of base. >> > > While in my (very biased) opinion I think Plots should be the first > package new users install, I don't think it belongs in base. (please don't > make me rebuild julia to hack on Plots ;) But I'm wondering... what was so > hard about installing on juliabox? Did the `Pkg` commands not work? > > >> The `plotly` backend does not require additional dependencies, so with >> that as a default, it would be one less hurdle for newcomers. >> > > Right now, it's the default if nothing else is installed: > https://github.com/tbreloff/Plots.jl/blob/master/src/plotter2.jl#L74 > > >> >> >> On Thursday, March 10, 2016 at 8:11:57 AM UTC-5, Daniel Carrera wrote: >>> >>> Hello, >>> >>> Does anyone know the status of Plots.jl? It seems to have come a long >>> way. At least the documentation makes it look pretty complete: >>> >>> http://plots.readthedocs.org/en/latest/ >>> >>> I'm looking at the backends. Does anyone know what "Gr", "Qwt", and >>> "unicodeplots" are? Apparently support for Winston was dropped? >>> >>> https://github.com/tbreloff/Plots.jl/issues/152 >>> >>> I don't use Winston, but I'm curious to know what happened. Was Winston >>> hard to support? >>> >>> I am currently using PyPlot because I need the maturity of Matplotlib, >>> but I am happy to see all the effort that's going into making a native >>> plotting library for Julia. >>> >>> Cheers, >>> Daniel. >>> >> >
