On Friday 28 June 2002 11:01 am, David Kastrup wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> > Alternatively, perhaps we should think of setting off a single
> > forked process that will result in multiple image files when loading
> > the document. This is definitely possible in the case of the mathed
> > preview I believe and is essentially what David was suggesting by
> > using preview.sty.
>
> It's one of the mechanisms we use here.  Starting off the previewing
> process with preview-latex involves a single run of LaTeX, a single
> run of Dvips generating a single PostScript file, and a single run of
> GhostScript in which the images are rendered by GhostScript in
> "display order", rendering the on-screen images (requests get
> reordered dynamically if you page while rendering is under process)
> with priority, the off-screen ones afterwards.
>
> The very first versions of preview-latex still used a single
> LaTeX/Dvips run, where Dvips produced a host of single EPS files, and
> those were handed to the display engine of Emacs, which then ran
> GhostScript on every single of them on-demand.
>
> Performance was abysmal.  Paging through the document became a pain,
> because it caused a flurry of GhostScript processes to be created.
> We never even made a single release from this state, it is just
> prehistoric CVS.
>
> You are of course free to ignore the experiences we made while
> developing preview-latex (I described this a few times already), and
> free to ignore the LaTeX styles, PostScript code and other
> infrastructure we developed to make this work smoothly.  Since you
> have quite more developers on your project, you can probably easily
> afford a bit of reinvention of the wheel, and probably come up even
> with a few interesting twists on that theme.
>
> It will certainly be interesting to see how this functionality will
> progress.
>
> All the best,

Devid, there's no need to be so prickly. We aren't monsters and we do listen. 
This is a new feature to us and we're having to develop some infrastructure 
first, that's all.

Angus

Reply via email to