[matplotlib-devel] WXAgg backend updates
Hello everyone, I just committed some accelerator-related updates to the WXAgg backend. I have fixed the problem with the way I was calling the wxBitmap constructor in _wxagg.src. More importantly, I written another set of the agg-to-wx.Bitmap conversion routines that uses the new BitmapFromBufferRGBA() function in wxPython 2.8. The blit() routine also got a bit faster after I realized it was more efficient to just convert the whole buffer and blit part of it instead of clipping during conversion. I have tested these changes with wxPython 2.8.1.1 under OSX 10.4.8. My goal is that none of the changes break compatibility with wxPython 2.4 or 2.6. I'd really appreciate it if someone could test and benchmark those versions using `examples/animation_blit_wx.py'. Ken - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Patch for enhancement of PDF backend
On 2/21/07, Jouni K. Seppänen <[EMAIL PROTECTED]> wrote: > > Have you had time to look at my patch regarding the PDF backend? :-) > > A bit, and I couldn't quite get it to work. But what the heck, let's > put it in the repository so we can all hack on it. It is quite an > improvement to the backend, and it doesn't seem to break anything that > used to work. (I ran the examples using backend_driver.py on both agg > and pdf.) Your patch (slightly modified) is committed as of svn > revision 3027. Thanks Jouni for committing this patch. Now, I'm working on the two issues you've mentioned below. I'll probably send a new patch fixing the font issue in the next few days. > The problem I'm having is that if I set use14corefonts on, I have to > make sure that Helvetica (or whatever) is chosen as the text font. > I used to have the setting > > font.sans-serif : Bitstream Vera Sans > > because that font works, and some other fonts that mpl finds (on my > OS X system) don't; but then setting use14corefonts on caused the afm > header parser to be called on Vera.ttf, which it obviously couldn't > make any sense of. I'm not sure I quite understand the Matplotlib font > selection system, though. > > Replacing the setting by > > font.sans-serif : Helvetica, Bitstream Vera Sans > > helps, but it would be nice to put in some sanity checks so that we > don't send the ttf file to the afm parser. > > On another note, the dpi setting was used for images. Removing it does > make the code simpler, but then all images will be at a resolution of > 72 dpi. Can you be more specific about the problems that the dpi > setting was causing? Anyway, perhaps we should find a better interface > for specifying image resolution for vectorial backends. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] WXAgg backend updates
Thanks Ken!! > More importantly, I written > another set of the agg-to-wx.Bitmap conversion routines that uses the > new BitmapFromBufferRGBA() function in wxPython 2.8. Are these in Python or c++? > The blit() > routine also got a bit faster after I realized it was more efficient > to just convert the whole buffer and blit part of it instead of > clipping during conversion. really? interesting -- it shows you never know! > I have tested these changes with wxPython 2.8.1.1 under OSX 10.4.8. > My goal is that none of the changes break compatibility with wxPython > 2.4 or 2.6. um, how is that possible if you're using the new 2.8 functions? > I'd really appreciate it if someone could test and > benchmark those versions using `examples/animation_blit_wx.py'. I'll see what I can do. By the way, did you see the weird toolbar behavior with 2.8 on OS-X? -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R(206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] building with python-2.3
I noticed today that setup.py is using package_data. Is this absolutely necessary? The most recent version of Red Hat Enterprise Linux includes python-2.3, which does not support package_data. We are still supporting python-2.3, aren't we? Darren - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] WXAgg backend updates
On Feb 22, 2007, at 1:11 PM, Christopher Barker wrote: > >> More importantly, I written another set of the agg-to-wx.Bitmap >> conversion routines that uses the new BitmapFromBufferRGBA() >> function in wxPython 2.8. > > Are these in Python or c++? Since BitmapFromBuffer() and its aforementioned cousin are covered in the wxWidgets documentation for wxBitmap, I believe they're mostly in C++. >> The blit() >> routine also got a bit faster after I realized it was more efficient >> to just convert the whole buffer and blit part of it instead of >> clipping during conversion. > > really? interesting -- it shows you never know! Yep. Benchmarking is your friend! >> I have tested these changes with wxPython 2.8.1.1 under OSX 10.4.8. >> My goal is that none of the changes break compatibility with wxPython >> 2.4 or 2.6. > > um, how is that possible if you're using the new 2.8 functions? There are two conditional checks based on wx.__version__. One is in setup.py to not build the C++ accelerator for wxPython 2.8. The other is in backend_wxagg.py and figures out which of the three agg/ wx.Bitmap conversion implementations to use -- the pure Python routines, the C++ accelerator, or the wxPython 2.8 edition of the pure Python routines. >> I'd really appreciate it if someone could test and >> benchmark those versions using `examples/animation_blit_wx.py'. > > I'll see what I can do. > > By the way, did you see the weird toolbar behavior with 2.8 on OS-X? It didn't jump out at me, but I wasn't paying much attention. I'll try to reproduce it tomorrow. Ken - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] WXAgg backend updates
Ken McIvor wrote: >> Are these in Python or c++? > > Since BitmapFromBuffer() and its aforementioned cousin are covered in > the wxWidgets documentation for wxBitmap, I believe they're mostly in C++. umm, I meant, is YOUR code in Python or C++, but it looks like you answered that below: >> um, how is that possible if you're using the new 2.8 functions? > > There are two conditional checks based on wx.__version__. One is in > setup.py to not build the C++ accelerator for wxPython 2.8. The other > is in backend_wxagg.py and figures out which of the three agg/wx.Bitmap > conversion implementations to use -- the pure Python routines, the C++ > accelerator, or the wxPython 2.8 edition of the pure Python routines. Ah. I had written some "smarts" for setup.py (and utilities it uses) to do a better job of finding the correct wx-config. Is there any point to that now? If so, I'll sent it along to you. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R(206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] WXAgg backend updates
FYI Christopher, et al. - Due to operator incompetence the changes I blabbed about earlier haven't hit the repository yet. Ken - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] WXAgg backend updates
On Feb 22, 2007, at 5:17 PM, Christopher Barker wrote: > > I had written some "smarts" for setup.py (and utilities it uses) to > do a better job of finding the correct wx-config. Is there any > point to that now? If so, I'll sent it along to you. Debian stable is going to be released soon with wxPython 2.4 and 2.6, so I'd like to keep working to improve the C++ accelerator when practical. Could you send me the changes? Ken - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] building with python-2.3
Darren Dale wrote: > I noticed today that setup.py is using package_data. Is this absolutely > necessary? The most recent version of Red Hat Enterprise Linux includes > python-2.3, which does not support package_data. We are still supporting > python-2.3, aren't we? Yes, I am sure that is the intention. The change to setup.py occurred in revision 3011 as part of the reorganization to support running from a working directory and making eggs, or something like that. Eric - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
