gnuplot-beta

Gnuplot version 5.0 is now available

[Ethan A M. <sf...@us...>]

Gnuplot version 5.0 is now available.

Release Notes here:

    http://gnuplot.sourceforge.net/ReleaseNotes_5_0.html

Source tarball and MSWin 32-bit binaries can be downloaded here:

    https://sourceforge.net/projects/gnuplot/files/gnuplot/5.0.0/

	Happy New Year
	     and
	Happy gnuplotting
-- 
Ethan Merritt (sf...@us...)
on behalf of the gnuplot development team

Thanks! (was: Gnuplot version 5.0 is now available)

[Philipp K. J. <ja...@ie...>]

That's exciting news - many thanks to Ethan and
the development team!

Best,

		Ph.



On Fri, 02 Jan 2015 10:15:33 -0800
Ethan A Merritt <sf...@us...> wrote:

> Gnuplot version 5.0 is now available.
> 
> Release Notes here:
> 
>     http://gnuplot.sourceforge.net/ReleaseNotes_5_0.html
> 
> Source tarball and MSWin 32-bit binaries can be downloaded here:
> 
>     https://sourceforge.net/projects/gnuplot/files/gnuplot/5.0.0/
> 
> 	Happy New Year
> 	     and
> 	Happy gnuplotting

Re: Gnuplot version 5.0 is now available

[Petr M. <mi...@ph...>]

> Gnuplot version 5.0 is now available.

Really great achievement!

I noticed a small bug - the "test" command on x11 shows dashed rectangle 
around the central numbers instead of a solid one.

I miss a note in "help new-features" why the linetype colour sequence has 
changed and how to revert it back. (The most strange is red at position 7.)
I remember the discussion about colour blind people but at the same time there 
are millions of old graphs rendered in the "traditional colour sequence" and 
most users are used to the first 3-4 colours.
Actually, "help linetype" says:
  ...
  For example, linetypes one and two default to red and green.
  ...
which is no longer valid.

---
Petr

Re: Gnuplot version 5.0 is now available

[Achim G. <Str...@ne...>]

Ethan A Merritt writes:
> Gnuplot version 5.0 is now available.

Thanks.  I've compiled on Cygwin (with cygport/autotools and both on
64bit and 32bit) and see the following issues:

1. The Qt terminal still doesn't work.  No plot window ever shows up and
each invocation of plot will produce another qt_terminal process.
gnuplot itself seems to hang, but recovers after about 20s with a
message about "font initialisation" taking too long.

2. Configuring with Qt5 need changes to configure.in to work.  The
configure script tries to determine the path to uic et.al. via a
pkg-config query for exec_bin.  The correct variable to query is
actually host_bins.

--8<---------------cut here---------------start------------->8---
 QT5LOC=`$PKG_CONFIG --variable=exec_prefix Qt5Core`
 UIC=${QT5LOC}/bin/uic
 MOC=${QT5LOC}/bin/moc
 RCC=${QT5LOC}/bin/rcc
 LRELEASE=${QT5LOC}/bin/lrelease
-------
 QT5LOC=`$PKG_CONFIG --variable=host_bins Qt5Core`
 UIC=${QT5LOC}/uic
 MOC=${QT5LOC}/moc
 RCC=${QT5LOC}/rcc
 LRELEASE=${QT5LOC}/lrelease

--8<---------------cut here---------------end--------------->8---

3. The demo plugin doesn't link, I haven't yet investigated why
(probably some of the hardcoded linker flags don't make much sense on
Cygwin).  I didn't find a way to tell configure that it should not
compile the demo plugin other than removing the plugin support
completely.


Other than that things seem to work well although we'll have to change a
number of scripts that got caught in the changes w.r.t. to the linetype
command and some tightened syntax rules.  On the upside it looks we can
drop a patch that gave us more linetypes and dash patterns and just
define them in the defaults instead.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

Re: Gnuplot version 5.0 is now available

[Ethan A M. <sf...@us...>]

On Tuesday, 06 January, 2015 19:25:17 Achim Gratz wrote:
> Ethan A Merritt writes:
> > Gnuplot version 5.0 is now available.
> 
> Thanks.  I've compiled on Cygwin (with cygport/autotools and both on
> 64bit and 32bit) and see the following issues:

Thanks for testing.

> 1. The Qt terminal still doesn't work.  No plot window ever shows up and
> each invocation of plot will produce another qt_terminal process.
> gnuplot itself seems to hang, but recovers after about 20s with a
> message about "font initialisation" taking too long.

I'm afraid I have no insight into what might be causing that problem.
IIRC the initial testers on OSX reported a similar problem but in
that case it really was font initialisation and the problem went 
away after the first run.

> 2. Configuring with Qt5 need changes to configure.in to work.  The
> configure script tries to determine the path to uic et.al. via a
> pkg-config query for exec_bin.  The correct variable to query is
> actually host_bins.

Hmm.
On my linux systems the host_bins field in Qt5Core.pc is empty,
so I am not sure this convention is universal.

On the other hand, the linux Qt5 package also sets the correct path via
/etc/profile.d/qt5.sh so that in practice the gnuplot autoconfigure
script would work anyhow.

Can you point to some documentation or policy about when that
pkg-config field is relevant or necessary?

