PyPlot is now mostly supported on the master branch of Plots.jl. See the readme/examples. Comments/issues welcome.
On Sun, Sep 13, 2015 at 4:17 PM, David van Leeuwen < david.vanleeu...@gmail.com> wrote: > Hello, > > On Thursday, September 10, 2015 at 10:26:35 PM UTC+2, Tom Breloff wrote: >> >> This may be a slightly premature announcement, but I wanted to put it out >> there so that people that have strong opinions have a chance to give their >> thoughts. Here's the link: >> >> https://github.com/tbreloff/Plots.jl >> >> Plots.jl is intended to be an API/interface that sits above other >> plotting packages (backends) and gives the user simple, consistent, and >> flexible plotting commands. It's a problem when someone is used to a >> package which is great for interactive plots, but then has to re-learn and >> re-code new plots in another package when producing publication-quality >> plots (or vice versa). The same goes for switching between desktop GUIs >> and javascript technologies... sometimes one package is better than another >> for a specific task, and it's a shame to be forced to choose. >> >> I think this is a great idea! > > ---david > > > >> I've implemented a bunch of functionality for both Gadfly.jl and Qwt.jl >> backends. See the examples to get a sense of how they differ. I think >> Vega.jl and UnicodePlots.jl might be next on my priority list, but please >> let me know if I should prioritize differently. Note: This is still a work >> in progress, and I will probably change parts of the API, and not every >> plot type is implemented yet. >> >> Please let me know comments, wish lists, etc. Issues are great for >> actionable items, comments can go here. This effort was partially inspired >> by various discussions here and on github, which prompted the forming of >> https://github.com/JuliaPlot, and an effort to improve the plotting >> landscape with tutorials and documentation. If you're interested: >> https://github.com/JuliaPlot/juliaplot_docs/issues >> >> Tom >> >
