This is a pre-production deployment of Warehouse. Changes made here affect the production instance of PyPI (pypi.python.org).
Help us improve Python packaging - Donate today!

Sphinx extensions for writing interactive documents.

Project Description

Packaging of the Runestone components for publishing educational materials using Sphinx and restructuredText. Check out the Overview To see all of the extensions in action. NOTE – If you have used an older version of this repo, please know this is a total restart. I think much better, and it WILL stay up to date as this is now the master copy of the components not just a copy. Check out the Development Roadmap to get an understanding of our migration towards webcomponents.

## Quick Start

If you are completely new to pip and github text editors, I have written a more thorough getting started

tutorial on my blog Otherwise, you can install everything you need with one simple command! (Although I recommend that you first create a virtual environment for your work.)

Install and make a Python virtualenv

$sudo pip install virtualenv$ virtualenv /path/to/home/MyEnv
$source /path/to/home/MyEnv/bin/activate  • You will need to do the last command every time you want to work on RunestoneComponents. If you have not used Python virtual environments before I strongly recommend reading the docs or watching the video With the virtual environment installed and configured you can continue. pip install runestone  Or, if you prefer to live on the development edge, you can check out the very latest from: pip install git+git://github.com/RunestoneInteractive/RunestoneComponents.git  To start a project, create a new folder and then run the following command (installed by pip) in that new folder runestone init For example: mkdir myproject cd myproject runestone init  The init command will ask you some questions and setup a default project for you. To build the included default project run runestone build  You will now have a build folder with a file index.html in it, along with some default content. The contents of the build folder are suitable for hosting anywhere that you can serve static web content from! For a small class you could even serve the content using the builtin Python webserver. $ runestone serve


Now from your browser you can open up http://localhost:8000/index.html You should see the table of contents for a sample page. If you edit _sources/index.html or _sources/overview.rst and then rebuild and serve again you will see your changes. The best documentation is probably the overview.rst file itself, as it demonstrates how to use all of the common components and shows most of their options.

Windows Users I have tested the installation, along with init, build, and serve on Windows 8.1. The biggest pain is probably setting your PATH environment variable so you can simply type the commands from the shell. Please note that I am not a regular user of windows, I only test things on my VMWare installation every so often. If you are new to using Python on windows I recommend you check out this link on Using Python with Windows

## Developing and Hacking

So, you would like to help out with developing the Runestone Components. What do you need to know?

1. Make a Fork of this repository.
1. Make a virtual environment for testing and working (I recommend pyvenv-3.4 as it is baked in to Python 3.4 and higher)
2. To use Runestone Components, rather than following the instructions above for installing runestone simply run pip install -e . from the top level runestone directory. This will install all of the required prerequisites and setup the runestone install as a link to the development directory.
3. When you have some changes to share, make a Pull Request.

(See the RunestoneServer repository and http://runestoneinteractive.org for more complete documentation on how this project works.)

## Writing Tests

A great way to contribute to the Runestone Components repository is to add to our test suite.

Our goal is to have unit tests which rely on Selenium (a library that helps simulate interactions in a web browser) for each directive, to see if the JavaScript that powers the directives is working correctly.

In order to get started with writing a test/writing additional tests, you will need the following:

• pip install selenium in the virtualenv you’re using for Runestone Components development
• pip install pyvirtualdisplay
• On linux you will need to install Xvfb apt-get install xvfb
• You’ll also need to have done the above installation.
• You should be using virtual environment, you’ll need a clone of the RunestoneComponents repository, and you’ll need to have done pip install -e from the top level of the RunestoneComponents directory.

To run tests:

• Make sure the directory containing the PhantomJS executable is in your PATH environment variable. e.g. PATH=\$PATH:path/to/thedirectory/where/it/is/here at your command line (or edit your .bash_profile).
• Check out the existing tests, e.g. the test_question.py file that tests the Question directive, which you can find at the path /runestone/question/test/test_question.py, for an example.
• Each directive’s individual set of tests requires a mini book. You’ll see a _sources folder for each existing test containing an index.rst file. That file contains a title, as required by .rst, and whatever directive examples you want to test.
• Finally, to run a test, ensuring that you have accessed a test folder within a directive folder, type the following at the command prompt in this order:
• runestone build (to build the mini-book for testing)
• runestone serve --port 8081 &
• python <testfilename>.py, e.g. python test_question.py

Note

8081 is the default test port. See the Python files, e.g. test_question.py, to see how this is set up. The & will set the process to run in the background. The mini-book needs to be served in order to test what’s in the DOM as a result of using these components!

You should then see some test output, showing a pass (ok), FAIL, or error(s).

If you have an error relating to PhantomJS/a driver in the output, you probably have a PATH or driver installation problem.

To write a new test:

• Create a test directory inside a directive’s folder
• Create a Python file to hold the test suite inside that directory, e.g. test_directivename.py
• Run runestone init inside that folder and answer the following prompts
• Write the appropriate directive example(s) inside the index.rst file (which will be created as a result of runestone init)
• Edit the Python file you created as appropriate (see documentation for the Python unittest module here.)

## Notes for more Advanced Users

If you already have an existing Sphinx project and you want to incorporate the runestone components into your project you can just make a couple of simple edits to your existing conf.py file.

• First add the following import line from runestone import runestone_static_dirs, runestone_extensions
• Then modify your extensions. You may have a different set of extensions already enabled, but it doesn’t matter just do this: extensions = ['sphinx.ext.mathjax'] + runestone_extensions()
• Then modify your html_static_path: html_static_path = ['_static']  + runestone_static_dirs() Again you may have your own set of static paths in the initial list.

See https://github.com/bnmnetp/runestone/wiki/DevelopmentRoadmap to get a sense for how this is all going to come together.

Release History

This version

3.0.6

3.0.5

3.0.4

3.0.3

3.0.2

3.0.1

3.0.0

3.0.0b6

3.0.0b5

3.0.0b4

3.0.0b3

3.0.0b2

3.0.0b1

2.7.15

2.7.14

2.7.13

2.7.12

2.7.11

2.7.10

2.7.9

2.7.8

2.7.7

2.7.6

2.7.5

2.7.4

2.7.3

2.7.2

2.7.1

2.7.0

2.6.10

2.6.9

2.6.8

2.6.7

2.6.6

2.6.5

2.6.4

2.6.3

2.6.2

2.6.1

2.6.0

2.5.0

2.4.0

2.3.6

2.3.5

2.3.4

2.3.3

2.3.2

2.3.1

2.3.0

2.2.2

2.2.1

2.2.0

2.1.6

2.1.5

2.1.4

2.1.3

2.1.2

2.1.1

2.1.0

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

2.0a6