> --8<---------------cut here---------------start------------->8---
>  QT5LOC=`$PKG_CONFIG --variable=exec_prefix Qt5Core`
>  UIC=${QT5LOC}/bin/uic
>  MOC=${QT5LOC}/bin/moc
>  RCC=${QT5LOC}/bin/rcc
>  LRELEASE=${QT5LOC}/bin/lrelease
> -------
>  QT5LOC=`$PKG_CONFIG --variable=host_bins Qt5Core`
>  UIC=${QT5LOC}/uic
>  MOC=${QT5LOC}/moc
>  RCC=${QT5LOC}/rcc
>  LRELEASE=${QT5LOC}/lrelease
> 
> --8<---------------cut here---------------end--------------->8---
> 
> 3. The demo plugin doesn't link, I haven't yet investigated why
> (probably some of the hardcoded linker flags don't make much sense on
> Cygwin).  I didn't find a way to tell configure that it should not
> compile the demo plugin other than removing the plugin support
> completely.

./configure --disable-plugins
is supposed to work.  Does it not?

> Other than that things seem to work well although we'll have to change a
> number of scripts that got caught in the changes w.r.t. to the linetype
> command and some tightened syntax rules.  On the upside it looks we can
> drop a patch that gave us more linetypes and dash patterns and just
> define them in the defaults instead.

If you don't mind my asking, who is the "we" in this case?

> 
> Regards,
> Achim.

	Ethan 

Re: Gnuplot version 5.0 is now available

[Enrico F. <fo...@ly...>]

On Tue, Jan 06, 2015 at 12:11:56PM -0800, Ethan A Merritt wrote:

> On Tuesday, 06 January, 2015 19:25:17 Achim Gratz wrote:
> > Ethan A Merritt writes:
> > > Gnuplot version 5.0 is now available.
> > 
> > Thanks.  I've compiled on Cygwin (with cygport/autotools and both on
> > 64bit and 32bit) and see the following issues:
> 
> Thanks for testing.
> 
> > 1. The Qt terminal still doesn't work.  No plot window ever shows up and
> > each invocation of plot will produce another qt_terminal process.
> > gnuplot itself seems to hang, but recovers after about 20s with a
> > message about "font initialisation" taking too long.
> 
> I'm afraid I have no insight into what might be causing that problem.
> IIRC the initial testers on OSX reported a similar problem but in
> that case it really was font initialisation and the problem went 
> away after the first run.

On Cygwin, this is due to the fact that non-blocking named pipes do not
work. See: http://thread.gmane.org/gmane.os.cygwin/113787/focus=114321

However, patching both Qt and gnuplot sources, I am able to get a
working Qt terminal on Cygwin. I am attaching the patches I use.

> > 3. The demo plugin doesn't link, I haven't yet investigated why
> > (probably some of the hardcoded linker flags don't make much sense on
> > Cygwin).  I didn't find a way to tell configure that it should not
> > compile the demo plugin other than removing the plugin support
> > completely.
> 
> ./configure --disable-plugins
> is supposed to work.  Does it not?

I found that replacing "so" with "dll" in demo/plugin/Makefile.am does
produce a plugin, even if it is named demo_plugin.dll.exe, i.e., with
an extra .exe suffix...

HTH

-- 
Enrico

Re: Gnuplot version 5.0 is now available

[Achim G. <Str...@ne...>]

Ethan A Merritt writes:
> Can you point to some documentation or policy about when that
> pkg-config field is relevant or necessary?

It's used in both Cygwin and openSUSE, but instead of looking at the .pc
file please try

pkg-config --variable=host_bins QT5Core

as there may be some fallback rules to fill in empty slots (I'm not
overly familiar with how the .pc files are put together).  If not, then
the configure rule in question should probably be re-written using the
PKG_CHECK_VAR autoconf macro to provide a fallback specific to gnuplot.

In any case using exec_prefix is clearly wrong (it works on some
installations purely by accident) and host_bins is what Qt5 introduced
as a repleacement for the tool variables in Qt4.

https://qt.gitorious.org/qt/qtbase/source/3fed060b94ff04131de603d4d668ae7853e50a53:dist/changes-5.0.0

--8<---------------cut here---------------start------------->8---
 * moc_dir, rcc_dir and some other tool variables are not defined in Qt's .pc files any more;
the generic host_bins is defined instead.
--8<---------------cut here---------------end--------------->8---

> ./configure --disable-plugins
> is supposed to work. Does it not?

Yes (I've been using that), but AFAICS that disables plugin support
completely.  I just wanted to find a way to not compile the demo plugin
until I can figure out why it doesn't link and there doesn't seem to be
any.

> If you don't mind my asking, who is the "we" in this case?

My colleagues and myself at work.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: Gnuplot version 5.0 is now available

[Achim G. <Str...@Ne...>]

Achim Gratz <Stromeko <at> nexgo.de> writes:
> Other than that things seem to work well although we'll have to change a
> number of scripts that got caught in the changes w.r.t. to the linetype
> command and some tightened syntax rules.  On the upside it looks we can
> drop a patch that gave us more linetypes and dash patterns and just
> define them in the defaults instead.

We've adapted the scripts now.

It was mostly that in many places an "offset" is now required instead of
simply the two coordinates.

Some observations that need further investigation ("before" refers to
gnuplot 4.6.6 and we're using the cairopdf terminal unless otherwise noted):

The linetype -1 is no longer working as it did before at least when you try
to change the linewidth and/or the dash type.

The positioning of the plot area is different than before.  There's more
space below the title than there was before and less space below the plot
area if you have the legend below the plot.

The ticks and grid lines are much thicker than before.

The Cairo PDF output is about 50% larger than before.  Going through PS and
ghostscript doesn't produce noticeably larger files.


Regards,
Achim.