<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel">
    <title>gmane.comp.python.matplotlib.devel</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6121"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6120"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6119"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6118"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6117"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6116"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6115"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6114"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6113"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6112"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6111"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6110"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6109"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6108"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6107"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6106"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6105"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6104"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6103"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6102"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6121">
    <title>Re: reimplemented legend class</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6121</link>
    <description>Thanks John,
I'll work on the revisions.



My original intention with the OffsetBox was to only support the
translation in the display coordinates. VPacker and HPacker even
doesn't use the transformation explicitly. One of the reason for this
was that the size of the Text objects does not depends on the
transformation. I guess in most cases, children will have a fixed
offset relative to their parent container. Introducing an arbitrary
transformation between the child and the parent may make things
complicated. On the other hand, the top most container may have its
own transformation. In the use case I considered (legend), the size of
the box is only known at the drawing time and the offset of the box
needs to be calculated on the fly (e.g., using the size of the box and
the anchor point). The reason that the offset can be a callable object
is to support such situation.
As implementing an optional transformation should be trivial, I'll
just go ahead an work on it. But it seems not clear to me how to
approach</description>
    <dc:creator>Jae-Joon Lee</dc:creator>
    <dc:date>2008-12-02T00:00:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6120">
    <title>Re: reimplemented legend class</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6120</link>
    <description>Hi Jae-Joon and John,

The MPL sizer toolkits looks entirely unaffected by these changes, and
the demo looks very convincing. So from my perspective this would be a
benefit to have in assuming that the issues John raises can be dealt with.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>Andrew Straw</dc:creator>
    <dc:date>2008-12-01T20:03:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6119">
    <title>Re: transforms bug: axhline with log y scale</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6119</link>
    <description>Thanks for the reminder.  It wasn't propagating the "non-affine" 
invalidation correctly.  I think I have a fix in r6465, but please let 
me know if you see anything else funny.

Cheers,
Mike

Eric Firing wrote:

</description>
    <dc:creator>Michael Droettboom</dc:creator>
    <dc:date>2008-12-01T19:35:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6118">
    <title>Re: transforms bug: axhline with log y scale</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6118</link>
    <description>Mike,

This is a gentle check--I suspect my original message, below, may have 
slipped under the radar.

Eric

Eric Firing wrote:


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>Eric Firing</dc:creator>
    <dc:date>2008-12-01T18:19:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6117">
    <title>Re: markersize change</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6117</link>
    <description>Ok.  I'll apply this fix to SVN.  I'll have to go back and find a better 
way to do this later.  Personally, I think the markers at normal to 
largish size (5+ pixels in diameter) look too fuzzy without the pixel 
quantizing.

Mike

Andrew Straw wrote:

</description>
    <dc:creator>Michael Droettboom</dc:creator>
    <dc:date>2008-12-01T15:23:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6116">
    <title>Re: reimplemented legend class</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6116</link>
    <description>

Hi Jae-Joon -- as usual this is great work, and brings one of the
oldest, hairiest, parts of the code into the modern age.  I went ahead
and committed this to svn r6461 with some minor spelling corrections,
but I have some minor comments below which may be worth addressing in
a revision.

Aside from the legend enhancement, the important and general piece
here is the offset box, which  could become a significant piece of the
low-level infrastructure (eg for axes layout)  so I do want to make
sure we get this right.  In particular, I'd like Andrew Straw, who has
a toolkit for sizers, and Michael Droettboom, who implemented the
Knuth boxes in support of mathtext, to take a look at the API and
provide some feedback as to whether if it looks sufficient.

I have some minor comments from the read-thru

+        self.legendPatch = FancyBboxPatch(
+            xy=(0.0, 0.0), width=1., height=1.,
             facecolor='w', edgecolor='k',
+            mutation_scale=self.fontsize,
             )

Should we make this</description>
    <dc:creator>John Hunter</dc:creator>
    <dc:date>2008-12-01T14:53:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6115">
    <title>Re: Debian Bug report logs - #503148</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6115</link>
    <description>Hello!

On Mon, Dec 1, 2008 at 11:24, Manuel Metz &lt;mmetz-U+JqRziUUhd+rGgg2dN5UrNAH6kLmebB&lt; at &gt;public.gmane.org&gt; wrote:

