matplotlib-devel Mailing List for matplotlib

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

FYI Christopher, et al. - Due to operator incompetence the changes I 
blabbed about earlier haven't hit the repository yet.
Ken

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
Chr...@no...

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

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

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
Chr...@no...

T24gMi8yMS8wNywgSm91bmkgSy4gU2VwcMOkbmVuIDxqa3NAaWtpLmZpPiB3cm90ZToKPiA+IEhh
dmUgeW91IGhhZCB0aW1lIHRvIGxvb2sgYXQgbXkgcGF0Y2ggcmVnYXJkaW5nIHRoZSBQREYgYmFj
a2VuZD8gOi0pCj4KPiBBIGJpdCwgYW5kIEkgY291bGRuJ3QgcXVpdGUgZ2V0IGl0IHRvIHdvcmsu
IEJ1dCB3aGF0IHRoZSBoZWNrLCBsZXQncwo+IHB1dCBpdCBpbiB0aGUgcmVwb3NpdG9yeSBzbyB3
ZSBjYW4gYWxsIGhhY2sgb24gaXQuIEl0IGlzIHF1aXRlIGFuCj4gaW1wcm92ZW1lbnQgdG8gdGhl
IGJhY2tlbmQsIGFuZCBpdCBkb2Vzbid0IHNlZW0gdG8gYnJlYWsgYW55dGhpbmcgdGhhdAo+IHVz
ZWQgdG8gd29yay4gKEkgcmFuIHRoZSBleGFtcGxlcyB1c2luZyBiYWNrZW5kX2RyaXZlci5weSBv
biBib3RoIGFnZwo+IGFuZCBwZGYuKSBZb3VyIHBhdGNoIChzbGlnaHRseSBtb2RpZmllZCkgaXMg
Y29tbWl0dGVkIGFzIG9mIHN2bgo+IHJldmlzaW9uIDMwMjcuCgpUaGFua3MgSm91bmkgZm9yIGNv
bW1pdHRpbmcgdGhpcyBwYXRjaC4KCk5vdywgSSdtIHdvcmtpbmcgb24gdGhlIHR3byBpc3N1ZXMg
eW91J3ZlIG1lbnRpb25lZCBiZWxvdy4gSSdsbApwcm9iYWJseSBzZW5kIGEgbmV3IHBhdGNoIGZp
eGluZyB0aGUgZm9udCBpc3N1ZSBpbiB0aGUgbmV4dCBmZXcgZGF5cy4KCj4gVGhlIHByb2JsZW0g
SSdtIGhhdmluZyBpcyB0aGF0IGlmIEkgc2V0IHVzZTE0Y29yZWZvbnRzIG9uLCBJIGhhdmUgdG8K
PiBtYWtlIHN1cmUgdGhhdCBIZWx2ZXRpY2EgKG9yIHdoYXRldmVyKSBpcyBjaG9zZW4gYXMgdGhl
IHRleHQgZm9udC4KPiBJIHVzZWQgdG8gaGF2ZSB0aGUgc2V0dGluZwo+Cj4gZm9udC5zYW5zLXNl
cmlmICAgICA6IEJpdHN0cmVhbSBWZXJhIFNhbnMKPgo+IGJlY2F1c2UgdGhhdCBmb250IHdvcmtz
LCBhbmQgc29tZSBvdGhlciBmb250cyB0aGF0IG1wbCBmaW5kcyAob24gbXkKPiBPUyBYIHN5c3Rl
bSkgZG9uJ3Q7IGJ1dCB0aGVuIHNldHRpbmcgdXNlMTRjb3JlZm9udHMgb24gY2F1c2VkIHRoZSBh
Zm0KPiBoZWFkZXIgcGFyc2VyIHRvIGJlIGNhbGxlZCBvbiBWZXJhLnR0Ziwgd2hpY2ggaXQgb2J2
aW91c2x5IGNvdWxkbid0Cj4gbWFrZSBhbnkgc2Vuc2Ugb2YuIEknbSBub3Qgc3VyZSBJIHF1aXRl
IHVuZGVyc3RhbmQgdGhlIE1hdHBsb3RsaWIgZm9udAo+IHNlbGVjdGlvbiBzeXN0ZW0sIHRob3Vn
aC4KPgo+IFJlcGxhY2luZyB0aGUgc2V0dGluZyBieQo+Cj4gZm9udC5zYW5zLXNlcmlmICAgICA6
IEhlbHZldGljYSwgQml0c3RyZWFtIFZlcmEgU2Fucwo+Cj4gaGVscHMsIGJ1dCBpdCB3b3VsZCBi
ZSBuaWNlIHRvIHB1dCBpbiBzb21lIHNhbml0eSBjaGVja3Mgc28gdGhhdCB3ZQo+IGRvbid0IHNl
bmQgdGhlIHR0ZiBmaWxlIHRvIHRoZSBhZm0gcGFyc2VyLgo+Cj4gT24gYW5vdGhlciBub3RlLCB0
aGUgZHBpIHNldHRpbmcgd2FzIHVzZWQgZm9yIGltYWdlcy4gUmVtb3ZpbmcgaXQgZG9lcwo+IG1h
a2UgdGhlIGNvZGUgc2ltcGxlciwgYnV0IHRoZW4gYWxsIGltYWdlcyB3aWxsIGJlIGF0IGEgcmVz
b2x1dGlvbiBvZgo+IDcyIGRwaS4gQ2FuIHlvdSBiZSBtb3JlIHNwZWNpZmljIGFib3V0IHRoZSBw
cm9ibGVtcyB0aGF0IHRoZSBkcGkKPiBzZXR0aW5nIHdhcyBjYXVzaW5nPyBBbnl3YXksIHBlcmhh
cHMgd2Ugc2hvdWxkIGZpbmQgYSBiZXR0ZXIgaW50ZXJmYWNlCj4gZm9yIHNwZWNpZnlpbmcgaW1h
Z2UgcmVzb2x1dGlvbiBmb3IgdmVjdG9yaWFsIGJhY2tlbmRzLgo=

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