Merge branch 'master' of github.com:sandialabs/toyplot

Author: tshead2

conda.recipe/bld.bat

@@ -0,0 +1 @@
+python setup.py install

conda.recipe/meta.yaml

@@ -0,0 +1,28 @@
+package:
+  name: toyplot
+  version: {{ environ['GIT_DESCRIBE_TAG'] }}
+
+source:
+  git_url: ../
+
+build:
+  script: python setup.py install
+  number: {{ environ.get('GIT_DESCRIBE_NUMBER', 0) }}
+
+requirements:
+  build:
+    - setuptools
+    - colormath
+    - multipledispatch
+    - numpy >=1.7
+  run:
+    - colormath
+    - multipledispatch
+    - numpy >=1.7
+
+
+about:
+  home: http://github.com/sandialabs/toyplot
+  license: BSD
+  summary: A modern plotting toolkit supporting electronic publishing and reproducibility.
+

design/embedding.py

@@ -0,0 +1,36 @@
+# Note: we prefer PyQt5 only because we've had issues embedding our HTML output
+# with specific versions (Qt 4.8.7 on a Mac) of QWebView.  Otherwise, the
+# functionality is equivalent.
+
+try:
+  from PyQt5.QtWidgets import *
+  from PyQt5.QtWebKitWidgets import *
+except:
+  from PySide.QtGui import *
+  from PySide.QtWebKit import *
+
+import numpy
+import sys
+import toyplot.html, toyplot.png, toyplot.svg
+import xml.etree.ElementTree as xml
+
+application = QApplication(sys.argv)
+window = QWebView()
+
+canvas, axes, mark = toyplot.plot(numpy.linspace(0, 1) ** 2)
+
+# Embed Toyplot HTML output in a QWebView.  This is the best option because it
+# retains figure interaction.
+window.setHtml(xml.tostring(toyplot.html.render(canvas), method="html"))
+
+# Embed Toyplot SVG in a QWebView.  This retains the figure quality, but no
+# interaction.
+#window.setContent(xml.tostring(toyplot.svg.render(canvas)), "image/svg+xml")
+
+# Embed Toyplot PNG in a QWebView.  This requires additional Python
+# dependencies, doesn't scale cleanly, and has no interaction.
+#window.setContent(toyplot.png.render(canvas), "image/png")
+
+#window.settings().setAttribute(QWebSettings.DeveloperExtrasEnabled, True)
+window.show()
+application.exec_()

design/qt-embedding.py

@@ -0,0 +1,20 @@
+.. _compatibility:
+
+.. image:: ../artwork/toyplot.png
+  :width: 200px
+  :align: right
+
+Compatibility
+=============
+
+A quick disclaimer on backwards-compatibility for Toyplot users:
+
+Toyplot follows the `Semantic Versioning <http://semver.org>`_ standard for
+assigning version numbers in a way that has specific meaning.  As of this
+writing Toyplot releases are still in the `0.y.z` development phase, which
+means (among other things) that the API may change at any time.  We try not to
+be abusive about it, and in practice there have been very few breaking changes
+in Toyplot's history, but they can and will happen on the road to the 1.0
+release, and you should be prepared for it.
+
+

design/series-labels.ipynb

@@ -35,18 +35,6 @@ Coding Style
 The Toyplot source code follows the `PEP-8 Style Guide for Python Code <http://legacy.python.org/dev/peps/pep-0008>`_,
 except that we use two spaces for indentation instead of four.
 
-Code Walkthrough
-----------------
-
-Most of Toyplot's public API is located in `toyplot/__init__.py` ... for most
-contributations, that's where you'll start.  If you're adding a new type of
-visualization, you'll need to create a new :class:`toyplot.Mark` derivative
-there.  Then, you'll create factory methods for creating instances of your
-new mark in :class:`toyplot.axes.Cartesian` and/or :class:`toyplot.canvas.Canvas`.  Once
-you've done that, you'll need to write code to render your new mark
-in `toyplot/svg.py`.  That's it ... all of the other backends are rendered
-from the SVG representation.
-
 Running Regression Tests
 ------------------------
 
@@ -66,7 +54,7 @@ Writing Regression Tests
   Toyplot is in the midst of a transition from `nose <https://nose.readthedocs.org/en/latest/>`_
   to `behave <http://pythonhosted.org/behave>`_ for running regression tests.  New tests should
   be added to the `features` directory using behave.  The following outlines how the old tests
-  were written, and wll remain as a reference until they are all replaced.
+  were written, and will remain as a reference until they are all replaced.
 
 Existing tests are located in `tests/tests.py`.