Re: Thoughts on InsetExternal
On Tue, Dec 09, 2003 at 12:15:46PM +, Angus Leeming wrote:
Here is my list of things to do with InsetExternal, together with a
rationale for my preference.
* What should we do if generation of the output file fails? My choice
is to do nothing. If the external_templates file defines the
generated latex as '\includegraphics[options]{your_file}' or as
'\input{your_file}' then the latex compiler will fail to compile the
file and the user will be notified. Should the user wish to be tricky
and generate more complex latex then he is still free to do so but is
on his own.
* InsetGraphics has a 'draft' option that leads to the output
displaying a box containing the filename. I guess that this is
generally useful and that InsetExternal should both have a 'draft'
option and generate appropriate LaTeX itself. Whilst we could output
\includegraphics[draft]{your_file}, we couldn't output
\input[draft]{your_file}. Best therefore to have something like
\fbox{your_file}) Moreover, if 'draft' is set, there is no need to
convert your_file.ext to some appropriate format.
* Currently, the LyXRC::preview option that can be set from the
Preferences dialog applies to all insets. I'm of the opinion that
only mathed should respect this option. All other insets
(InsetExternal and InsetInclude) state explicitly whether they want a
preview generated and I think that this should override the LyXRC
variable. Thoughts? (Presumably this would mean renaming the LyXRC
variable to preview_math or somesuch.)
Everything fine as far as I am concerned.
* If the user specifies that he'd like to see a preview of the
external file and if the generation of the preview fails, then he's
left with an incorrect diagnostic message. The preview code needs
re-working if this is to be corrected.
Well, minor annoyance...
Andre'
Re: Thoughts on InsetExternal
Andre Poenitz wrote: * If the user specifies that he'd like to see a preview of the external file and if the generation of the preview fails, then he's left with an incorrect diagnostic message. The preview code needs re-working if this is to be corrected. Well, minor annoyance... You'd be amazed at how many complaints I used to get (mainly from John ;-) about the quality of the diagnostic messages output by InsetGraphics... -- Angus
Re: Thoughts on InsetExternal
On Tue, Dec 09, 2003 at 02:22:10PM +, Angus Leeming wrote: You'd be amazed at how many complaints I used to get (mainly from John ;-) Probably not. Andre'
Re: Thoughts on InsetExternal
On Tue, Dec 09, 2003 at 12:15:46PM +, Angus Leeming wrote:
> Here is my list of things to do with InsetExternal, together with a
> rationale for my preference.
>
> * What should we do if generation of the output file fails? My choice
> is to do nothing. If the external_templates file defines the
> generated latex as '\includegraphics[options]{your_file}' or as
> '\input{your_file}' then the latex compiler will fail to compile the
> file and the user will be notified. Should the user wish to be tricky
> and generate more complex latex then he is still free to do so but is
> on his own.
>
> * InsetGraphics has a 'draft' option that leads to the output
> displaying a box containing the filename. I guess that this is
> generally useful and that InsetExternal should both have a 'draft'
> option and generate appropriate LaTeX itself. Whilst we could output
> \includegraphics[draft]{your_file}, we couldn't output
> \input[draft]{your_file}. Best therefore to have something like
> \fbox{your_file}) Moreover, if 'draft' is set, there is no need to
> convert your_file.ext to some appropriate format.
>
> * Currently, the LyXRC::preview option that can be set from the
> Preferences dialog applies to all insets. I'm of the opinion that
> only mathed should respect this option. All other insets
> (InsetExternal and InsetInclude) state explicitly whether they want a
> preview generated and I think that this should override the LyXRC
> variable. Thoughts? (Presumably this would mean renaming the LyXRC
> variable to preview_math or somesuch.)
Everything fine as far as I am concerned.
> * If the user specifies that he'd like to see a preview of the
> external file and if the generation of the preview fails, then he's
> left with an incorrect diagnostic message. The preview code needs
> re-working if this is to be corrected.
Well, minor annoyance...
Andre'
Re: Thoughts on InsetExternal
Andre Poenitz wrote: >> * If the user specifies that he'd like to see a preview of the >> external file and if the generation of the preview fails, then he's >> left with an incorrect diagnostic message. The preview code needs >> re-working if this is to be corrected. > > Well, minor annoyance... You'd be amazed at how many complaints I used to get (mainly from John ;-) about the quality of the diagnostic messages output by InsetGraphics... -- Angus
Re: Thoughts on InsetExternal
On Tue, Dec 09, 2003 at 02:22:10PM +, Angus Leeming wrote: > You'd be amazed at how many complaints I used to get (mainly from John > ;-) Probably not. Andre'
