Agg backends (in addition to the ps backend) now support
affine-transformed image.
Regards,
-JJ
On Thu, Dec 17, 2009 at 7:05 PM, Jae-Joon Lee wrote:
> On Thu, Dec 17, 2009 at 5:03 PM, Andrew Straw wrote:
>> It's not clear to me if this proposal lets one specify any arbitrary affine
>> transfor
On Thu, Dec 17, 2009 at 5:03 PM, Andrew Straw wrote:
> It's not clear to me if this proposal lets one specify any arbitrary affine
> transformation. Does it?
I believe it does. 3 coordinates will define 6 equations where we have
6 unknowns of the affine matrix.
The question is how user want to sp
Jae-Joon Lee wrote:
> What I have in my mind is to extend the "extent" keyword of the imshow
> and make it optionally take a tuple of 6 numbers, which are (x1,
> x_lrc, x2, y1, y_lrc, y2).
> x1, x2, y1, y2 are same as the original "extent", and the (x_lrc,
> y_lrc) represent the coordinate of the l
I change the api to support an arbitrary affine transform. The current api is
def draw_image(self, gc, x, y, im, dx=None, dy=None, transform=None):
dx, dy is the width and height of the image, i.e.,
The 4 edge points of the image will be
(x, y), (x+dx, y), (x+dx, y+dy), (x, y+dy) after transfor
Jae-Joon Lee wrote:
> On Wed, Dec 16, 2009 at 12:59 PM, Jouni K. Seppänen wrote:
>
>> While the backend API is being changed, would it be similarly easy to
>> support arbitrary affine transformations? It would make the API more
>> symmetric, since many other draw_* methods take an affine
>> tra
On Wed, Dec 16, 2009 at 12:59 PM, Jouni K. Seppänen wrote:
> Jae-Joon Lee writes:
>
>> While extending this to other backend such as pdf and svg should be
>> straight forward, I want to hear how others think about the overall
>> approach, e.g., api change and such. The current approach is to
>> m
Jae-Joon Lee writes:
> While extending this to other backend such as pdf and svg should be
> straight forward, I want to hear how others think about the overall
> approach, e.g., api change and such. The current approach is to
> minimize change in backends.
While the backend API is being changed
A patch that enables drawing image in ps backend without resampling is
committed in r8035.
So, please test it if you're interested.
The raw image is to be used only when interpolation=="nearest" and
there is only one image.
While extending this to other backend such as pdf and svg should be
straig
Eric Firing writes:
> I'm not sure who the SVG expert is, and I presume the attached message
> applies to pdf as well as ps. I'm bringing it to your attention
> because it is suggesting what would seem to be significant
> improvements in some backends by taking better advantage of their
> native
