Re: [Pyx-devel] units and canvas marriage

[Andre W. <And...@Ph...>]

Hi,

On 26.02.02, Joerg Lehmann wrote:
> Hey, just to go over to something completely different.

(Next time it would be better to start a new thread for those things.
Otherwise we'll end up in just one subject line with 100 postings ...)

> How about
> dropping the unit in canvas, i.e. the late evaluation of units?
> I'm becoming more and more in favour of it, since I don't like:
>=20
> - passing a canvas for the intersection of bezier curves
> - passing a canvas for tranforming a arct into a bezier curves

The same for the h-size problem in tex.py.

> Both times, the canvas is absolutely necessary, so we are doing
> something wrong. At the moment I'm thinking of a solution, where
> you can only use uvw via a instance u("1 u mm"), which is the=20
> instance of a class generated by a metaclass unit:
>=20
>         u=3Dunit.unit(scale=3D{'u':1.5,...})
>=20
> Ok, metaclasses, but it would be a perfect fit ;))

One problem on dropping that out of the canvas is, that we then do not
know anymore how to change the unit, which we use, if we just write
plain numbers. If I see through it correctly, that was the reason for
the marriage of the canvas and the units and therefore for the late
evaluation. What about just saying t.text(1,2,"bla"). In what units
are these 1 and 2 are measured? (Same for paths, like lineto and
thatever else ...)


Andr=E9

--=20
by  _ _      _   And...@Ph...
   / \ \    / )  http://www.physik.uni-augsburg.de/~wobsta/
  / _ \ \/\/ /   watch a movie and learn about the mystery tippe top:
 (_/ \_)_/\_/    http://www.physik.uni-augsburg.de/~wobsta/tippetop/