created stand-alone scripts that reproduce the plots in the docs #142
Conversation
…cale dependent, previous example was a bit confusing as the results looked no different
* 'master' of github.com:ioam/geoviews: changed scale example in Geometries notebook to use feature that is scale dependent, previous example was a bit confusing as the results looked no different (holoviz#137) Fixed sphinx pin in previous commit.
|
Thanks! These are clearly useful for GeoViews users, but I'd be concerned about our ability to maintain them and keep them up to date as the original versions change over time. For one thing, as we implement #121 , we'll have dozens of separate notebooks, each of which could usefully have an associated script. Should we not just use an automatic mechanism to convert each notebook into a runnable python script, which I believe @jlstevens has prototyped if I am not making that up? Then every page could have a link saying "Right click to download this code as a notebook or as a script to try it out yourself". |
That's right although it is (as you say) a prototype right now though if I have a chance I can clean it up (the conversion will be done using the holoviews console script). |
|
The inclusion of the .options method recently already made me think maintaining will be an issue. Having a conversion script would be heaps better! |
When I first started not having working examples was quite difficult. It's obvious to me now how to get the same results as the ipython magics, but at the time I recall it was quite confusing
These should be useful for people who don't or can't use the notebooks.
I tried to show a few different ways to set the plot options, i.e. globally, or locally, using dictionary or strings.
I wasn't 100% sure when to put them, so ended up putting them in the notebooks/user_guide directory.
In the docs there is a link that says "Right click to download this notebook from GitHub."
I would also suggest adding "Right click to download this script from GitHub."