matplotlib-devel Mailing List for matplotlib

>>>>> "Jeremy" == Jeremy O'Donoghue <je...@o-...> writes:
 Jeremy> I'm not concerned by moving targets - the changes to date
 Jeremy> have been sensible both in improving functionality and
 Jeremy> rationalising the backend design.
Good to hear -- I think the code is becoming much cleaner. Even I
understand the way _matlab_helpers and Gcf works now!
 Jeremy> I may need to think about font size scaling separately -
 Jeremy> currently I just define the font point size, which
 Jeremy> probably is not what I should be doing. I may not have
 Jeremy> time to do this today, but will try to think about it in
 Jeremy> airport lounges ;-)
You probably will. Font size needs to scale with DPI, otherwise when
you go to a high res output the fonts look really tiny. I use
something like
 scale = self.dpi.get()/72.0
 self._font.set_size(scale*self._fontsize)
which as I indicated above is not perfect but gets close.
 Jeremy> By the way, I noticed on the users list that people are
 Jeremy> asking for Debian packages. I'm quite happy to do one, but
 Jeremy> would rather wait until things have calmed down - I'll
 Jeremy> target the 4.0 release for a .deb on the Sourceforge site.
I hope you mean 0.4 <wink>. By 4.0 we'll have already acquired The
MathWorks.
 Jeremy> We'll have to think about how the Debian package
 Jeremy> dependencies are worked out. My inclination is that we
 Jeremy> should require appropriate support for at least one
 Jeremy> backend, and suggest the others. Something like:
Required packages: python2.3-numeric, python2.3-numeric-ext, fonttools
 python2.3-gtk | libgd2-dev | libwxpython
Recommended packages: python2.3-gtk, libgd2-dev, libwxpython
Yes, I've been wondering about this but don't know enough about debian
to know how optional packages are handled. Note that neither gtk, gd,
or wx are required if all you want is PS (or Template!) output. For
the record, I'll list the dependencies by backend below. Since I am
not a debian whiz, I'll just list the actual dependencies and leave it
to the experts to sort out the debian packages that provide them
matplotlib
 Numeric
 PS backend
 (nothing extra)
 GTK backend
 GTK2
 pygtk-1.99.16 or later
 GD backend: 
 gd-2.0.15 
 gdmodule-0.42
 fonttools-2.0b1
 TTFQuery-0.2.6
 WX backend:
 wxPython-2.4.2.4
 Jeremy> Debian practice would normally provide separate packages
 Jeremy> matplotlib-doc and matplotlib-examples, so I'll try to
 Jeremy> arrange that.
 Jeremy> However, I don't really want to get into doing this until
 Jeremy> we are ready to make the next release. Debian packaging
 Jeremy> isn't especially hard, but it is rather tedious...
OK, but since we're shooting for release date of around 3 weeks from
now, it might be good to lay the groundwork, figure out how to handle
the optional dependencies, see if we can get gdmodule packed, etc....
Thanks!
John Hunter

I was unable to contact Marco awhile (months) back. I had been foolish
enough to volunteer to package, and he said he'd wait a couple of days and
then do it. After a week or so I wrote to say I wasn't going to get the
time, but my mails kept bouncing.
JV:I think that Marco Presi <zu...@de...> claims to be
JV:working on this. Maybe you can coordinate with him.
JV:See
JV:
JV: http://bugs.debian.org/206691
-- 
Charles R. Twardy www.csse.monash.edu.au/~ctwardy
Monash University sarbayes.org
Computer Sci. & Software Eng.
+61(3) 9905 5823 (w) 5146 (fax)

Hello,
On Tue, Nov 18, 2003 at 10:10:33AM -0000, Jeremy O'Donoghue wrote:
> By the way, I noticed on the users list that people are asking for Debian
> packages. I'm quite happy to do one, but would rather wait until things
> have calmed down - I'll target the 4.0 release for a .deb on the
> Sourceforge site.
> 
> We'll have to think about how the Debian package dependencies are worked
> out. My inclination is that we should require appropriate support for at
> least one backend, and suggest the others. Something like:
> 
> Required packages: python2.3-numeric, python2.3-numeric-ext, fonttools
> python2.3-gtk | libgd2-dev | libwxpython
> Recommended packages: python2.3-gtk, libgd2-dev, libwxpython
> 
> This would allow a Debian user to install matplotlib for only one backend
> (e.g. gd2 only for a webserver without X), but recommend packages to
> support other backends.
I think that Marco Presi <zu...@de...> claims to be
working on this. Maybe you can coordinate with him.
See
 http://bugs.debian.org/206691
for details.
> I can probably put simple packages for TTFQuery
> and gdmodule , which could be 'suggested'.
At http://seehuhn.de/debian/ you can find a python-ttfquery
package, which I produced for my own personal use. If
anything else in the Debian archive would use it, I probably
could upload it to the archive.
Best regards,
Jochen
-- 
http://seehuhn.de/

John Hunter said:
>
[snip]
>
> Jeremy - what this means for you is some more changes. Sorry to
> present you with an ever changing target. I've been working pretty
> hard of late clearing up a lot of lingering issues. Hopefully, we'll
> stabilize soon....
I'm not concerned by moving targets - the changes to date have been
sensible both in improving functionality and rationalising the backend
design.
Will try to commit appropriate changes today before I go off on a busines=
s
trip (back Friday, won't have CVS access before then, although I will tak=
e
a snapshot with me before I leave)
> Not sure this is perfect yet, but it seems to be a step in the right
> direction, and the relative sizes of the fonts to the figure appear to
> be better now -- previously too large in some backends, eg, GD. There
> is still a discrepancy between relative font sizes between the
> backends (eg, GTK versus PS) which may have to do with the font dpi
> issue (75 versus 100 dpi fonts under X11) but am not sure. In any
> case, I think the CVS changes are step in the right direction
I may need to think about font size scaling separately - currently I just
define the font point size, which probably is not what I should be doing.
I may not have time to do this today, but will try to think about it in
airport lounges ;-)
By the way, I noticed on the users list that people are asking for Debian
packages. I'm quite happy to do one, but would rather wait until things
have calmed down - I'll target the 4.0 release for a .deb on the
Sourceforge site.
We'll have to think about how the Debian package dependencies are worked
out. My inclination is that we should require appropriate support for at
least one backend, and suggest the others. Something like:
Required packages: python2.3-numeric, python2.3-numeric-ext, fonttools
 python2.3-gtk | libgd2-dev | libwxpython
Recommended packages: python2.3-gtk, libgd2-dev, libwxpython
This would allow a Debian user to install matplotlib for only one backend
(e.g. gd2 only for a webserver without X), but recommend packages to
support other backends. I can probably put simple packages for TTFQuery
and gdmodule , which could be 'suggested'.
Debian practice would normally provide separate packages matplotlib-doc
and matplotlib-examples, so I'll try to arrange that.
However, I don't really want to get into doing this until we are ready to
make the next release. Debian packaging isn't especially hard, but it is
rather tedious...
Regards
Jeremy