octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Another FLTK/gnuplot divergence


From: Michael D. Godfrey
Subject: Re: Another FLTK/gnuplot divergence
Date: Fri, 27 Sep 2013 14:12:29 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130805 Thunderbird/17.0.8

On 09/27/2013 12:26 PM, Rik wrote:
On 09/27/2013 08:57 AM, Mike Miller wrote:
> On Fri, Sep 27, 2013 at 08:47:20 -0700, Rik wrote:
>> 8. FLTK also can't do printing of hidden figures.
>>
>> It would be nice to switch the production of figures for the Octave manual
>> from gnuplot to FLTK now that it is the default.  The only problem is that
>> the window will have to flash on the screen and close as the make process
>> is going on.  This shouldn't happen very often as the images are only
>> re-built after a 'make maintainer-clean' and they are distributed with the
>> documentation so newbies won't have to see this.
>>
>> Any objections to making this change?
> Yes, the build *must* be able to complete and produce valid
> documentation without any display, without even an X server running,
> to work in automated or minimal build environments for example.
I take your point, although automated builds of tarballs (such as for a
downstream package maintainer like Debian) would still work in all cases
because the images are shipped with the code.  It would only be an
automated build server like Hydra, which is operating directly from the
Mercurial sources, that would have a problem.

--Rik
Rik,

There is another problem with using fltk for doc:  print with interpreter
set to tex does not work.  Thus, Figures like 15.7 would not come out right.

Just as a feature, it would be nice to be able to generate plots as images (PDF, jif, etc.)
without any display on the screen.  It appears that this will take some work.
An obvious case where this would be useful is when using a script to generate
lots of plots which are to be included in a TeX or LaTeX or similar for publication.

Michael


reply via email to

[Prev in Thread] Current Thread [Next in Thread]