On Fri, May 16, 2008 at 7:18 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Yeah. Those all use the SWIG wrapper to Agg that we ultimately decided not
> to use. I think clearing out the examples is probably a
> good idea -- though moving them to some part of SVN (outside of the main
> trunk) might be a good idea so we don't "lose" them.
> The SWIG wrapper represents a lot of work and may be useful in the future.
I removed these from the trunk since they are already in the maintenance branch.
On the subject of examples, one thing I'd like to do is organize them a bit
- "pylab" - all the current examples that do "from pylab import *"
with a README indicating that while this idiom is fine for interactive
use, for scripts or anything worth keepking, we recommend pyplot
- "pyplot" - as we get time, rewrite the examples from pylab using
the pyplot and numpy namespaces, and emphasizing the API, eg
import numpy as np
import matplotlib.pyplot as plt\
fig = plt.figure()
ax = fig.add_subplot(111)
ax.plot(np.random.rand(10))
ax.set_title('a simple plot')
plt.show()
- "applications" or "user_interfaces" or something like that. All
the UI examples
- animations - example code doing dynamic/animated plotting. this
overlaps a bit wtih user interfaces since the recommended way to do
animations is with the GUI event loop
- event handling - interacting with the plot, mouse and key events, picking
- widgets - the mpl widget examples
Does anyone object to me doing this, or would like to see it done otherwise?
JDH
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel