ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Florian Wobbe <Florian.Wobbe@awi.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Gnuplot module: Patching of Gnuplot binary still needed?
Date: Mon, 22 Nov 2010 22:44:28 +0100	[thread overview]
Message-ID: <C159DB97-7809-465D-BABD-790CF6A6E9BA@awi.de> (raw)
In-Reply-To: <AANLkTin6mUxZJV8JnHDtxBEMU3MM5qOwVqZnz2GQ_JNS@mail.gmail.com>

On Nov 22, 2010, at 22:03 , Mojca Miklavec wrote:

> On Mon, Nov 22, 2010 at 20:15, Florian Wobbe wrote:
> 
>> Especially for line drawings it would be beneficial not to place every single point. Instead consecutive points should be skipped if they are close to each other (with regard to plot units) - it makes no sense to include points which you won't see anyway. This could be done by defining a grid with a certain (user defined) resolution and rounding the coordinates (plot units) of a line point to the nearest grid node. All consecutive line points falling on the same grid node should not be passed on to terminal drivers. The psxy utility of GMT (http://gmt.soest.hawaii.edu/) does this for instance. I am not aware of such a functionality within gnuplot but it would be a nice feature.
> 
> But this is an issue of Gnuplot, not something that a terminal writer
> is supposed to think of.

Indeed, this was my point in the first place. It should be handled by gnuplot prior to handing the data over to the terminal driver.

> But yes, it would be nice if also ConTeXt terminal would be included.
> It still doesn't support raw images, but most other features are
> present.

Right, this might help increase the awareness among academics. Also not everyone has the ability to build gnuplot from sources.

Florian

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2010-11-22 21:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-14 22:04 Paul Menzel
2010-11-15 11:29 ` Mojca Miklavec
     [not found]   ` <201011152131.18476.peter@affenbande.org>
2010-11-17 10:47     ` Mojca Miklavec
2010-11-18 23:38       ` Florian Wobbe
2010-11-22 15:01         ` Mojca Miklavec
2010-11-22 18:12           ` Ethan Merritt
2010-11-22 19:15           ` Florian Wobbe
2010-11-22 21:03             ` Mojca Miklavec
2010-11-22 21:19               ` Aditya Mahajan
2010-11-22 21:26                 ` Mojca Miklavec
2010-11-22 22:20                 ` Alan BRASLAU
2010-11-22 21:44               ` Florian Wobbe [this message]
2010-11-22 22:10                 ` Mojca Miklavec
2010-11-18  6:11   ` Jonas Stein
2011-01-09 21:50     ` jeroen.muskee
2011-01-09 18:54       ` Mojca Miklavec
2011-01-09 19:01         ` Aditya Mahajan
2011-01-09 23:20         ` Mojca Miklavec
2011-01-11  3:26           ` jeroen.muskee
2010-11-18 18:28   ` Paul Menzel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C159DB97-7809-465D-BABD-790CF6A6E9BA@awi.de \
    --to=florian.wobbe@awi.de \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).