Re: [matplotlib-devel] GTK pylab console
Hi, I've added some basic support for readline shortcuts: Ctrl-A: start of line Ctrl-E: end of line Ctrl-K: kill from cursor to end of line Ctrl-Y: yank kill buffer Ctrl-L: clear console I've also added an option for displaying the toolbar(2). Usage is now: pycons [--ipython] [--pylab] [--toolbar] If the toolbar is not specified, commands can be typed directly within console: zoom(), pan(), home(), back(), forward(), save() There is now a installable package (pycons.tgz) available from: http://www.loria.fr/~rougier/pycons.html Nicolas On Mon, 2008-06-30 at 21:21 -0500, John Hunter wrote: > On Sun, Jun 29, 2008 at 9:28 AM, Nicolas Rougier > <[EMAIL PROTECTED]> wrote: > > > > > > Thanks John, I've update the new version with your code. > > > > It is now available at: > > http://www.loria.fr/~rougier/pylab.html > > > > You can now choose between python and ipython (option -s python > > or -s ipython) and all user events on a figure should be handled > > properly (mouse, scroll and key). > > > > Concerning the toolbar, is is quite easy to add but it is not > > very pleasant to the eyes. I'm looking for a more asethetic solution. > > I've only had a limited chance to test this but it looks very > exciting. I am amazed by how quickly you go the ipython shell > incorporated. I am still a bit vexed by the lack of support for emacs > key bindings (I guess having ipython and readline support are not > enough, but I bet there is some gtk console code out there to support > them). I do miss my CTRL-a and CTRL-k and friends. > > As for the toolbar, I think functionality over aesthetics carries the > day because it is easy to make it pretty after you make it work (and > you can always make it optional with a flag), but note that you do not > need to use the standard gtk toolbar widget -- you can write your own > that works however you want. There is only minimal overhead for the > toolbar writer that is fairly well documented in backend_bases.py. > One option is to draw no toolbar at all but just just set up key > bindings (press 'z' to toggle zoom mode, 'r' to toggle draw to rect > mode, etc, or draw your own toolbar or whatever. But having the > functionality is a killer feature, in my opinion. > > Keep us posted. > > JDH - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] axes_class in add_subplot()?
Sounds ok to me. One thing to clarify though -- what to do if both "projection" and "axes_class" are provided? Throw an exception? I have a small problem with the name "axes_class" because it is very non-obvious that it corresponds to "projection". Perhaps we should either 1) overload projection to take a class as well as strings, or 2) use "projection_class" instead of "axes_class". I think I prefer 1) though I'm wary of overloading in Python in general. Cheers, Mike John Hunter wrote: > On Mon, Jun 30, 2008 at 2:31 PM, Jae-Joon Lee <[EMAIL PROTECTED]> wrote: > > >> It seems rather straight forward to implement "axes_class" keyword in >> add_subplot() and I may make a patch for it. >> So, how does others think? >> > > Seems totally reasonable an we'd be happy to accept a patch. > > Thanks, > JDH > > - > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > ___ > Matplotlib-devel mailing list > Matplotlib-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Latex Documentation build errors - possibly scale_docs
Hi Chris, > I'm using the svn version of the docs on a debian system with > matplotlib 0.98.1 and sphinx 0.4. here the same with 0.91.2 > Latex hangs ( but can be made to continue by pressing return) at the > following point: > > Underfull \hbox (badness 1) in paragraph at lines 17819--17822 > []\T1/txr/m/n/10.95 A dic-tio-nary with key-word ar-gu-ments ac-cepted by the > [181] [182] > Underfull \hbox (badness 1) in paragraph at lines 18251--18254 > [][][]\T1/txtt/m/n/10.95 semilogx()[][] \T1/txr/m/n/10.95 sup-ports all the > key > -word ar-gu-ments of [][]\T1/txtt/m/n/10.95 plot()[][] \T1/txr/m/n/10.95 and > [183] > Overfull \hbox (92.42264pt too wide) in paragraph at lines 18443--18444 > [][] > > Underfull \hbox (badness 1) in paragraph at lines 18458--18461 > [][][]\T1/txtt/m/n/10.95 semilogy()[][] \T1/txr/m/n/10.95 sup-ports all the > key > -word ar-gu-ments of \T1/txtt/m/n/10.95 plot() \T1/txr/m/n/10.95 and > [184] > Overfull \hbox (92.42264pt too wide) in paragraph at lines 18650--18651 > [][] > [185] > Overfull \hbox (92.41579pt too wide) in paragraph at lines 18760--18761 > [][] > [186] > Overfull \hbox (92.45047pt too wide) in paragraph at lines 19150--19151 > [][] > [187] > Overfull \hbox (92.45047pt too wide) in paragraph at lines 19351--19352 > [][] > [188] [189] > > ! LaTeX Error: Too deeply nested. > > See the LaTeX manual or LaTeX Companion for explanation. > Type H for immediate help. > ... > > l.19440 [EMAIL PROTECTED] > > ? I got this fixed with: MATPLOTLIBDATA=../lib/matplotlib/mpl-data/ PYTHONPATH=../build/lib.linux-x86_64-2.5/ ./make.py (discard the PYTHONPATH) in the matplotlib debian trunk. Cheers, Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] GTK pylab console
Hi Nicolas, Your pycons is great! I has to correct a small issue in the tar.gz from your website before being able to test pycons: I had to change: "import gtk_console.console as cons" to "import console as cons" in pycons file around line 12. After that I can report pycons is running on my MacBook (MacOS 10.5) with python, pygtk... from macports. Another point: do you mind releasing your code in a more permissive license that GPL. I mean LGPL or BSD like? I'm interested in including your code in my own LGPL app. Thanks for this great peace of work. All the best, David Nicolas Rougier a écrit : > > Hi, > > I've added some basic support for readline shortcuts: > > Ctrl-A: start of line > Ctrl-E: end of line > Ctrl-K: kill from cursor to end of line > Ctrl-Y: yank kill buffer > Ctrl-L: clear console > > I've also added an option for displaying the toolbar(2). > > Usage is now: > > pycons [--ipython] [--pylab] [--toolbar] > > > If the toolbar is not specified, commands can be typed directly within > console: zoom(), pan(), home(), back(), forward(), save() > > There is now a installable package (pycons.tgz) available from: > > http://www.loria.fr/~rougier/pycons.html > > > > Nicolas > > > > On Mon, 2008-06-30 at 21:21 -0500, John Hunter wrote: >> On Sun, Jun 29, 2008 at 9:28 AM, Nicolas Rougier >> <[EMAIL PROTECTED]> wrote: >>> >>> Thanks John, I've update the new version with your code. >>> >>> It is now available at: >>> http://www.loria.fr/~rougier/pylab.html >>> >>> You can now choose between python and ipython (option -s python >>> or -s ipython) and all user events on a figure should be handled >>> properly (mouse, scroll and key). >>> >>> Concerning the toolbar, is is quite easy to add but it is not >>> very pleasant to the eyes. I'm looking for a more asethetic solution. >> I've only had a limited chance to test this but it looks very >> exciting. I am amazed by how quickly you go the ipython shell >> incorporated. I am still a bit vexed by the lack of support for emacs >> key bindings (I guess having ipython and readline support are not >> enough, but I bet there is some gtk console code out there to support >> them). I do miss my CTRL-a and CTRL-k and friends. >> >> As for the toolbar, I think functionality over aesthetics carries the >> day because it is easy to make it pretty after you make it work (and >> you can always make it optional with a flag), but note that you do not >> need to use the standard gtk toolbar widget -- you can write your own >> that works however you want. There is only minimal overhead for the >> toolbar writer that is fairly well documented in backend_bases.py. >> One option is to draw no toolbar at all but just just set up key >> bindings (press 'z' to toggle zoom mode, 'r' to toggle draw to rect >> mode, etc, or draw your own toolbar or whatever. But having the >> functionality is a killer feature, in my opinion. >> >> Keep us posted. >> >> JDH > > > - > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > ___ > Matplotlib-devel mailing list > Matplotlib-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Latex Documentation build errors - possibly scale_docs
On Tuesday 01 July 2008 08:21:10 am Sandro Tosi wrote: > Hi Chris, > > > I'm using the svn version of the docs on a debian system with > > matplotlib 0.98.1 and sphinx 0.4. > > here the same with 0.91.2 You need to install 0.98.svn to work with the sphinx-based docs. Darren - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Latex Documentation build errors - possibly scale_docs
On Tue, Jul 1, 2008 at 14:42, Darren Dale <[EMAIL PROTECTED]> wrote: > On Tuesday 01 July 2008 08:21:10 am Sandro Tosi wrote: >> Hi Chris, >> >> > I'm using the svn version of the docs on a debian system with >> > matplotlib 0.98.1 and sphinx 0.4. >> >> here the same with 0.91.2 > > You need to install 0.98.svn to work with the sphinx-based docs. Sorry, mistype: I'm using 0.98.2 (the source only release created fro Debian). -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] GTK pylab console
Thanks, I changed the license to a BSD one, hope this is compatible with matplotlib. I also changed the module name from 'gtk_console' to pycons since it makes more sense. I also tried to remove the gtk_console.console (now this is pycons.console) in favor of console but it does not work as expected I would say. In fact, I'm surprised it's working for you. What do you get from a simple "import pycons" ? Nicolas On Tue, 2008-07-01 at 14:32 +0200, David Trem wrote: > Hi Nicolas, > > Your pycons is great! > I has to correct a small issue in the tar.gz from your website before > being able to test pycons: > I had to change: > "import gtk_console.console as cons" > to "import console as cons" > in pycons file around line 12. > > After that I can report pycons is running on my MacBook (MacOS 10.5) > with python, pygtk... from macports. > > Another point: > do you mind releasing your code in a more permissive license that GPL. I > mean LGPL or BSD like? I'm interested in including your code in my own > LGPL app. > > Thanks for this great peace of work. > > All the best, > > David > > Nicolas Rougier a écrit : > > > > Hi, > > > > I've added some basic support for readline shortcuts: > > > > Ctrl-A: start of line > > Ctrl-E: end of line > > Ctrl-K: kill from cursor to end of line > > Ctrl-Y: yank kill buffer > > Ctrl-L: clear console > > > > I've also added an option for displaying the toolbar(2). > > > > Usage is now: > > > > pycons [--ipython] [--pylab] [--toolbar] > > > > > > If the toolbar is not specified, commands can be typed directly within > > console: zoom(), pan(), home(), back(), forward(), save() > > > > There is now a installable package (pycons.tgz) available from: > > > > http://www.loria.fr/~rougier/pycons.html > > > > > > > > Nicolas > > > > > > > > On Mon, 2008-06-30 at 21:21 -0500, John Hunter wrote: > >> On Sun, Jun 29, 2008 at 9:28 AM, Nicolas Rougier > >> <[EMAIL PROTECTED]> wrote: > >>> > >>> Thanks John, I've update the new version with your code. > >>> > >>> It is now available at: > >>> http://www.loria.fr/~rougier/pylab.html > >>> > >>> You can now choose between python and ipython (option -s python > >>> or -s ipython) and all user events on a figure should be handled > >>> properly (mouse, scroll and key). > >>> > >>> Concerning the toolbar, is is quite easy to add but it is not > >>> very pleasant to the eyes. I'm looking for a more asethetic solution. > >> I've only had a limited chance to test this but it looks very > >> exciting. I am amazed by how quickly you go the ipython shell > >> incorporated. I am still a bit vexed by the lack of support for emacs > >> key bindings (I guess having ipython and readline support are not > >> enough, but I bet there is some gtk console code out there to support > >> them). I do miss my CTRL-a and CTRL-k and friends. > >> > >> As for the toolbar, I think functionality over aesthetics carries the > >> day because it is easy to make it pretty after you make it work (and > >> you can always make it optional with a flag), but note that you do not > >> need to use the standard gtk toolbar widget -- you can write your own > >> that works however you want. There is only minimal overhead for the > >> toolbar writer that is fairly well documented in backend_bases.py. > >> One option is to draw no toolbar at all but just just set up key > >> bindings (press 'z' to toggle zoom mode, 'r' to toggle draw to rect > >> mode, etc, or draw your own toolbar or whatever. But having the > >> functionality is a killer feature, in my opinion. > >> > >> Keep us posted. > >> > >> JDH > > > > > > - > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > http://sourceforge.net/services/buy/index.php > > ___ > > Matplotlib-devel mailing list > > Matplotlib-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Latex Documentation build errors - possibly scale_docs
On Tuesday 01 July 2008 08:44:32 am Sandro Tosi wrote: > On Tue, Jul 1, 2008 at 14:42, Darren Dale <[EMAIL PROTECTED]> wrote: > > On Tuesday 01 July 2008 08:21:10 am Sandro Tosi wrote: > >> Hi Chris, > >> > >> > I'm using the svn version of the docs on a debian system with > >> > matplotlib 0.98.1 and sphinx 0.4. > >> > >> here the same with 0.91.2 > > > > You need to install 0.98.svn to work with the sphinx-based docs. > > Sorry, mistype: I'm using 0.98.2 (the source only release created fro > Debian). Looks like John fixed it, latex was successful here. Darren - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] GTK pylab console
Sorry for the trouble, I started testing your "old" pylab wich was provided without the setup script, which led me testing pycons from the pycons folder itself (no setup.py install done). Pycons was actually working fine. However, I encounter problem when closing the console with a graph inside and with the >>>help() command which is freezing the windows... But this is basically usable. Thanks you very much considering my license request! I don't think there could be license issue with matplotlib since it is also using a quite permissive license. Could the matplotlib gurus comment on that? Thanks, David Nicolas Rougier a écrit : > > Thanks, > > I changed the license to a BSD one, hope this is compatible with > matplotlib. I also changed the module name from 'gtk_console' to pycons > since it makes more sense. > > I also tried to remove the gtk_console.console (now this is > pycons.console) in favor of console but it does not work as expected I > would say. In fact, I'm surprised it's working for you. What do you get > from a simple "import pycons" ? > > Nicolas > > > On Tue, 2008-07-01 at 14:32 +0200, David Trem wrote: >> Hi Nicolas, >> >> Your pycons is great! >> I has to correct a small issue in the tar.gz from your website before >> being able to test pycons: >> I had to change: >> "import gtk_console.console as cons" >> to "import console as cons" >> in pycons file around line 12. >> >> After that I can report pycons is running on my MacBook (MacOS 10.5) >> with python, pygtk... from macports. >> >> Another point: >> do you mind releasing your code in a more permissive license that GPL. I >> mean LGPL or BSD like? I'm interested in including your code in my own >> LGPL app. >> >> Thanks for this great peace of work. >> >> All the best, >> >> David >> >> Nicolas Rougier a écrit : >>> Hi, >>> >>> I've added some basic support for readline shortcuts: >>> >>> Ctrl-A: start of line >>> Ctrl-E: end of line >>> Ctrl-K: kill from cursor to end of line >>> Ctrl-Y: yank kill buffer >>> Ctrl-L: clear console >>> >>> I've also added an option for displaying the toolbar(2). >>> >>> Usage is now: >>> >>> pycons [--ipython] [--pylab] [--toolbar] >>> >>> >>> If the toolbar is not specified, commands can be typed directly within >>> console: zoom(), pan(), home(), back(), forward(), save() >>> >>> There is now a installable package (pycons.tgz) available from: >>> >>> http://www.loria.fr/~rougier/pycons.html >>> >>> >>> >>> Nicolas >>> >>> >>> >>> On Mon, 2008-06-30 at 21:21 -0500, John Hunter wrote: On Sun, Jun 29, 2008 at 9:28 AM, Nicolas Rougier <[EMAIL PROTECTED]> wrote: > Thanks John, I've update the new version with your code. > > It is now available at: > http://www.loria.fr/~rougier/pylab.html > > You can now choose between python and ipython (option -s python > or -s ipython) and all user events on a figure should be handled > properly (mouse, scroll and key). > > Concerning the toolbar, is is quite easy to add but it is not > very pleasant to the eyes. I'm looking for a more asethetic solution. I've only had a limited chance to test this but it looks very exciting. I am amazed by how quickly you go the ipython shell incorporated. I am still a bit vexed by the lack of support for emacs key bindings (I guess having ipython and readline support are not enough, but I bet there is some gtk console code out there to support them). I do miss my CTRL-a and CTRL-k and friends. As for the toolbar, I think functionality over aesthetics carries the day because it is easy to make it pretty after you make it work (and you can always make it optional with a flag), but note that you do not need to use the standard gtk toolbar widget -- you can write your own that works however you want. There is only minimal overhead for the toolbar writer that is fairly well documented in backend_bases.py. One option is to draw no toolbar at all but just just set up key bindings (press 'z' to toggle zoom mode, 'r' to toggle draw to rect mode, etc, or draw your own toolbar or whatever. But having the functionality is a killer feature, in my opinion. Keep us posted. JDH >>> >>> - >>> Check out the new SourceForge.net Marketplace. >>> It's the best place to buy or sell services for >>> just about anything Open Source. >>> http://sourceforge.net/services/buy/index.php >>> ___ >>> Matplotlib-devel mailing list >>> Matplotlib-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.ne
Re: [matplotlib-devel] GTK pylab console
On Tue, Jul 1, 2008 at 5:31 AM, Nicolas Rougier <[EMAIL PROTECTED]> wrote: > There is now a installable package (pycons.tgz) available from: > > http://www.loria.fr/~rougier/pycons.html Cool, this is working for me now. Very nice. Two more comments: You must override draw_if_interactive *before* importing pylab: import matplotlib.backends.backend_gtkagg as backend_gtkagg def draw_if_interactive(): """ Is called after every pylab drawing command """ show(console) # do this before importing pylab backend_gtkagg.draw_if_interactive = draw_if_interactive import pylab import matplotlib.pylab from matplotlib._pylab_helpers import Gcf and when I run in --pylab mode, the pylab namespace is not imported. I have to manually 'from pylab import *' . Is that intentional? - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] GTK pylab console
On Tue, Jul 1, 2008 at 8:37 AM, David Trem <[EMAIL PROTECTED]> wrote: > Thanks you very much considering my license request! > I don't think there could be license issue with matplotlib since it is > also using a quite permissive license. Could the matplotlib gurus > comment on that? Yes, the BSD license is compatible with mpl, the GPL one was not. Thanks for changing it Nicolas. JDH - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] GTK pylab console
On Tue, Jul 1, 2008 at 6:01 AM, Nicolas Rougier <[EMAIL PROTECTED]> wrote: > > > Thanks, > > I changed the license to a BSD one, hope this is compatible with > matplotlib. I also changed the module name from 'gtk_console' to pycons > since it makes more sense. Beautiful work, and many thanks for the license change too, since it's now comatible with ipython as well. BTW, are you on the ipython-dev list? If not, I'd like to encourage you to join in. Right now we're in the middle of refactoring the ipython code and we have people working on WX, Qt and Cocoa consoles, with a proper architecture (backend/frontend separation). I think it would be great if your GTK one also made it into the same codebase, so that your console could 'ride' on top of the common layer that all others will share. Minor note: you may want to initialize the ipython session with --colors LightBG since you have a light background, so we get better readability. Cheers, f - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] axes_class in add_subplot()?
I picked "axes_class" because this is what is used in
"subplot_class_factory" function.
I rather prefer "axes_class" because, IMO, subclassing of Axes is not
only for a new projection.
For example, I have a simple subclass of Axes where I have
"baseline"-aligned x-ticklabels (instead of "top" align). Also, from
available options
from matplotlib.projection import AitoffAxes
1) f.add_subplot(1,2,1, projection=AitoffAxes)
2) f.add_subplot(1,2,1, projection_class=AitoffAxes)
3) f.add_subplot(1,2,1, axes_class=AitoffAxes)
I think option 3 makes a slightly more sense.
My patch (which is attached) if for option 3 and simply adds
"axes_class" keyword. It raises an Exception if "projection" is
supplied or polar=True. But feel free to modify or give me
suggestions. If others prefer option 1 or 2, I'll make a subsequent
change for it.
Regards,
-JJ
On Tue, Jul 1, 2008 at 7:51 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Sounds ok to me. One thing to clarify though -- what to do if both
> "projection" and "axes_class" are provided? Throw an exception?
>
> I have a small problem with the name "axes_class" because it is very
> non-obvious that it corresponds to "projection". Perhaps we should either
> 1) overload projection to take a class as well as strings, or 2) use
> "projection_class" instead of "axes_class". I think I prefer 1) though I'm
> wary of overloading in Python in general.
>
> Cheers,
> Mike
>
> John Hunter wrote:
>>
>> On Mon, Jun 30, 2008 at 2:31 PM, Jae-Joon Lee <[EMAIL PROTECTED]>
>> wrote:
>>
>>
>>>
>>> It seems rather straight forward to implement "axes_class" keyword in
>>> add_subplot() and I may make a patch for it.
>>> So, how does others think?
>>>
>>
>> Seems totally reasonable an we'd be happy to accept a patch.
>>
>> Thanks,
>> JDH
>>
>> -
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> ___
>> Matplotlib-devel mailing list
>> Matplotlib-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>
> --
> Michael Droettboom
> Science Software Branch
> Operations and Engineering Division
> Space Telescope Science Institute
> Operated by AURA for NASA
>
>
Index: figure.py
===
--- figure.py (revision 5704)
+++ figure.py (working copy)
@@ -716,12 +716,15 @@
fig.add_subplot(111, polar=True) # add a polar subplot
fig.add_subplot(sub) # add Subplot instance sub
-*kwargs* are legal :class:`!matplotlib.axes.Axes` kwargs plus *projection*, which chooses
+*kwargs* are legal :class:`!matplotlib.axes.Axes` kwargs plus *projection*
+and *axes_class*. *projection* chooses
a projection type for the axes. (For backward compatibility,
*polar=True* may also be provided, which is equivalent to
*projection='polar'*). Valid values for *projection* are: %s.
Some of these projections support additional *kwargs*, which may
-be provided to :meth:`add_axes`.
+be provided to :meth:`add_axes`. When *axes_class* is provided (which
+should be a subclass of :class:`!matplotlib.axes.Axes`), the axes of the
+subplot will be created with *axes_class*.
The :class:`~matplotlib.axes.Axes` instance will be returned.
@@ -747,17 +750,29 @@
else:
ispolar = kwargs.pop('polar', False)
projection = kwargs.pop('projection', None)
-if ispolar:
-if projection is not None and projection != 'polar':
+axes_class = kwargs.pop('axes_class', None)
+
+
+if axes_class:
+if projection is not None or ispolar:
raise ValueError(
-"polar=True, yet projection='%s'. " +
-"Only one of these arguments should be supplied." %
-projection)
-projection = 'polar'
+"polar or projection keyword should not be supplied "
+"when axes_class is used.")
+a = subplot_class_factory(axes_class)(self, *args, **kwargs)
-projection_class = get_projection_class(projection)
-a = subplot_class_factory(projection_class)(self, *args, **kwargs)
+else:
+if ispolar:
+if projection is not None and projection != 'polar':
+raise ValueError(
+"polar=True, yet projection='%s'. " +
+"Only one of these arguments should be supplied." %
+projection)
+projection = 'polar'
+project
Re: [matplotlib-devel] GTK pylab console
Thanks, corrected. I just forgot the pylab import, it has been corrected as well. Nicolas On Tue, 2008-07-01 at 08:38 -0500, John Hunter wrote: > On Tue, Jul 1, 2008 at 5:31 AM, Nicolas Rougier > <[EMAIL PROTECTED]> wrote: > > > There is now a installable package (pycons.tgz) available from: > > > > http://www.loria.fr/~rougier/pycons.html > > Cool, this is working for me now. Very nice. Two more comments: > > You must override draw_if_interactive *before* importing pylab: > > import matplotlib.backends.backend_gtkagg as backend_gtkagg > > def draw_if_interactive(): > """ Is called after every pylab drawing command """ > show(console) > # do this before importing pylab > backend_gtkagg.draw_if_interactive = draw_if_interactive > import pylab > import matplotlib.pylab > from matplotlib._pylab_helpers import Gcf > > > and when I run in --pylab mode, the pylab namespace is not imported. > I have to manually 'from pylab import *' . Is that intentional? - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] GTK pylab console
The "help()" freeze is not really a freeze since you can type input within the terminal from where you started pycons. I managed to find that the IPython import was responsible for this behavior for some unknown reason. If you remove all reference to IPython in the pycons file, then you got the expected behavior. Since IPython is under heavy redesign, I won't investigate further until the next version. What is the problem when closing with a graph inside ? Nicolas On Tue, 2008-07-01 at 15:37 +0200, David Trem wrote: > Sorry for the trouble, I started testing your "old" pylab wich was > provided without the setup script, which led me testing pycons from the > pycons folder itself (no setup.py install done). > Pycons was actually working fine. > However, I encounter problem when closing the console with a graph > inside and with the >>>help() command which is freezing the windows... > But this is basically usable. > > Thanks you very much considering my license request! > I don't think there could be license issue with matplotlib since it is > also using a quite permissive license. Could the matplotlib gurus > comment on that? > > Thanks, > > David > > Nicolas Rougier a écrit : > > > > Thanks, > > > > I changed the license to a BSD one, hope this is compatible with > > matplotlib. I also changed the module name from 'gtk_console' to pycons > > since it makes more sense. > > > > I also tried to remove the gtk_console.console (now this is > > pycons.console) in favor of console but it does not work as expected I > > would say. In fact, I'm surprised it's working for you. What do you get > > from a simple "import pycons" ? > > > > Nicolas > > > > > > On Tue, 2008-07-01 at 14:32 +0200, David Trem wrote: > >> Hi Nicolas, > >> > >> Your pycons is great! > >> I has to correct a small issue in the tar.gz from your website before > >> being able to test pycons: > >> I had to change: > >> "import gtk_console.console as cons" > >> to "import console as cons" > >> in pycons file around line 12. > >> > >> After that I can report pycons is running on my MacBook (MacOS 10.5) > >> with python, pygtk... from macports. > >> > >> Another point: > >> do you mind releasing your code in a more permissive license that GPL. I > >> mean LGPL or BSD like? I'm interested in including your code in my own > >> LGPL app. > >> > >> Thanks for this great peace of work. > >> > >> All the best, > >> > >> David > >> > >> Nicolas Rougier a écrit : > >>> Hi, > >>> > >>> I've added some basic support for readline shortcuts: > >>> > >>> Ctrl-A: start of line > >>> Ctrl-E: end of line > >>> Ctrl-K: kill from cursor to end of line > >>> Ctrl-Y: yank kill buffer > >>> Ctrl-L: clear console > >>> > >>> I've also added an option for displaying the toolbar(2). > >>> > >>> Usage is now: > >>> > >>> pycons [--ipython] [--pylab] [--toolbar] > >>> > >>> > >>> If the toolbar is not specified, commands can be typed directly within > >>> console: zoom(), pan(), home(), back(), forward(), save() > >>> > >>> There is now a installable package (pycons.tgz) available from: > >>> > >>> http://www.loria.fr/~rougier/pycons.html > >>> > >>> > >>> > >>> Nicolas > >>> > >>> > >>> > >>> On Mon, 2008-06-30 at 21:21 -0500, John Hunter wrote: > On Sun, Jun 29, 2008 at 9:28 AM, Nicolas Rougier > <[EMAIL PROTECTED]> wrote: > > Thanks John, I've update the new version with your code. > > > > It is now available at: > > http://www.loria.fr/~rougier/pylab.html > > > > You can now choose between python and ipython (option -s python > > or -s ipython) and all user events on a figure should be handled > > properly (mouse, scroll and key). > > > > Concerning the toolbar, is is quite easy to add but it is not > > very pleasant to the eyes. I'm looking for a more asethetic solution. > I've only had a limited chance to test this but it looks very > exciting. I am amazed by how quickly you go the ipython shell > incorporated. I am still a bit vexed by the lack of support for emacs > key bindings (I guess having ipython and readline support are not > enough, but I bet there is some gtk console code out there to support > them). I do miss my CTRL-a and CTRL-k and friends. > > As for the toolbar, I think functionality over aesthetics carries the > day because it is easy to make it pretty after you make it work (and > you can always make it optional with a flag), but note that you do not > need to use the standard gtk toolbar widget -- you can write your own > that works however you want. There is only minimal overhead for the > toolbar writer that is fairly well documented in backend_bases.py. > One option is to draw no toolbar at all but just just set up key > bindings (press 'z' to toggle zoom mode, 'r' to toggle draw to rect > mode, etc, or draw your own toolbar or whatever. But having the > functionality is
Re: [matplotlib-devel] GTK pylab console
I'm not yet on the ipython-dev but I read the archive to check progress on ipython1 and I get a bit lost with the redesign. The backend/frontend will definitely help to embed ipython. Where can I get the latest version (with wx for example) so I can try to code the GTK one ? Concerning the colors options, I'm not sure where to put it, in the argv argument ? Cheers. Nicolas On Tue, 2008-07-01 at 12:22 -0700, Fernando Perez wrote: > On Tue, Jul 1, 2008 at 6:01 AM, Nicolas Rougier > <[EMAIL PROTECTED]> wrote: > > > > > > Thanks, > > > > I changed the license to a BSD one, hope this is compatible with > > matplotlib. I also changed the module name from 'gtk_console' to pycons > > since it makes more sense. > > Beautiful work, and many thanks for the license change too, since it's > now comatible with ipython as well. > > BTW, are you on the ipython-dev list? If not, I'd like to encourage > you to join in. Right now we're in the middle of refactoring the > ipython code and we have people working on WX, Qt and Cocoa consoles, > with a proper architecture (backend/frontend separation). I think it > would be great if your GTK one also made it into the same codebase, so > that your console could 'ride' on top of the common layer that all > others will share. > > Minor note: you may want to initialize the ipython session with > --colors LightBG since you have a light background, so we get better > readability. > > Cheers, > > f - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] GTK pylab console
On Tue, Jul 1, 2008 at 1:34 PM, Nicolas Rougier
<[EMAIL PROTECTED]> wrote:
>
> I'm not yet on the ipython-dev but I read the archive to check progress
> on ipython1 and I get a bit lost with the redesign. The backend/frontend
> will definitely help to embed ipython. Where can I get the latest
> version (with wx for example) so I can try to code the GTK one ?
All development for ipython now happens on launchpad, so you can just
bzr branch lp:iptyhon
as indicated here:
http://ipython.scipy.org/moin/Developer_Zone
The various GUI frontends are just being built, so there isn't a
single component to download yet. But feel free to jump on the list
with questions (and show your code!) I'm sure there will be plenty of
interest.
>
> Concerning the colors options, I'm not sure where to put it, in the argv
> argument ?
You can do that, but here's a cleaner solution that uses the actual ipython api:
tlon[pycons]> diff -u ishell.py.ori ishell.py
--- ishell.py.ori 2008-07-01 15:25:01.0 -0700
+++ ishell.py 2008-07-01 15:33:46.0 -0700
@@ -19,6 +19,7 @@
from StringIO import StringIO
try:
import IPython
+from IPython import ipapi
except Exception,e:
raise "Error importing IPython (%s)" % str(e)
@@ -52,6 +53,11 @@
self.IP.system = lambda cmd: self.shell(self.IP.var_expand(cmd),
header='IPython system call: ',
verbose=self.IP.rc.system_verbose)
+
+# Get a hold of the public IPython API object and use it
+self.ip = ipapi.get()
+self.ip.magic('colors LightBG')
+
sys.excepthook = excepthook
self.iter_more = 0
self.complete_sep = re.compile('[\s\{\}\[\]\(\)]')
# END PATCH
Cheers,
f
-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
