.ig >>
<STYLE TYPE="text/css">
<!--
        A:link{text-decoration:none}
        A:visited{text-decoration:none}
        A:active{text-decoration:none}
        OL,UL,P,BODY,TD,TR,TH,FORM { font-family: arial,helvetica,sans-serif;; font-size:small; color: #333333; }

        H1 { font-size: x-large; font-family: arial,helvetica,sans-serif; }
        H2 { font-size: large; font-family: arial,helvetica,sans-serif; }
        H3 { font-size: medium; font-family: arial,helvetica,sans-serif; }
        H4 { font-size: small; font-family: arial,helvetica,sans-serif; }
-->
</STYLE>
<title>ploticus: what's new</title>
<body bgcolor=D0D0EE vlink=0000FF>
<br>
<br>
<center>
<table cellpadding=2 bgcolor=FFFFFF width=550><tr>
<td>
  <table cellpadding=2 width=550><tr>
  <td><br><h2>What's new</h2></td>
  <td align=right>
  <small>
  <a href="../doc/welcome.html"><img src="../doc/ploticus.gif" border=0></a><br>
  Version 2.33 Jun'06
  <td></tr></table>
</td></tr>
<td>
<br>
<br>
.>>

.TH What's_new PL "02-JUN-2006   PL ploticus.sourceforge.net"

.ig >>


<li> <a href="prefab_updates.html">Recent prefab file updates</a>
<br><br>
 
<li> <a href="updates.html">Recent source code updates</a>
<br><br>

<li> Ploticus 2.33 release - 2 Jun '06 &nbsp; 
&nbsp; <a href="http://ploticus.sourceforge.net/doc/download.html">Download</a></h2>
<br><br>

<li> <a href="version233.html">What's new in version 2.33</a>
<br><br>

<li> <a href="news_old.html">What's new in version 2.32 and earlier</a>

<br><br>
<li> Home page: <a href="http://ploticus.sourceforge.net">ploticus.sourceforge.net</a>

<br><br><br>

<a name=breakers></a>
<h2>Cumulative summary of changes that might affect existing/old applications</h2>
Unless otherwise stated, ploticus versions are designed to be backward-compatible, meaning 
that a "well-behaved" script written for an earlier version of ploticus should work 
on any later version.  Any exceptions to this rule are noted here (most are fairly obscure).
<ul>
<li> <b>version 2.33</b> - proc scatterplot - the <tt>cluster</tt> option is now <tt>no</tt> by default.
Previous default had been <tt>yes</tt>.  The cluster option forces duplicate data points
to be made visible by offsetting them slightly, and involves a sort of all data points
(to ensure that duplicates are adjacent).
<br><br>
<li> <b>version 2.33</b> - clickmap - URLs are now encoded properly.  Before, the only encoding
performed on clickmap URLs was that embedded spaces would be changed to underscores.  Apps that
depended on this quirk might need adjustment.
<br><br>
<li> <b>version 2.33</b> - SVG - proc settings - the svg_linkparms attribute has been discontinued;
instead use the new <tt>clickmapurl: [target=new]http://abc.com...</tt> syntax.
<br><br>
<li> <b>version 2.33</b> - proc bars - when doing floating segment bars, the default method for
labelling bars has been changed to "longways", that is, a label is centered within each bar
rather than shown at the end of each bar.  This change likely won't bother anybody.
<br><br>
<li> <b>version 2.31</b> - the "datematic" feature was added for more automatic handling of date, time, and datetime data.
Old default behavior was autorange to exact maxima and minima, and to display one stub every 7 days.
New default behavior is for autorange and stub increment to be selected based on context.
Script that relied on old defaults may now give different results.
Scripts must now specify eg. <tt>xautorange: ... nearest=exact</tt> to get the exact max and min (and see
<a href="download.html">late update 2.31-03</a>)
<br><br>
<li> <b>version 2.31</b> - proc processdata, <tt>action: stats</tt> now can compute stats
on the data in one or several data fields given in the <tt>fields</tt> attribute.
Previously, a second field specified in the <tt>fields</tt> attribute was taken as an identifier field
for MIN_ID and MAX_ID.. now a separate attribute <tt>tagfield</tt> is used for this purpose.
<br><br>
<li> <b>version 2.30</b> - with -csmap (client-side image maps PNG/GIF/JPEG) the default is now for map 
content to be written to <tt>stdout</tt> since this seems to be what is usually wanted.  
Previously the default had been for it to be written to a file.  
Server-side image maps (<tt>-map</tt>) and SVG are not affected by this change.
<br><br>
<li> <b>version 2.30</b> - <a href="prefab_news.html">prefabs - a few changes that might minimally affect existing applications</a>
 - see "Caution:"
<br><br>
<li> <b>version 2.30</b> - <a href="svg.html#mouseover">SVG mouseover</a> - the default method for
doing mouseover text tooltip bubbles has been improved but it now references
two new <a href="download.html#acc">javascript files</a>.

<br><br>

<li> <b>version 2.10</b> (probably) - the <a href="processdata.html">proc processdata</a> <tt>breaks</tt> action requires
an invocation of <a href="usedata.html">proc usedata</a> to get back to the original data
set.  This is now explained correctly in the docs.

<br><br>
<li> sometime after version 1.39, time values greater than 24:00:00 began to be regarded as
invalid (they're invalid for clock times but not for elapsed times).  This has been fixed in 2.20
but requires a format such as <tt>hhh:mm:ss</tt> to be specified when working with elapsed times (<tt>hhh</tt>
indicates elapsed time, no upper limit).  
<br><br>
<li> <b>version 2.10</b> - several obscure changes: 
config file parameters <tt>sid</tt>, <tt>gid</tt>, and <tt>filesizelimit</tt> dropped;
number display format settings dropped from proc page;
proc areadef <tt>catcompmethod: fuzzy</tt> no longer supported;
proc processdata <tt>stack</tt> is now <tt>no</tt> by default, which might be an issue in scripts that use 
<tt>originaldata</tt> to access processdata result data set;
<br><br>
<li> <b>version 2.03</b> - pltab no longer supported.  However, it is still available from
<a href="http://ploticus.sourceforge.net/steve.html">here</a>.
<br>
<br>
<li> <b>version 2.03</b> - proc rect (old name proc bevelrect) - bevelsize must now be specified
in order to get a bevelled rectangle.
<br>
<br>
<li> <b>version 2.02</b> - lines prefab - changed the way that the <tt> fill </tt> parameter works.  
Previously it had applied to all curves and line color was used.  Now it is specified
as a color, and separately for each curve (using fill2, fill3, and fill4).  This will 
break any existing applications that use the lines prefab to render multiple filled curves.
<br>
<br>
<li> <b>version 2.00</b> - New script interpreter resulted in some script syntax changes.
Concatenation of variables is done differently in <b>#set</b> and <b>#if</b> statements,
<b>#setifnotgiven</b> replaces <b>#declare soft</b>, and some other minor issues.
<a href="changes20.html">Here are the details.</a> 
</ul>
<br>
<br>
<br>
<a name=requests></a>
<br>
<h2>Requested features list</h2>
These items have been mentioned in correspondence (or in some cases dreamed up by myself) 
but are not currently on the "front burner".  It's likely that some of these will
be addressed eventually but probably not in the immediate future.  If you have interest
in taking any of these on, let me know and I will be happy to facilitate.

<ul>
<li> a method for automatic annotation placement, including avoidance of annotation, label, and plot object collisions.
Rudimentary collision detection would probably
involve keeping a list of labels and graphical elements and checking this
list before rendering each successive element.  The workaround for people
who need it (such as those publishing in journals) is to render in EPS
then use Adobe tools to manipulate elements by hand.


<br><br>
<li> polar coordinates, radar plots, star plots (<a href="http://ploticus.sourceforge.net/download/stargraph.jpg">example</a>)
Unfortunately polar/radar can't be implemented just by writing new data
space to absolute space translating routines.. for one thing assumptions
about drawing long straight lines in x y space based on two endpoints
don't hold in polar/radar space (they need to be curved around).
<br><br>
<li> Interface to later versions of GD that have antialiased linedrawing (in grgd.c, shielded by #ifdefs)
(note: may not be necessary now with the better data point symbols in 2.33)
<br><br>
<li> Provide a "canned" ploticus freetype build (executables) for linux (requires static freetype2 lib(s)
<br><br>
<li> Right-to-left font support for languages such as Arabic, Hebrew, for ploticus
freetype, SVG, etc.  This might be best implemented by someone who can read in one
of these languages, to verify correctness.
<br><br>
<li> PDF output capability
<br><br>
<li> additional prefabs 
<br><br>
<li> a way to define holidays in config file (similar to omitweekends)
<br><br>
<li> facilities to make QQ plots easier
<br><br>
<li> the ability to run as a persistent daemon and accept commands via named pipe
<br><br>
<li> more 3-D plots and effects
<br><br>
<li> XML script syntax option - the plotting procs fit the xml model easily enough
but not sure what to do about flow of control operators such as #if or #for .. #endloop.
<br><br>
<li> a mechanism similar to catslide that would allow similar minor adjustment of scaled data placement
for any type of axis, not just categories.
<br><br>
<li> alternative to 0am for displaying "midnight"
<br><br>
<li> proc pie option to produce ring graphs
</ul>
<br>
<br>


.>>

.ig >>
<br>
<br>
</td></tr>
<td align=right>
<a href="../doc/welcome.html">
<img src="../doc/ploticus.gif" border=0></a><br><small>data display engine &nbsp; <br>
<a href="../doc/Copyright.html">Copyright Steve Grubb</a>
<br>
<br>
<center>
<img src="../gallery/all.gif"> 
</center>
</td></tr>
</table>
<br>
<center>
Ploticus is hosted at http://ploticus.sourceforge.net <br>
<img src="http://sourceforge.net/sflogo.php?group_id=38453" width="88" height="31" border="0" alt="SourceForge Logo">
</center>
.>>