Nah, I can wait for your next release (that is really soon now, isn't it? :) ).

Thanks for the fix,
</description>
    <dc:creator>Sandro Tosi</dc:creator>
    <dc:date>2008-12-01T10:29:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6114">
    <title>Re: Debian Bug report logs - #503148</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6114</link>
    <description>
This if fixed now on the trunk in r6459.

(Sandro, please note: the patch is not applicable to the version 0.98.3
If you need a patch for the Debian package, please let me know).

mm

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>Manuel Metz</dc:creator>
    <dc:date>2008-12-01T10:24:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6113">
    <title>Re: help request: wx, tk, qt backend leave event</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6113</link>
    <description>-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&lt; at &gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
</description>
    <dc:creator>Darren Dale</dc:creator>
    <dc:date>2008-11-30T22:04:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6112">
    <title>Re: any git clones of the MPL svn repo out there?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6112</link>
    <description>I used rsync to mirror the entire SVN repo locally and then using "git
svn clone" to import it (which took about 12 hours on a 2.5 GHz Core 2
machine, even with the local SVN mirror).

I haven't been able to clone the new git repo such that the 2nd git copy
would not need to do "git svn fetch" on the entire repository. Thus, it
seems that putting my git svn mirror in a publicly accessible location
isn't actually going to save anyone the pain of letting git call
subversion a bazillion times to import all history. (At least not
without me understanding things like
http://utsl.gen.nz/talks/git-svn/intro.html#howto-track-rebuildmeta )

I'll plan to use my local git repository to interact with the MPL svn
repo, but I don't plan to publish my git repo unless I figure out how to
set it up so it's actually useful. Until or unless that happens, here's
how I cloned the MPL repo:

# Directories
MPL_RSYNC_DIR="/mnt/workdisk/tmp/matplotlib-svn-rsync"
MPL_GIT_DIR="/mnt/workdisk/tmp/matplotlib"

# Copy the svn repo history</description>
    <dc:creator>Andrew Straw</dc:creator>
    <dc:date>2008-11-30T20:42:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6111">
    <title>Re: markersize change</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6111</link>
    <description>Hi Mike,

That does fix the issue. Another thing I noticed that is fixed with your
patch: the '.' marks appear like '+' when drawn at a smallish size.

Thanks,
Andrew

Michael Droettboom wrote:


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>Andrew Straw</dc:creator>
    <dc:date>2008-11-30T19:42:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6110">
    <title>reimplemented legend class</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6110</link>
    <description>Hello,

I have been working on reimplementation of the legend class, and I
guess it is mostly done. The biggest change is how each items are
placed. For this, I made a simple container class("offsetbox.py"),
which can pack the mpl artists in a similar way as widget packing in
gtk, tk, etc.

 * paddings are given as fraction of the font size.
 * baseline alignment (when supported by backend)
 * multicolumn
 * expand-mode (see the last panel in the attached figure)
 * fancybox for the frame


It should be backward compatible. The backend_driver.py runs fine and
all the examples I checked looks good.
So, here is the patch and example figure. It would be great if others
review and test this patch.

Regards,

-JJ
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
</description>
    <dc:creator>Jae-Joon Lee</dc:creator>
    <dc:date>2008-11-30T17:53:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6109">
    <title>Re: any git clones of the MPL svn repo out there?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6109</link>
    <description>I don't know of any, but if you create one let us know.  I'd be 
interested in playing with such a thing.  I'm ready to see what all the 
fuss is about... ;)

Mike

Andrew Straw wrote:


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>Michael Droettboom</dc:creator>
    <dc:date>2008-11-30T11:55:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6108">
    <title>Re: markersize change</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6108</link>
    <description>This might be related to a change I made in the Agg backend to make the 
markers look better by rounding their coordinates to the nearest pixel.  
It certainly made the stock markers at a standard size look better, but 
I suspect as they get smaller, they are converging down to the same 
value, thus having a truly zero-sized marker.

I'm away from a machine with build tools at the moment, so can't 
confirm.  Does the attached patch work for you?

Mike

Andrew Straw wrote:

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&lt; at &gt;public.gmane.org
https://lists.sourceforge.net/lists/l</description>
    <dc:creator>Michael Droettboom</dc:creator>
    <dc:date>2008-11-30T11:53:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6107">
    <title>Re: markersize change</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6107</link>
    <description>
It doesn't happen with PS or SVG, so I'll say yes.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>Andrew Straw</dc:creator>
    <dc:date>2008-11-30T00:21:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6106">
    <title>Re: markersize change</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6106</link>
    <description>
Is this agg only?

JDH

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>John Hunter</dc:creator>
    <dc:date>2008-11-29T23:29:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6105">
    <title>any git clones of the MPL svn repo out there?</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6105</link>
    <description>Since using git for some time on several projects (including projects
with a central svn repository), it's been hard to go back to the
universally slow web-based subversion history browsers and the absence
of 'git bisect'. Thus, I'm thinking about cloning the MPL SVN history
into a git repo, but I wonder if anyone has already done this? Are there
any git clones of the MPL svn repo out there?

