matplotlib-users Mailing List for matplotlib

>>>>> "James" == James Boyle <bo...@ll...> writes:
 James> To reply to my own post: On question (1): I modified the
 James> call to colorbar in pylab.py to accept a color map and norm
 James> keyword arguments. It was this functionality that was
Perhaps it would be cleaner simply to derive a custom class from
ScalarMappable that does your fill calls and stores your cmap and norm
instances; then you would get the observer stuff for free. If you
decide to go this route, perhaps you could submit the example.
 James> I would also like to code up a floating color bar. Often I
 James> make 4/5 images per page with a common colormap and
 James> normalization. It is handy just to plop the reference
 James> colorbar in a central location not attached to a particular
 James> figure.
I just committed changes to CVS to support this -- you can now place a
colorbar in a custom axes, and I added an orientation kwarg to
support horizontal or vertical colorbar layout. Make sure you get
pylab.py revision 1.21 or later.
Here is an example
from pylab import *
ax = axes([0.1, 0.3, 0.8, 0.6])
im = imshow(rand(12,12), interpolation='nearest')
cax = axes([0.1, 0.1, 0.8, 0.15])
colorbar(cax=cax, orientation='horizontal')
show()
 James> On question (2): Alan Isaac pointed out that using the same
 James> edgecolor as the fillcolor would make the borders
 James> invisible.
Yep.
JDH

>>>>> "Carol" == Carol Leger <car...@sr...> writes:
 Carol> This is how I modified poormans_contour.py:
It's a bug; in the matplotlib/pylab.py function "colorbar", replace
the line that reads
 N = 200
with
 N = cmap.N
No need to tweak the clim....
Should cure what ails ya,
JDH

>>>>> "Alan" == Alan G Isaac <ai...@am...> writes:
 Alan> Did you make full matplotlib and/or scipy language
 Alan> definitions? If so, are they available? Alan Isaac
I did, as you found in your PS, but I choose not to emphasize them
because I found all the extra color distracting. So I made the emph
color "black", ie the same as the color of plain text, but left the
wordlist there in case I changed my mind
 emphstyle = \color{black}, % color for matplotlib funcs
What do you think? Would it be useful to colorize the matplotlib
functions in the guide?
JDH

On 2005年1月15日, John Hunter apparently wrote:
> I'm using latex with the excellent listings package-
> http://www.atscire.de/index.php?nav=products/listings. It knows
> python syntax, and can do string, comment, keyword highlighting and
> more.
Did you make full matplotlib and/or scipy language definitions?
If so, are they available?
Alan Isaac
PS I found this list in the docs,
which is of course part of the answer to my question.
{axes, axis, bar, cla, clf, clim, close, cohere, colorbar,
 colors, csd, draw, errorbar, figimage, figlegend, figtext, figure,
 fill, gca, gcf, gci, get, get_current_fig_manager,
 get_plot_commands, gray, grid, hist, hlines, hold, imshow, jet,
 legend, load, loglog, pcolor, pcolor_classic, plot, plot_date,
 plotting, psd, raise_msg_to_str, rc, rcdefaults, save, savefig,
 scatter, scatter_classic, semilogx, semilogy, set, specgram, stem,
 subplot, table, text, title, vlines, xlabel, ylabel},

>>>>> "Gary" == Gary <pa...@in...> writes:
 Gary> John, I've been meaning to ask you ... how did you produce
 Gary> the very fine User Guide? Is that TeXmacs? LyX? raw
 Gary> LaTeX? ConTeXt? emacs magic?
I'm using latex with the excellent listings package-
http://www.atscire.de/index.php?nav=products/listings. It knows
python syntax, and can do string, comment, keyword highlighting and
more. 
You can see the latex src that created the user's guide by checking
out users_guide from matplotlib CVS, or visiting
http://cvs.sourceforge.net/viewcvs.py/matplotlib/users_guide . The
README file in that directory contains more information.
For much of the user's guide, I keep the python code in external files
and include them in a special verbatim environment that does syntax
highlighting with , eg
\lstinputlisting[linerange=1-12,caption={Wild and wonderful ways to specify colors;
 see Figure~\ref{fig:color_demo}},
label=lst:color_demo]{code/color_demo.py}
The linerange is used to leave some boilerplate at the beginning and
end of the file (eg some savefig calls to generate the accompanying
figures in eps and png). This helps insure that the python code in
the manual actually runs, since it is the same code used to generate
the figures for the guide.
 Gary> Is there some slick way of getting the listings from the
 Gary> command line window into the document, especially with the
 Gary> comments colorized? I'm writing a small local guide, and
 Gary> was wondering ...
By "the command line window" do you mean the python shell? If so,
you'll have to do some special tweaks to handle the >>> prompt, but
the listings packages is very sophisticated, and can ignore prefixes
or add them, etc.... There is a fairly comprehensive manual. Or did
you mean something else?
JDH