> > Storing the xfig-source within the .lyx is not difficult with
> > the filecontents environment. On the other hand, in order for
> > xfig to render a picture into an xfig-inset, you have to patch
> > xfig as well. Remember LyX pretends to be a ghostview (by
> > setting some hints) in order for a ghostscript to render a
> > figure in an inset.
> > A gnuplot-inset (with egplot?) and a gyve-inset would also be
> > nice :) Any takers?
>
> This is where a generic external-app-inset would be handy. However it
> needs to have a way of having these 'hints' or whatever tricks are
> required. For X at least aren't we supposed to be able to effectively run
> one app in a window of another app easily without need for extra tricks?
> This might however require that we have a real ghostview window in the
> fig-inset. I don't know X so I'm sure someone will correct me.
I don't think that it is necessary to run xfig within lyx's window.
Am I missing the point?
If the .fig file is stored in the .lyx file, and the user selects
somehow the xfig inset, one could store the .fig in some temporary .fig
file, spawn xfig. When the user quits xfig, grab the tempfile, put it
back into lyx. Use fig2dev to create an .ps that could be rendered as it
is done in ps-insets.
When printing (or creating a .dvi) one could use fig2dev to create a .ps
or even combined ps/latex (which I'd prefer) that gets included in the
LaTeX source.
There is obviously some work involved, but I don't see the need for
"dirty hacking" ;-)
Andre'
--
Andre' Poenitz, TU Chemnitz, Fakultaet fuer Mathematik
[EMAIL PROTECTED] ... +49 3727 58 1381
