[matplotlib-devel] Re: Matplotlib: wxWindows backend

[John H. <jdh...@ac...>]

    Jeremy> My Debian machine is Python 2.3, and it seems to work
    Jeremy> there. As I mentioned, the code seems (on Linux) to need
    Jeremy> to run in a PyCrust shell at the moment - I need to fix
    Jeremy> this, but I suspect that it means getting bogged down in
    Jeremy> details of how the event loop works, which I'd rather put
    Jeremy> off until the main backend is stable.

I think this is not too hard.  I created a 

  wxapp = wxPySimpleApp()

at the top of backend_wx (to solve the bitmap problem).  Then in
ShowOn.realize_windows I called wxapp.MainLoop().  With these changes
I can call 

  > python simple_plot.py -dWX

and it launches!!  I am very excited about this wx backend, by the
way.

    Jeremy> I have no worries about dealing with several people on CVS
    Jeremy> at the same time.  At work we have about 50 developers
    Jeremy> working on the same codebase (admittedly with a slightly
    Jeremy> more heavyweight SCM tool). Basically the rules are:

Thanks for the CVS info.  You'll need to get a sourceforge account if
you don't already have one, and send me your user name.  Then I'll add
you as a developer so you can have write access to the repository.

I'll do some reading up on CVS.  What happens if we both check out a
copy of the wx backend and make changes to different functions in the
same file, and then both check the code back in?  Will CVS
automagically update the separate parts of the file, or will the
second person get an error saying "You can't check this in because the
CVS file has changed since you checked out", or what?

I made a couple of small changes to your code (BTW, I don't know if
matplotlib-devel is working because none of my emails have made it
through).  The images dir is now in the matplotlib root (where
setup.py and the fonts dir reside).  The distutils installer puts them
in the matplotlib shared dir for data files, and I changed
_load_bitmap to look for them there.  This maintains consistency with
how I deal with other data files, eg, font files.

Also, I added a KNOWN BUGS section to backend_wx.py where I pasted in
those from your email and added some I came across while running most
of the demos.  We can both use that area to keep up with known bugs
and fixes.

JDH