matplotlib-devel Mailing List for matplotlib

My fear is that all these native implementations will become very hard
to maintain. What happens when Qt 4.2 comes out and the person who
did the original Qt impl is long gone? (this is just for arguments
sake of course). Native tools seem better left to developers creating
their own apps. The typical user probably won't care if the laf is
native, just whether it works consistently.
On 8/7/06, Mark Bakker <ma...@gm...> wrote:
> Darren -
>
> Although I agree with your on some level, the advantage of the current
> toolbar is that it is easy to incorporate in a GUI, where the user can
> define his own drop down menu. So I vote for a backend native slider, but
> keep the button on the toolbar.
>
> I have been thinking about an easier way to have user-defined toolbars (and
> I am sure others have much better ideas). I would rather put energy towards
> modifyable toolbars than a dropdown menu,
>
> Mark
>
> > ------------------------------
> >
> > Message: 4
> > Date: Mon, 7 Aug 2006 09:34:57 -0400
> > From: Darren Dale <dd...@co...>
> > Subject: [matplotlib-devel] subplots adjust
> > To: mat...@li...
> > Message-ID: <200...@co...>
> > Content-Type: text/plain; charset="us-ascii"
> >
> > I am writing to ask about the subplots adjust widget. I think the gui
> would be
> > better implimented by each backend using the native widgets rather than by
> > the existing set of backend-neutral sliders, which are somewhat
> unbecoming.
> > The proposed backend-specific widgets could call the generic subplot
> resize
> > routines, and really shouldn't be that difficult to impliment. Also, I was
> > thinking that subplot_adjust should be selectable from a standard
> > dropdown "File, Edit, View..." menubar instead of on the main toolbar. The
> > save button could also be moved to the drop down menu bar.
> >
> > Darren
> >
> >
> >
> > ------------------------------
> >
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>

Hey, glad it might actually be of use to other people. I know I've 
been awful about finishing things, as anything that doesn't directly 
relate to my thesis has fallen to wayside as of late. When I was 
investigating saving it as an XML format, I remember coming across a 
problem. If I remember correctly, you could easily write a backend 
that would just spit out the proper XML, but it wouldn't be a very 
good XML file -- it would just be a collection of 'draw_lines', etc.. 
The current format that I've been using looks more like:
<pylab>
<figure name="foo">
<axes pos="1,1">
	<plot name="bar">
		<params name="a" value="10.5" type="float"/>
		<params name="b" value="baz" type="str"/>
	</plot>
</axes>
<axes pos="1,2">
	<plot name="bar">
		<params name="a" value="0.53" type="float"/>
		<params name="b" value="zab" type="str"/>
