winston backend

[juliaplots]

winston backend

[tbreloff]

This is an excellent start... thanks! I mainly didn't start with dictionary mappings because

• Dependencies aren't loaded immediately, so if you need to put a Winston.Circle (for example) in the dictionary mapping it will fail (it doesn't know about Winston yet).
• There hasn't exactly been a 1-1 mapping for most stuff.

For this case, it seems like a dict should work fine.

You should create a pull request for this on the dev branch. The file should be in src/backends/winston.jl. If you don't care about the credit, then I'm also happy to just copy/paste. Let me know!

[jverzani]

Feel free to copy and paste. That will likely be easier for you too. As for checking, I just meant to check that a proper value was passed in so that in the backend the value passed as a key is known to be correct. But you are right, there are likely values that depend on the underlying package being loaded.

[tbreloff]

One of the things I'm working on now is a more complete/robust approach for
understanding what is supported with each backend, and warning the user (or
erroring if necessary). It will probably take a few iterations to get
right. Thanks for the permission to copy... I'll make a note in the
comments.

On Wed, Sep 16, 2015 at 10:44 AM, john verzani [email protected]
wrote:

Feel free to copy and paste. That will likely be easier for you too. As
for checking, I just meant to check that a proper value was passed in so
that in the backend the value passed as a key is known to be correct. But
you are right, there are likely values that depend on the underlying
package being loaded.

—
Reply to this email directly or view it on GitHub
#18 (comment).

[tbreloff]

Lets leave it open... I'll close it when I'm done with Winston support.

[tbreloff]

Pretty good progress! Thanks again for the head start. Check out the Winston examples and if you're curious where I'm going with the backend code, look here

[jverzani]

Nice. You are like a coding machine-- one new backend per day before lunch!
I wasn't clear exactly what fillto specifies, but Winston does have those
functions FillAbove/Below/Between functions sitting there.

On Wed, Sep 16, 2015 at 5:21 PM, Tom Breloff [email protected]
wrote:

Pretty good progress! Thanks again for the head start. Check out the Winston
examples
https://github.com/tbreloff/Plots.jl/blob/dev/docs/winston_examples.md
and if you're curious where I'm going with the backend code, look here
https://github.com/tbreloff/Plots.jl/blob/dev/src/backends/winston.jl

—
Reply to this email directly or view it on GitHub
#18 (comment).

John Verzani
Chair, Department of Mathematics
College of Staten Island, CUNY
[email protected]

[Evizero]

+1 to coding machine

[tbreloff]

Heh... Just trying to make sure the skeptics get a good first impression. I don't want people to brush it off because "you don't support XYZ so I can't use it". It's pretty easy to add features and backends now that the framework is somewhat stable.

On Sep 16, 2015, at 5:33 PM, Christof Stocker [email protected] wrote:

+1 to coding machine

—
Reply to this email directly or view it on GitHub.

[tbreloff]

Also regarding fillto... in my mind it is used for 2 puposes. It can be used to turn a line plot into an area plot:

or could be used for bar/histogram plots as well:

Winston's FillAbove/Below/Between might work... maybe I need to call both FillAbove and FillBelow to make it work?

[tbreloff]

Actually this was easier than expected. I used Winston.FillBetween:

plot(sin,0,3π; fillto=0.5)

x=0:0.1:3π
plot(sin,x; fillto=cumsum(randn(length(x))/10))

[tbreloff]

@jverzani I'm curious... how much do you care about Winston as a backend? It's fallen a bit behind in the dev cycle, and I'm not sure I see a clear reason to use it over, say, Immerse. Would anyone be disappointed if I deprecate it at the same time I stop supporting 0.3?

[jverzani]

I don't actually use it personally, but for a little side project
(GtkInteract) Winston is the only realistic backend at the moment. I'll see
if I can GtkInteract to work with the display mechanism of immerse there,
so that Plots can be supported that way. Thanks for asking.

On Sun, Oct 18, 2015 at 1:10 AM, Tom Breloff [email protected]
wrote:

@jverzani https://github.com/jverzani I'm curious... how much do you
care about Winston as a backend? It's fallen a bit behind in the dev cycle,
and I'm not sure I see a clear reason to use it over, say, Immerse. Would
anyone be disappointed if I deprecate it at the same time I stop supporting
0.3?

—
Reply to this email directly or view it on GitHub
#18 (comment).

John Verzani
Chair, Department of Mathematics
College of Staten Island, CUNY
[email protected]

[jverzani]

Okay, adding Immerse support to my project was easy. Deprecating Winston support won't cause any concerns on my end.

[tbreloff]

Ok thanks. If anyone else has an opinion on Winston, please chime in. The code in Immerse is very similar (it might have even been copied directly?) and I think it's a better backend. I want to start supporting Vega and GLPlot, and eventually Qt5, which all offer some different strengths, so the fewer distractions the better.

Also I may deprecate Qwt as well once Qt5 becomes usable.

On Oct 18, 2015, at 11:01 AM, john verzani [email protected] wrote:

Closed #18.

—
Reply to this email directly or view it on GitHub.