{
    "mode": "perldoc",
    "parameter": "Chart",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/perldoc/Chart/json",
    "generated": "2026-06-15T16:01:21Z",
    "synopsis": "use Chart::type;   (type is one of: Points, Lines, Bars, LinesPoints, Composite,\nStackedBars, Mountain, Pie, HorizontalBars, Split, ErrorBars, Pareto, Direction)\n$obj = Chart::type->new;\n$obj = Chart::type->new ( $pngwidth, $pngheight );\n$obj->set ( $key1, $val1, ... ,$keyn, $valn );\n$obj->set ( $key1 => $val1,\n...\n$keyn => $valn );\n$obj->set ( %hash );\n# GIFgraph.pm-style API to produce png formatted charts\n@data = ( \\@xticklabels, \\@dataset1, ... , \\@datasetn );\n$obj->png ( \"filename\", \\@data );\n$obj->png ( $filehandle, \\@data );\n$obj->png ( FILEHANDLE, \\@data );\n$obj->cgipng ( \\@data );\n# Graph.pm-style API\n$obj->addpt ($label, $val1, ... , $valn);\n$obj->adddataset ($val1, ... , $valn);\n$obj->png ( \"filename\" );\n$obj->png ( $filehandle );\n$obj->png ( FILEHANDLE );\n$obj->cgipng ();\nThe similar functions are available for j-peg\n# Retrieve image map information\n$obj->set ( 'imagemap' => 'true' );\n$imagemapref = $obj->imagemapdump ();",
    "sections": {
        "NAME": {
            "content": "Chart - a series of charting modules\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "use Chart::type;   (type is one of: Points, Lines, Bars, LinesPoints, Composite,\nStackedBars, Mountain, Pie, HorizontalBars, Split, ErrorBars, Pareto, Direction)\n\n$obj = Chart::type->new;\n$obj = Chart::type->new ( $pngwidth, $pngheight );\n\n$obj->set ( $key1, $val1, ... ,$keyn, $valn );\n$obj->set ( $key1 => $val1,\n...\n$keyn => $valn );\n$obj->set ( %hash );\n\n# GIFgraph.pm-style API to produce png formatted charts\n@data = ( \\@xticklabels, \\@dataset1, ... , \\@datasetn );\n$obj->png ( \"filename\", \\@data );\n$obj->png ( $filehandle, \\@data );\n$obj->png ( FILEHANDLE, \\@data );\n$obj->cgipng ( \\@data );\n\n# Graph.pm-style API\n$obj->addpt ($label, $val1, ... , $valn);\n$obj->adddataset ($val1, ... , $valn);\n$obj->png ( \"filename\" );\n$obj->png ( $filehandle );\n$obj->png ( FILEHANDLE );\n$obj->cgipng ();\n\nThe similar functions are available for j-peg\n\n# Retrieve image map information\n$obj->set ( 'imagemap' => 'true' );\n$imagemapref = $obj->imagemapdump ();\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "These man-pages give you the most important information about Chart. There is also a complete\ndocumentation (Documentation.pdf) within the Chart package. Look at it to get more information.\nThis module is an attempt to build a general purpose graphing module that is easily modified and\nexpanded. I borrowed most of the API from Martien Verbruggen's GIFgraph module. I liked most of\nGIFgraph, but I thought it was to difficult to modify, and it was missing a few things that I\nneeded, most notably legends. So I decided to write a new module from scratch, and I've designed\nit from the bottom up to be easy to modify. Like GIFgraph, Chart uses Lincoln Stein's GD module\nfor all of its graphics primitives calls.\n\nuse-ing Chart\nOkay, so you caught me. There's really no Chart::type module. All of the different chart types\n(Points, Lines, Bars, LinesPoints, Composite, StackedBars, Pie, Pareto, HorizontalBars, Split,\nErrorBars, Direction and Mountain so far) are classes by themselves, each inheriting a bunch of\nmethods from the Chart::Base class. Simply replace the word type with the type of chart you want\nand you're on your way. For example,\n\nuse Chart::Lines;\n\nwould invoke the lines module.\n",
            "subsections": [
                {
                    "name": "Getting an object",
                    "content": "The new method can either be called without arguments, in which case it returns an object with\nthe default image size (400x300 pixels), or you can specify the width and height of the image.\nJust remember to replace type with the type of graph you want. For example,\n\n$obj = Chart::Bars->new (600,400);\n\nwould return a Chart::Bars object containing a 600x400 pixel image. New also initializes most of\nthe default variables, which you can subsequently change with the set method.\n"
                },
                {
                    "name": "Setting different options",
                    "content": "This is where the fun begins. Set looks for a hash of keys and values. You can pass it a hash\nthat you've already constructed, like\n\n%hash = ('title' => 'Foo Bar');\n$obj->set (%hash);\n\nor you can try just constructing the hash inside the set call, like\n\n$obj->set ('title' => 'Foo Bar');\n\nThe following are all of the currently supported options:\n\n'transparent'\nMakes the background of the image transparent if set to 'true'. Useful for making web page\nimages. Default is 'false'.\n\n'pngborder'\nSets the number of pixels used as a border between the graph and the edges of the png/j-peg.\nDefaults to 10.\n\n'graphborder'\nSets the number of pixels used as a border between the title/labels and the actual graph\nwithin the png. Defaults to 10.\n\n'textspace'\nSets the amount of space left on the sides of text, to make it more readable. Defaults to 2.\n\n'title'\nTells GD graph what to use for the title of the graph. If empty, no title is drawn. It\nrecognizes '\\n' as a newline, and acts accordingly. Remember, if you want to use normal\nquotation marks instead of single quotation marks then you have to quote \"\\\\n\". Default is\nempty.\n\n'subtitle'\nWrite a sub-title under the title in smaller letters.\n\n'xlabel'\nTells Chart what to use for the x-axis label. If empty, no label is drawn. Default is empty.\n\n'ylabel', 'ylabel2'\nTells Chart what to use for the y-axis labels. If empty, no label is drawn. Default is\nempty.\n\n'legend'\nSpecifies the placement of the legend. Valid values are 'left', 'right', 'top', 'bottom'.\nSetting this to 'none' tells chart not to draw a legend. Default is 'right'.\n\n'legendlabels'\nSets the values for the labels for the different data sets. Should be assigned a reference\nto an array of labels. For example,\n\n@labels = ('foo', 'bar');\n$obj->set ('legendlabels' => \\@labels);\n\nDefault is empty, in which case 'Dataset 1', 'Dataset 2', etc. are used as the labels.\n\n'ticklen'\nSets the length of the x- and y-ticks in pixels. Default is 4.\n\n'xticks'\nSpecifies how to draw the x-tick labels. Valid values are 'normal', 'staggered' (staggers\nthe labels vertically), and 'vertical' (the labels are draw upwards). Default is 'normal'.\n\n'xyplot'\nForces Chart to plot a x-y-graph, which means, that the x-axis is also numeric if set to\n'true'. Very useful for mathematical graphs. Works for Lines, Points, LinesPoints and\nErrorBars. Split makes always a xyplot. Defaults to 'false'.\n\n'minyticks'\nSets the minimum number of yticks to draw when generating a scale. Default is 6, The\nminimum is 2.\n\n'maxyticks'\nSets the maximum number of yticks to draw when generating a scale. Default is 100. This\nlimit is used to avoid plotting an unreasonable large number of ticks if non-round values\nare used for the minval and maxval.\n\nThe value for 'maxyticks' should be at least 5 times larger than 'minyticks'.\n\n'maxxticks', 'minxticks'\nWork similar as 'maxyticks' and 'minyticks'. Of course, only for a xyplot.\n\n'integerticksonly'\nSpecifies how to draw the x- and y-ticks: as floating point ('false', '0') or as integer\nnumbers ('true', 1). Default: 'false'\n\n'skipintticks'\nIf 'integerticksonly' was set to 'true' the labels and ticks will be drawn every nth tick.\nOf course in horizontalBars it affects the x-axis. Default to 1, no skipping.\n\n'precision'\nSets the number of numerals after the decimal point. Affects in most cases the y-axis. But\nalso the x-axis if 'xyplot' was set and also the labels in a pie chart. Defaults to 3.\n\n'maxval'\nSets the maximum y-value on the graph, overriding the normal auto-scaling. Default is undef.\n\n'minval'\nSets the minimum y-value on the graph, overriding the normal auto-scaling. Default is undef.\n\nCaution should be used when setting 'maxval' and 'minval' to floating point or non-round\nnumbers. This is because the scale must start & end on a tick, ticks must have round-number\nintervals, and include round numbers.\n\nExample: Suppose your data set has a range of 35-114 units. If you specify them as the\n'minval' & 'maxval', the yaxis will be plotted with 80 ticks every 1 unit.. If no\n'minval' & 'maxval', the system will auto scale the range to 30-120 with 10 ticks every 10\nunits.\n\nIf the 'minval' & 'maxval' are specified to excessive precision, they may be overridden by\nthe system, plotting a maximum 'maxyticks' ticks.\n\n'includezero'\nIf 'true', forces the y-axis to include zero if it is not in the dataset range. Default is\n'false'.\n\nIn general, it is better to use this, than to set the 'minval' if that is all you want to\nachieve.\n\n'ptsize'\nSets the radius of the points (for Chart::Points, etc.) in pixels. Default is 18.\n\n'brushsize'\nSets the width of the lines (for Chart::Lines, etc.) in pixels. Default is 6.\n\n'brushStyle'\nSets the shape of points for Chart::Points, Chart::LinesPoints. The possibilities are\n'FilledCircle', 'circle', 'donut', 'OpenCircle', 'fatPlus', 'triangle',\n'upsidedownTriangle', 'square', 'hollowSquare', 'OpenRectangle', 'FilledDiamond',\n'OpenDiamond', 'Star', 'OpenStar'. Default: 'FilledCircle\n\n'skipxticks'\nSets the number of x-ticks and x-tick labels to skip. (ie. if 'skipxticks' was set to 4,\nChart would draw every 4th x-tick and x-tick label). Default is undef.\n\n'customxticks'\nUsed in points, lines, linespoints, errorbars and bars charts, this option allows you to you\nto specify exactly which x-ticks and x-tick labels should be drawn. It should be assigned a\nreference to an array of desired ticks. Just remember that I'm counting from the 0th element\nof the array. (ie., if 'customxticks' is assigned [0,3,4], then the 0th, 3rd, and 4th\nx-ticks will be displayed)\n\n'fxtick'\nNeeds a reference to a function which uses the x-tick labels generated by the '@data[0]' as\nthe argument. The result of this function can reformat the labels. For instance\n\n$obj -> set ('fxtick' => \\&formatter );\n\nAn example for the function formatter: x labels are seconds since an event. The referenced\nfunction can transform this seconds to hour, minutes and seconds.\n\n'fytick'\nThe same situation as for 'fxtick' but now used for y labels.\n\n'colors'\nThis option lets you control the colors the chart will use. It takes a reference to a hash.\nThe hash should contain keys mapped to references to arrays of rgb values. For instance,\n\n$obj->set('colors' => {'background' => [255,255,255]});\n\nsets the background color to white (which is the default). Valid keys for this hash are\n\n'background' (background color for the png)\n'title' (color of the title)\n'text' (all the text in the chart)\n'xlabel' (color of the x-axis label)\n'ylabel' (color of the first y axis label)\n'ylabel2' (color of the second y axis label)\n'gridlines' (color of the grid lines)\n'xgridlines' (color of the x grid lines - for x axis ticks)\n'ygridlines' (color of the y grid lines - for to left y axis ticks)\n'y2gridlines' (color of the y2 grid lines - for right y axis ticks)\n'dataset0'..'dataset63' (the different datasets)\n'misc' (everything else, ie. ticks, box around the legend)\n\nNB. For composite charts, there is a limit of 8 datasets per component. The colors for\n'dataset8' through 'dataset15' become the colors for 'dataset0' through 'dataset7' for the\nsecond component chart.\n\n'titlefont'\nThis option changes the font of the title. The key has to be a GD font. eg. GD::Font->Large\n\n'labelfont'\nThis option changes the font of the labels. The key has to be a GD font.\n\n'legendfont'\nThis option changes the font of the text in the legend. The key has to be a GD font.\n\n'ticklabelfont'\nThis is the font for the tick labels. It also needs a GD font object as an argument.\n\n'greybackground'\nPuts a nice soft grey background on the actual data plot when set to 'true'. Default is\n'true'.\n\n'yaxes'\nTells Chart where to place the y-axis. Has no effect on Composite and Pie. Valid values are\n'left', 'right' and 'both'. Defaults to 'left'.\n\n'xgridlines'\nDraws grid lines matching up to x ticks if set to 'true'. Default is false.\n\n'ygridlines'\nDraws grid lines matching up to y ticks if set to 'true'. Default is false.\n\n'gridlines'\nDraws grid lines matching up to x and y ticks.\n\n'spacedbars'\nLeaves space between the groups of bars at each data point when set to 'true'. This just\nmakes it easier to read a bar chart. Default is 'true'.\n\n'imagemap'\nLets Chart know you're going to ask for information about the placement of the data for use\nin creating an image map from the png. This information can be retrieved using the\nimagemapdump() method. NB. that the imagemapdump() method cannot be called until after the\nChart has been generated (ie. using the png() or cgipng() methods).\n\n'sort'\nIn a xy-plot, the data will be sorted ascending if set to 'true'. (Should be set if the data\nisn't sorted, especially in Lines, Split and LinesPoints) In a Pareto Chart the data will be\nsorted descending. Defaults to 'false'.\n\n'compositeinfo'\nThis option is only used for composite charts. It contains the information about which types\nto use for the two component charts, and which datasets belong to which component chart. It\nshould be a reference to an array of array references, containing information like the\nfollowing\n\n$obj->set ('compositeinfo' => [ ['Bars', [1,2]],\n['Lines', [3,4] ] ]);\n\nThis example would set the two component charts to be a bar chart and a line chart. It would\nuse the first two data sets for the bar chart (note that the numbering starts at 1, not zero\nlike most of the other numbered things in Chart), and the second two data sets for the line\nchart. The default is undef.\n\nNB. Chart::Composite can only do two component charts.\n\n'minval1', 'minval2'\nOnly for composite charts, these options specify the minimum y-value for the first and\nsecond components respectively. Both default to undef.\n\n'maxval1', 'maxval2'\nOnly for composite charts, these options specify the maximum y-value for the first and\nsecond components respectively. Both default to undef.\n\n'ylabel2'\nThe label for the right y-axis (the second component chart) on a composite chart. Default is\nundef.\n\n'yticks1', 'yticks2'\nThe number of y ticks to use on the first and second y-axis on a composite chart. Please\nnote that if you just set the 'yticks' option, both axes will use that number of y ticks.\nBoth default to undef.\n\n'fyticks1', 'fyticks2'\nOnly for composite charts, needs a reference to a function which has one argument and has to\nreturn a string which labels the first resp. second y axis. Both default to undef.\n\n'sameyaxes'\nForces both component charts in a composite chart to use the same maximum and minimum\ny-values if set to 'true'. This helps to keep the composite charts from being too confusing.\nDefault is undef.\n\n'nocache'\nAdds Pragma: no-cache to the http header. Be careful with this one, as Netscape 4.5 is\nunfriendly with POST using this method.\n\n'legendexamplesize'\nSets the length of the example line in the legend in pixels. Defaults to 20.\n\n'sameerror'\nThis is a option only for ErrorBars. It tells chart that you want use the same error value\nof a data point if set to 'true'. Look at the documentation to see how the module ErrorBars\nworks. Default: 'false'.\n\n'skipyticks'\nDoes the same for the y-axis at a HorizontalBars chart as 'skipxticks' does for other\ncharts. Defaults to 1.\n\n'labelvalues'\nTells a pie chart what labels to draw beside the pie. Valid values are 'percent', 'value',\n'both' and 'none'. Defaults to 'percent'.\n\n'legendlabelvalues'\nTells a pie chart what labels to draw in the legend. Valid values are 'percent', 'value',\n'both' and 'none'. Defaults to 'value'.\n\n'start'\nRequired value for a split chart. Sets the start value of the first interval. If the x\ncoordinate of the first data point is zero, you should 'set' to zero. Default is 'undef'.\n\n'interval'\nAlso a required value for a split chart. It sets the interval of one line to plot. Defaults\n'undef'.\n\n'intervalticks'\nSets the number of ticks for the x-axis of a Split chart. Defaults to 5.\n\n'scale'\nEvery y-value of a split chart will be multiplied with that value, but the scale won't\nchange. Which means that split allows one to overdraw certain rows! Only useful if you want\nto give prominence to the maximal amplitudes of the data. Defaults to 1.\n\n'point'\nIndicates to draw points in a direction chart. 'true' or 'false' possible. Defaults to\n'true'.\n\n'line'\nIf you turn this option to 'true', then direction will connect the points with lines.\nDefaults to 'false'.\n\n'arrow'\nThis is also an option for the direction module. If set to 'true', chart will draw a arrow\nfrom the center to the point. Defaults to 'false'.\n\n'angleinterval'\nThis option tells direction, how many angle lines should be drawn. The default value is 30,\nwhich means that a line will be drawn every 30 degrees. Valid Values are: 0, 5, 10, 15, 20,\n30, 45 and 60. If you choose 0, direction will draw no line.\n\n'mincircles'\nSets the minimum number of circles when generating a scale for direction. Default is 4,\nminimum is 2.\n\n'maxcircles'\nSets the maximum number of circles when generating a scale for direction. Default is 100.\nThis limit is used to avoid plotting an unreasonable large number of ticks if non-round\nvalues are used for the minval and maxval.\n\n'pairs'\nOnly used for direction how to handle more datasets. If 'pairs' is set to 'true', Chart uses\nthe first dataset as a set of degrees and the second dataset as a set of values. Then, the\nthird set is a set of degrees and the fourth a set of values \\dots. \\\\ If 'pairs' is set to\n'false', Chart uses the first dataset as a set of angels and all following datasets as sets\nof values. Defaults to 'false'.\n\nSets the maximum number of circles when generating a scale for direction. Default is 100.\nThis limit is used to avoid plotting an unreasonable large number of ticks if non-round\nvalues are used for the minval and maxval.\n\nGIFgraph.pm-style API\nSending the image to a file\nInvoking the png method causes the graph to be plotted and saved to a file. It takes the\nname of the output file and a reference to the data as arguments. For example,\n\n$obj->png (\"foo.png\", \\@data);\n\nwould plot the data in @data, and the save the image to foo.png. Of course, this then\nbeggars the question \"What should @data look like?\". Well, just like GIFgraph, @data should\ncontain references to arrays of data, with the first array reference pointing to an array of\nx-tick labels. For example,\n\n@data = ( [ 'foo', 'bar', 'junk' ],\n[ 30.2,  23.5,  92.1   ] );\n\nwould set up a graph with one dataset, and three data points in that set. In general, the\n@data array should look something like\n\n@data = ( \\@xticklabels, \\@dataset1, ... , \\@datasetn );\n\nAnd no worries, I make my own internal copy of the data, so that it doesn't mess with yours.\n\nCGI and Chart\nOkay, so you're probably thinking, \"Do I always have to save these images to disk? What if I\nwant to use Chart to create dynamic images for my web site?\" Well, here's the answer to\nthat.\n\n$obj->cgipng ( \\@data );\n\nThe cgipng method will print the chart, along with the appropriate http header, to stdout,\nallowing you to call chart-generating scripts directly from your html pages (ie. with a\n<lt>img src=image.pl<gt> HTML tag). The @data array should be set up the same way as for the\nnormal png method.\n"
                },
                {
                    "name": "Graph.pm-style API",
                    "content": "You might ask, \"But what if I just want to add a few points to the graph, and then display it,\nwithout all those references to references?\". Well, friend, the solution is simple. Borrowing\nthe addpt idea from Matt Kruse's Graph module, you simply make a few calls to the addpt\nmethod, like so:\n\n$obj->addpt ('foo', 30, 25);\n$obj->addpt ('bar', 16, 32);\n\nOr, if you want to be able to add entire datasets, simply use the adddataset method:\n\n$obj->adddataset ('foo', 'bar');\n$obj->adddataset (30, 16);\n$obj->adddataset (25, 32);\n\nThese methods check to make sure that the points and datasets you are adding are the same size\nas the ones already there. So, if you have two datasets currently stored, and try to add a data\npoint with three different values, it will carp (per the Carp module) an error message.\nSimilarly, if you try to add a dataset with 4 data points, and all the other datasets have 3\ndata points, it will carp an error message.\n\nDon't forget, when using this API, that I treat the first dataset as a series of x-tick labels.\nSo, in the above examples, the graph would have two x-ticks, labeled 'foo' and 'bar', each with\ntwo data points. Pie and ErrorBars handle it different, look at the documentation to see how it\nworks.\n\nAdding a datafile\nYou can also add a complete datafile to a chart object. Just use the adddatafile() method.\n\n$obj->adddatafile('file', 'set' or 'pt');\n\nfile can be the name of the data file or a filehandle. 'set' or 'pt is the type of the\ndatafile. If the parameter is 'set' then each line in the data file has to be a complete\ndata set. The value of the set has to be separated by white spaces. For example the file\nlooks like this:\n\n'foo'  'bar'\n30     16\n25     32\n\nIf the parameter is 'pt', one line has to include all values of one data point separated by\nwhite spaces. For example:\n\n'foo'  30  25\n'bar'  16  32\n\nClearing the data\nA simple call to the cleardata method empties any values that may have been entered.\n\n$obj->cleardata ();\n\nGetting a copy of the data\nIf you want a copy of the data that has been added so far, make a call to the getdata\nmethod like so:\n\n$dataref = $obj->getdata;\n\nIt returns (you guessed it!) a reference to an array of references to datasets. So the\nx-tick labels would be stored as\n\n@xlabels = @{$dataref->[0]};\n\nSending the image to a file\nIf you just want to print this chart to a file, all you have to do is pass the name of the\nfile to the png() method.\n\n$obj->png (\"foo.png\");\n\nSending the image to a filehandle\nIf you want to do something else with the image, you can also pass a filehandle (either a\ntypeglob or a FileHandle object) to png, and it will print directly to that.\n\n$obj->png ($filehandle);\n$obj->png (FILEHANDLE);\n\nCGI and Chart\nOkay, so you're probably thinking (again), \"Do I always have to save these images to disk?\nWhat if I want to use Chart to create dynamic images for my web site?\" Well, here's the\nanswer to that.\n\n$obj->cgipng ();\n\nThe cgipng method will print the chart, along with the appropriate http header, to stdout,\nallowing you to call chart-generating scripts directly from your html pages (ie. with a\n<lt>img src=image.pl<gt> HTML tag).\n\nProduce a png image as a scalar\nLike scalarjpeg() the image is produced as a scalar so that the programmer-user can do\nwhatever the heck s/he wants to with it:\n\n$obj-scalarpng($dataref)\n\nProduce a jpeg image as a scalar\nLike scalarpng() the image is produced as a scalar so that the programmer-user can do\nwhatever the heck s/he wants to with it:\n\n$obj-scalarjpeg($dataref)\n"
                },
                {
                    "name": "Imagemap Support",
                    "content": "Chart can also return the pixel positioning information so that you can create image maps from\nthe pngs Chart generates. Simply set the 'imagemap' option to 'true' before you generate the\npng, then call the imagemapdump() method afterwards to retrieve the information. You will be\nreturned a data structure almost identical to the @data array described above to pass the data\ninto Chart.\n\n$imagemapdata = $obj->imagemapdump ();\n\nInstead of single data values, you will be passed references to arrays of pixel information. For\nBars, HorizontalBars and StackedBars charts, the arrays will contain two x-y pairs (specifying\nthe upper left and lower right corner of the bar), like so\n\n( $x1, $y1, $x2, $y2 ) = @{ $imagemapdata->[$dataset][$datapoint] };\n\nFor Lines, Points, ErrorBars, Split and LinesPoints, the arrays will contain a single x-y pair\n(specifying the center of the point), like so\n\n( $x, $y ) = @{ $imagemapdata->[$dataset][$datapoint] };\n\nA few caveats apply here. First of all, GD treats the upper-left corner of the png as the (0,0)\npoint, so positive y values are measured from the top of the png, not the bottom. Second, these\nvalues will most likely contain long decimal values. GD, of course, has to truncate these to\nsingle pixel values. Since I don't know how GD does it, I can't truncate it the same way he\ndoes. In a worst-case scenario, this will result in an error of one pixel on your imagemap. If\nthis is really an issue, your only option is to either experiment with it, or to contact Lincoln\nStein and ask him. Third, please remember that the 0th dataset will be empty, since that's the\nplace in the @data array for the data point labels.\n"
                }
            ]
        },
        "TO DO": {
            "content": "*   Add some 3-D graphs. Include True Type Fonts\n",
            "subsections": []
        },
        "BUGS": {
            "content": "Probably quite a few, since it's been completely rewritten. As usual, please mail me with any\nbugs, patches, suggestions, comments, flames, death threats, etc.\n",
            "subsections": []
        },
        "AUTHOR": {
            "content": "David Bonner (dbonner@cs.bu.edu)\n",
            "subsections": []
        },
        "MAINTAINER": {
            "content": "Chart Group (Chart@fs.wettzell.de)\n",
            "subsections": []
        },
        "COPYRIGHT": {
            "content": "Copyright(c) 1997-1998 by David Bonner, 1999 by Peter Clark, 2001 by the Chart group at\nBKG-Wettzell. All rights reserved. This program is free software; you can redistribute it and/or\nmodify it under the same terms as Perl itself.\n",
            "subsections": []
        }
    },
    "summary": "Chart - a series of charting modules",
    "flags": [],
    "examples": [],
    "see_also": []
}