</axes>
</figure>
</pylab>
It has a plug-in architecture, so it looks for all python files in a 
specified directory, and that is how it decides which plot function 
to call (in this case, it would find a class 'bar' within those 
files). The class specifies what arguments it can take, which are 
required arguments, and which are optional (as well as default values).
What made sense to me, would be to simply create plot classes that 
corresponded with the draw_line, draw_arc, etc. That way, to render a 
saved XML file, would simply consist of having those classes make the 
correct backend calls. But, there doesn't seem an easy way to 
generate this with the backends, as they know nothing about figures, 
axes, subplot, etc.
So it seems like matplotlib would have to have a separate way for 
saving a native format. I think this would be a huge gain, as it 
would allow figures to be generated, saved, edited, reopened/ 
regenerated, but would involve yet another output method.
I could very well be missing something obvious, if so please correct me!
As for the SVG, I'll have to look into it. I think that's probably an 
easier issue, as I believe you could construct it in a similiar 
fashion to the other backends, as a collection of lines.
Abe
On Aug 7, 2006, at 4:14 PM, Andrew Straw wrote:
> Dear Abraham,
>
> I'm sorry it's taken so long to get back to you. I didn't see any 
> other
> responses on the list, but I think this is a super idea (although I 
> have
> yet to look at the code). In particular I like your idea to save to 
> your
> XML format. Then we could plot to an XML file, and replot (later) with
> whatever backend we need at the time. It sounds great. We could 
> even zip
> the file automatically (or just the data parts of the innards) so 
> they'd
> hopefully be pretty small.
>
> I suspect that if you get the XML backend working and incorporate it,
> you'll have a lot of users trying it out when they see it in their 
> "save
> as" format list.
>
> Relatedly, is there any way would could add to the SVG backend that
> would give us essentially this and, simultaneously, a valid SVG 
> file? Is
> SVG even "officially" extensible in this way? (I don't know much about
> SVG or XML.)
>
> Cheers!
> Andrew
>
> Abraham Schneider wrote:
>> Hi. A long while ago I had sent out an email asking if anyone was
>> interested in an XML library for plotting with matplotlib. It seemed
>> the general consensus was no, though it might be nice as a backend 
>> for
>> saving files. So I developed the XML library for my own purposes, and
>> have been using it for some time.
>>
>> I thought I might as well clean it up, package it, and release it in
>> the wild. I'm not sure if this would even qualify as an alpha 
>> release,
>> perhaps more of a RFC, but if anyone is interested, and wants to give
>> some comments, let me know. While it has gotten a good amount of use
>> (including a soon to be published paper), it has evolved to fit my
>> needs more than anything else. So in the clean up, I tried to
>> refractor some saneness into it, and had to fix some things in the
>> process. I tried to test as much of it as possible, but I'm sure I
>> forgot some obvious things as well.
>>
>> It is trying to serve 3 purposes:
>> (1) Framework for making publishable figures easy
>> (2) Provide an easy way to allow pylab figures to be saveable/ 
>> loadable
>> and editable by human
>> (3) Provide a general framework for a higher level plotting library
>>
>> I'm hoping to in the near future write the backend to pylab to 
>> save in
>> the XML format. It should (hopefully) be fairly trivial..
>>
>> It can be found (this includes some documentation and examples):
>> www.cns.nyu.edu/~abes/xmlplot.tar.gz
>>
>> Thanks,
>>
>> Abe
>>
>>
>> -------------------------------------------------------
>> Using Tomcat but need to do more? Need to support web services, 
>> security?
>> Get stuff done quickly with pre-integrated technology to make your 
>> job
>> easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache
>> Geronimo
>> http://sel.as-us.falkag.net/sel? 
>> cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
> ---------------------------------------------------------------------- 
> ---
> Using Tomcat but need to do more? Need to support web services, 
> security?
> Get stuff done quickly with pre-integrated technology to make your 
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
> Geronimo
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Dear Abraham,
I'm sorry it's taken so long to get back to you. I didn't see any other
responses on the list, but I think this is a super idea (although I have
yet to look at the code). In particular I like your idea to save to your
XML format. Then we could plot to an XML file, and replot (later) with
whatever backend we need at the time. It sounds great. We could even zip
the file automatically (or just the data parts of the innards) so they'd
hopefully be pretty small.
I suspect that if you get the XML backend working and incorporate it,
you'll have a lot of users trying it out when they see it in their "save
as" format list.
Relatedly, is there any way would could add to the SVG backend that
would give us essentially this and, simultaneously, a valid SVG file? Is
SVG even "officially" extensible in this way? (I don't know much about
SVG or XML.)
Cheers!
Andrew
Abraham Schneider wrote:
> Hi. A long while ago I had sent out an email asking if anyone was
> interested in an XML library for plotting with matplotlib. It seemed
> the general consensus was no, though it might be nice as a backend for
> saving files. So I developed the XML library for my own purposes, and
> have been using it for some time.
>
> I thought I might as well clean it up, package it, and release it in
> the wild. I'm not sure if this would even qualify as an alpha release,
> perhaps more of a RFC, but if anyone is interested, and wants to give
> some comments, let me know. While it has gotten a good amount of use
> (including a soon to be published paper), it has evolved to fit my
> needs more than anything else. So in the clean up, I tried to
> refractor some saneness into it, and had to fix some things in the
> process. I tried to test as much of it as possible, but I'm sure I
> forgot some obvious things as well.
>
> It is trying to serve 3 purposes:
> (1) Framework for making publishable figures easy
> (2) Provide an easy way to allow pylab figures to be saveable/loadable
> and editable by human
> (3) Provide a general framework for a higher level plotting library
>
> I'm hoping to in the near future write the backend to pylab to save in
> the XML format. It should (hopefully) be fairly trivial..
>
> It can be found (this includes some documentation and examples):
> www.cns.nyu.edu/~abes/xmlplot.tar.gz
>
> Thanks,
>
> Abe
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Darren -
Although I agree with your on some level, the advantage of the current
toolbar is that it is easy to incorporate in a GUI, where the user can
define his own drop down menu. So I vote for a backend native slider, but
keep the button on the toolbar.
I have been thinking about an easier way to have user-defined toolbars (and
I am sure others have much better ideas). I would rather put energy towards
modifyable toolbars than a dropdown menu,
Mark
> ------------------------------
>
> Message: 4
> Date: Mon, 7 Aug 2006 09:34:57 -0400
> From: Darren Dale <dd...@co...>
> Subject: [matplotlib-devel] subplots adjust
> To: mat...@li...
> Message-ID: <200...@co...>
> Content-Type: text/plain; charset="us-ascii"
>
> I am writing to ask about the subplots adjust widget. I think the gui
> would be
> better implimented by each backend using the native widgets rather than by
> the existing set of backend-neutral sliders, which are somewhat
> unbecoming.
> The proposed backend-specific widgets could call the generic subplot
> resize
> routines, and really shouldn't be that difficult to impliment. Also, I was
> thinking that subplot_adjust should be selectable from a standard
> dropdown "File, Edit, View..." menubar instead of on the main toolbar. The
> save button could also be moved to the drop down menu bar.
>
> Darren
>
>
>
> ------------------------------
>

