Asger Kunuk Alstrup wrote:
> A simple export feature, however, even if it flashes a window
> shortly, is often a five-line patch: Open the document, save it in
> some useful format, and close the application again. From there, the
> converter business picks up the ball.
>
> Most maintainers would
On Tue, 7 Oct 2003, Angus Leeming wrote:
> One thing I have been thinking might be nice is the ability to use an
> arbitrary _external_ renderer to visualise the contents of the inset.
> We already have two internal renderers --- a simple button and a
> graphics renderer --- with a preview rendere
Asger Kunuk Alstrup wrote:
> So, maybe the best feature to develop is a "Template" editing GUI in
> the form of a "Wizard" which helps you make one.
;-)
Maybe indeed.
One thing I have been thinking might be nice is the ability to use an
arbitrary _external_ renderer to visualise the contents of
On Sat, 4 Oct 2003, Angus Leeming wrote:
> Oh come on! We have two or three Templates that are going to be used
> by many people. The rest are really just curiosities.
That's because the system is too complex for others to contribute
templates. I see lots of relevant template being added. Suitabl
Asger Kunuk Alstrup wrote:
> Exactly what you did above should probably be a transformer in
> itself. Call it "Transform WarningIfInputMissing". This is a general
> thing which many templates would have good use for.
>
> So, that example does not convince me -- in fact it convinces me
> that my ap
On Fri, 3 Oct 2003, Angus Leeming wrote:
[Clever stuff to print warning if input file is missing]
> Shrug. Nobody is using InsetExternal and that isn't because it has
> a complex API. Anyway, I think that the above example should get
> you on my side.
Exactly what you did above should probably b
Angus Leeming <[EMAIL PROTECTED]> writes:
| This patch is IMO ready to go.
| So, to quote ze main man, "Object now or be silent forever!"
So assuuming (the ass in you and me): I never said that!
--
Lgb
Angus Leeming <[EMAIL PROTECTED]> writes:
| Shrug.
Stop shrugging!
--
Lgb
This patch is IMO ready to go.
So, to quote ze main man, "Object now or be silent forever!"
It adds Resize, Rotate, Clip and an arbitrary Extra transformation to
InsetExternal. Frontend support is provided (both xforms and Qt) for
the Extra transform only. The rest will have to wait till the
I
Angus Leeming wrote:
> "\IfFileExists{#1}{$$RotateFront\input{$$BaseName.pstex_t}$$RotateBack}{\warnNotFound{$$BaseName.pstex_t}}"
Of course, $$BaseName should have a lowercase 'n' and you should
also replace #1 in the above with $$Basename.pstex_t
--
Asger Kunuk Alstrup wrote:
> I don't think you understood what I meant. I am not arguing to remove the
> entering and configuration of the rotation angle, or crippling the
> functionality to remove the "Extra" feature.
Yes, I had misunderstood.
However, I really don't like your proposal either,
I don't think you understood what I meant. I am not arguing to remove the
entering and configuration of the rotation angle, or crippling the
functionality to remove the "Extra" feature.
The GUI functionality is exactly the same as your current proposal.
The difference is only a question about wha
Asger Kunuk Alstrup wrote:
> OK, thank you. A high-level summary:
>
> LyX supports a fixed number of transformations, and a fixed number of
> exporting formats for these. In the external material definition file,
> you can define which transformations each template supports, and how to
> use combi
On Thu, 2 Oct 2003, Angus Leeming wrote:
> Attached. The document describes the ideas behind the language and the
> rationale of the separation of Data from Transform. It does not (yet)
> describe how it all glues together. Instead I attach a small sample code
> illustrating how I think it should
Asger Kunuk Alstrup wrote:
> From what I see, you have managed to keep the changes to the external
> definition file pretty simple. I'd like to read your documentation,
> but I do not have LyX working. Can you export to ASCII and send it
> privately?
Attached. The document describes the ideas behi
On Thu, 2 Oct 2003, Angus Leeming wrote:
> I also attach a document discussing the changes to the external template
> language and how the transformations are implemented. The document does
> not discuss how InsetExternal connects data and output transformations
> together, partly because this is
Angus Leeming wrote:
> (The code doing the work is fine, but I find the connections I make
> between RotationData and RotationLatexCommand, RotationLatexOption etc,
> etc very inelegant code. I have tried to introduce function pointers
> which do at least mean that the current approach will scale
Attached is a patch to InsetExternal allowing the user to 'transform' the
output in various ways. Specifically he can apply resize, rotate and clip
transformations. He can also apply arbitrary options not supported
directly by the GUI, These 'extra' options can be applied to specific
output for
18 matches
Mail list logo
