Re: [matplotlib-devel] Mathtext improvements (merging into trunk)

2007-07-27 Thread Gael Varoquaux
On Fri, Jul 27, 2007 at 08:52:27AM -0400, Michael Droettboom wrote: Using this mathtext=True option (as opposed to using a delimiter that TeX doesn't understand) or something else entirely, would certainly make it easier to make usetex vs. not usetex more consistent. I think so to. More

Re: [matplotlib-devel] Mathtext improvements (merging into trunk)

2007-07-27 Thread Michael Droettboom
Gael Varoquaux wrote: On Fri, Jul 27, 2007 at 08:38:49AM -0400, Michael Droettboom wrote: text(x, y, 'what is the $\sin(x)$', mathtext=True) Except for the backward incompatibility, I like this because it is explicit. Juust a data point for the discussion. I think it

Re: [matplotlib-devel] Mathtext improvements (merging into trunk)

2007-07-27 Thread Gael Varoquaux
On Fri, Jul 27, 2007 at 08:38:49AM -0400, Michael Droettboom wrote: text(x, y, 'what is the $\sin(x)$', mathtext=True) Except for the backward incompatibility, I like this because it is explicit. Juust a data point for the discussion. I think it would be very nice if a script gave the same

Re: [matplotlib-devel] Mathtext improvements (merging into trunk)

2007-07-27 Thread Michael Droettboom
John Hunter wrote: Option 1 is to educate them, and require them to \$ quote that symbol. Option 2 is to enable a text property eg mathtext, and do text(x, y, 'what is the $\sin(x)$', mathtext=True) Except for the backward incompatibility, I like this because it is explicit. Option 3 is

Re: [matplotlib-devel] Mathtext improvements (merging into trunk)

2007-07-27 Thread Darren Dale
On Friday 27 July 2007 08:38:49 am Michael Droettboom wrote: If we go with another delimiter, there are others in TeX to choose from. Plain TeX uses $$ for display math, and LaTeX uses \[, \]. Both of these are less likely to be legitimate literals. While display math normally implies that

Re: [matplotlib-devel] organization of traited config system

2007-07-27 Thread Darren Dale
On Thursday 26 July 2007 11:40:23 am Fernando Perez wrote: On 7/26/07, Darren Dale [EMAIL PROTECTED] wrote: On Thursday 26 July 2007 10:30:34 am Ted Drain wrote: Why do you need an api file at all? Why not have config be a python package and let config/__init__.py take care of importing

[matplotlib-devel] Determining file format in print_figure

2007-07-27 Thread Jouni K . Seppänen
A problem was reported on the users list that saving to a file named 'blah.pdf' using the wxagg backend actually saves a jpeg file named 'blah.pdf.jpg'. I think I can see how to fix this (by adding a block to FigureCanvasWx.print_figure() similar to the existing blocks for ps and svg), but would

Re: [matplotlib-devel] mpl1 draft

2007-07-27 Thread Ken McIvor
On Jul 25, 2007, at 12:09 PM, John Hunter wrote: Hi Ken -- sorry for the radio silence, I'm not intentionally ignoring you. Real life has made some demands on my time of late, and probably will until next week, but I was able to download, read through and test your code. I appreciate you

Re: [matplotlib-devel] mpl1 draft

2007-07-27 Thread John Hunter
Sent via BlackBerry from T-Mobile -Original Message- From: Ken McIvor [EMAIL PROTECTED] Date: Fri, 27 Jul 2007 17:35:05 To:John Hunter [EMAIL PROTECTED] Cc:matplotlib development list matplotlib-devel@lists.sourceforge.net Subject: Re: [matplotlib-devel] mpl1 draft On Jul 25, 2007,