>>>>> "Charlie" == Charlie Moad <cw...@gm...> writes:
 Charlie> Are they any lingering issues that would prevent a
 Charlie> Wednesday minor rev bump for the latest numpy? Ideally
 Charlie> it would last through the numpy 1.0 release.
Since scipy is next week, we should concentrate on getting a release
out that works with whatever numpy/scipy Travis is targeting for the
scipy conference.
JDH

On 8/7/06, Christopher Barker <Chr...@no...> wrote:
> Darren Dale wrote:
> > On Monday 07 August 2006 08:55, Charlie Moad wrote:
> > Pushing a
> >> release now for 1.0 might be pointless, since the C-api could possibly
> >> change and break compatibility again. After all, it still is a beta.
>
> > I wonder how long we should continue to hold off on a new release. As I said
> > in a previous email, Travis does not foresee changes to the C API before
> > numpy-1.1 (although he doesn't rule them out). Besides, several bug fixes and
> > new features have been added since 0.87.4.
>
> Isn't the "current" version using numpy 0.9.8? No matter, they are ALL
> beta, (or alpha), so there is no reason to stick with any particular one.
>
> 1.0b seems to be the least buggy and most future-proof (which, of
> course, doesn't mean that much) at the moment, so I say we do it.
>
> Charlie, can you do OS-X? I still don't have my build environment set up
> quite right, and you beat me to it last time. We'll need to put a new
> numpy mpkg on pythonmac.org at the same time. I'd be glad to do that, if
> it helps, but I need to make sure we use the same version.
Are they any lingering issues that would prevent a Wednesday minor rev
bump for the latest numpy? Ideally it would last through the numpy
1.0 release.
- Charlie

Eric Firing wrote:
> I think the following (now in svn) should be OK; it seems to work on 
> Windows, at least in the sense that it doesn't trigger an exception.
> 
> nan = struct.unpack('d', struct.pack('Q', 0x7ff8000000000000))[0]
It works on OS-X PPC also. I was wondering about endian issues.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

I am writing to ask about the subplots adjust widget. I think the gui would be 
better implimented by each backend using the native widgets rather than by 
the existing set of backend-neutral sliders, which are somewhat unbecoming. 
The proposed backend-specific widgets could call the generic subplot resize 
routines, and really shouldn't be that difficult to impliment. Also, I was 
thinking that subplot_adjust should be selectable from a standard 
dropdown "File, Edit, View..." menubar instead of on the main toolbar. The 
save button could also be moved to the drop down menu bar.
Darren

Robert Kern wrote:
> Eric Firing wrote:
> 
>> I added nan definitions for
>>Numeric and numarray which work on my linux box, but I have not tested 
>>them on other platforms; I guess in the worst case, if it doesn't work 
>>on Mac or Windows I will have to change quiver.py to use masked arrays 
>>internally instead of nans. (The definition I used is "nan = 
>>float('nan')".)
> 
> 
> That will certainly not work on Windows.
> 
Thanks for the quick info.
I think the following (now in svn) should be OK; it seems to work on 
Windows, at least in the sense that it doesn't trigger an exception.
nan = struct.unpack('d', struct.pack('Q', 0x7ff8000000000000))[0]
Eric