Thanks,
Andrew

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/
</description>
    <dc:creator>Andrew Straw</dc:creator>
    <dc:date>2008-11-29T22:02:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6104">
    <title>markersize change</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6104</link>
    <description>Hi All,

I have been testing the latest svn matplotlib, which failed to produce
any visible data in some long-standing scripts of mine. :(

Investigating further, my use of markersize=0.5 combined with the '.'
symbol and the Agg backend caused a complete disappearance of the
markers. I'm attaching example images from 0.93.3 and the most recent
SVN using the attached script.

I'd be happy to track this down, but I think this might be a no-brainer
for someone on the list.

-Andrew
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK &amp; win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&amp;url=/_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&lt; at &gt;public.gmane.org
https://lists.sourceforge.net/l</description>
    <dc:creator>Andrew Straw</dc:creator>
    <dc:date>2008-11-29T21:55:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6103">
    <title>Re: selection bar widget - new version with showrange and push</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6103</link>
    <description>Hi John,

John Hunter wrote:
Sorry about the new thread. What you wrote makes a lot of sense, so 
thank you for taking the time to write the list rules down. Big thumbs 
up for following this up  John, appreciated! There's no rush though and 
I hope I'm not pressurising any of the devs to answer my problems! Just 
kick me out if that's what you feel :-)
Yes, overlapping ranges will be much easier to visualise with visual 
queues of different thickness. I thought that with an alpha of 0.2, the 
colours would blend, but they don't? anyway, new keyword coming!
This is good! I can also check how this is done with the hlines / vlines 
I'm using for the selector itself, maybe there's some code I can borrow 
in there.
OK, I'll try and explain that again using the my test example, the green 
selector (GS, left) and blue selector (BS, right). The two selectors are 
linked together with barmin and barmax, so that GS can move from 10 to 
BS and BS can move from GS to 60. with the push keyword enabled, a 
selector can p</description>
    <dc:creator>Egor Zindy</dc:creator>
    <dc:date>2008-11-29T10:20:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6102">
    <title>Re: selection bar widget - new version withshowrange and push</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6102</link>
    <description>Hi Egor -- thanks for the update.  For future posts on the same theme,
could you please respond to the existing thread rather than creating a
new one.  This makes it easier for people who are following a thread
to keep following it, and those ignoring it to keep ignoring it.
Importantly, for future generations of googlers and nabblers, it makes
it easier to follow a single conversation.  If you feel like you
earlier post fell on deaf ears because you got no response, its more
likely that we fell behind than that we didn't see it, because all of
us have threaded news readers.  Just "bump" the thread with a polite
and gentle "did anyone have a chance to test this?" rather than
creating a new thread....

Comments on the patch inline below.

On Fri, Nov 28, 2008 at 8:19 AM, Egor Zindy &lt;ezindy-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; wrote:

This is a nice enhancement --  could you also add a keyword arg so
users can customize the min/max of the span.  You've hardcoded
[0.99...1], which may be a little tight for </description>
    <dc:creator>John Hunter</dc:creator>
    <dc:date>2008-11-29T00:54:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6101">
    <title>selection bar widget - new version withshowrange and push</title>
    <link>http://permalink.gmane.org/gmane.comp.python.matplotlib.devel/6101</link>
    <description>A few things I added this time round:
* showrange keyword (as per John's suggestion)
* push keyword

New problems:
* Not sure how to make an axvspan / axhspan span from -inf to value or 
value to +inf.  I use None in my valrange keyword to indicate that but 
using None as an argument in axvspan doesn't help much...
* My push keyword kind of works now (see the example, green line can 
push the blue line) but the implementation is a real mess. I might have 
to rewrite the blitting (I need a background image with none of the bars 
so that I can use that for blitting).

Other problems (in my previous posts) still stand:
* there is a toobar.set_cursor() but no toolbar.get_cursor() which would 
be interesting to have to set the cursor back to what it should be 
(rather than arbitrary POINTER type).
* more cursor types would be nice (could do with size_ver and size_hor 
in 
http://wiki.openusability.org/guidelines/index.php/Design_and_Layout:Visual_Design:Cursors). 

* took a long time to check out matplotlib from </description>
    <dc:creator>Egor Zindy</dc:creator>
    <dc:date>2008-11-28T14:19:05</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.python.matplotlib.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.python.matplotlib.devel</link>
  </textinput>
</rdf:RDF>
