Jean-Marc Lasgouttes wrote:
>>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> * rotate, scale, crop. Which, if any, of these should be
> Angus> functions of the GraphicsInset? I think that none of them are
> Angus> and that we should have an InsetTransform that can contain an
> Angus> InsetGraphics (or an InsetExternal) and would pass (at least,
> Angus> only?) the crop info to the contained inset. I have little idea
> Angus> about how to do this however.
>
> I think you could make these part of the external inset and mark in
> the templates definitions whether they should be active for the given
> template. I would really real like to avoid an inset transform (but I
> am sure andre will think it is a great idea; actually I know it already).
Am I allowed to grin on a Friday?
Actually, if we combine it with the idea of using one InsetExternal but
several dialogs, then it might work really well. In fact, we could have
support for xfig (or even for 'latex images'?) that 'feels' identical to
that for InsetGraphics, but produces sophisticated output automatically.
Nonetheless, it 'feels' wrong to have this transformation info in
InsetGraphics. (Let's concentrate on what we have for the moment.) I have
this mad idea of 'two insets but one dialog'. Ie, InsetGraphics and
InsetTransform. Think of it as the counterpoint to the 'one inset,
multiple dialogs' suggestion ;-)
InsetTransform could be 'used' (somehow, not sure how) by InsetGraphics, by
InsetExternal, by InsetInclude (for \include{image.tex}).
Subcaption really has to go though.
--
Angus
