Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial draft of james_bednar chapter #26

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

jbednar
Copy link
Contributor

@jbednar jbednar commented Apr 27, 2018

Initial draft of the PyViz/HoloViews chapter for the cookbook. Ready for review.

The notebook version of this chapter can be viewed at anaconda.org.

@jbednar
Copy link
Contributor Author

jbednar commented Apr 28, 2018

For my own future reference, the .rst file was generated by running the included notebook in the pyviz environment, then saving it as .rst twice, with different display formats:

hv.extension('matplotlib', 'bokeh', width=100, display_formats=['svg','html'])
hv.extension('matplotlib', 'bokeh', width=100, display_formats=['png'])

The .svg versions of the Matplotlib figures used in the paper came from the first run (separately converted to PDF), and the PNG versions of the Bokeh figures came from the second one. I also took screenshots for cells that require HTML for proper display, such as those with associated widgets (from holomaps and parambokeh) or those with pandas tables. (Presumably there is some way to get a .rst-compatible table formatting of a pandas dataframe display, but I didn't see one.)

Because the paper alternates rapidly between text, code, and graphical output, I did not designate the plots as figures with captions, but if that's deemed necessary I can do so. Seems to me like that would detract from the flow, in this case, where inline images seem more appropriate (and more notebook-like).

I had to substantially reorganize the code to fit into the two-column format, making it not always as clean and easy to read, so it might be worth considering whether the book should be in a one-column format.

Note that the code and output cells are designated as different markup categories in the .rst, but when compiled to PDF via latex in this workflow, they end up being rendered similarly, which is confusing. Maybe the code listings could have a light-grey background or a box around them or something else to distinguish them visibly from textual output?

@jbednar jbednar mentioned this pull request May 6, 2019
41 tasks
@jbednar jbednar mentioned this pull request Sep 21, 2020
48 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant