Making a Pie Chart

The difficulty with making a pie chart with Scribus is that, if there is a way to use the various drawing tools to do it, the programming is quite beyond anything one would want to tackle. What we need then, is a more elegant way. Fortunately, with SVGs, there is a way.

What you cannot do is draw a circle, then subdivide it, because what we really want is a series of segments like variably sized pieces of pie, each of which can have its own fill color. What I want to show in this page is the process of putting information together to make the python script you will find at the end.

SVG Specifications and Drawing Arcs
For the details and much more information about SVG specifications, check this link. The first line shows our directions. M is the command for our starting point, the center of our pie circle, and relates to a point relative to the screen origin of our SVG space -- the upper left hand corner. After this all subsequent commands will be relative ones (in this example). Next the l says to draw a line from the starting point 150 X-units, but Y stays the same. (For this first segment, we could have used the h command, which will draw a horizontal line, but we need to generalize our process, and most or all of the other segments will not have a horizontal line.)

Now we draw our arc, using the a command, which is followed by X and Y radii, each of which we have set to 150 -- if they were not equal, we would be drawing an elliptical arc. Next are three zeros, but only the middle might need to be changed for our pie chart. Since we are only specifying two points along a hypothetical circle, we need to specify whether we will take the short route or the long route around the circle. Our middle zero says to take the short route (our piece of pie is less than half the pie).

Now, the tricky part. The last two numbers (-37, -97) are the relative distances from point 2 to point 3, in Cartesian X,Y computer-display coordinates. Finally, the z at the end says to complete this shape to a closed form -- go back to point 1.

How do we figure out these relative measurements along our arc? Trigonometry.

Trigonometry Awakens
Let's think about what pie charts represent. Pie charts merely show us visually how some whole list of data values is subdivided into its components, with the size of each piece corresponding to the size of its share of the pie. So to know how big this piece should display, I need to divide it by the total size of the pie. Since the circle of our pie spans 360&deg;, our formula looks like this: angle = [(size of piece)/total] &times; 360 which gives us the angle of the circle occupied by our segment. Now if we use our cosine and sine formulas again with this obtuse angle, we will get the correct X,Y values for point 4.

Eventually, we work our way around the pie, so that we have the coordinates for all these points, making the relative calculations as we go, as you see in piechart.py. From a mathematical point-of-view, we end up with more consistent results when we calculate from the same starting point. If we made successive calculations by shifting the reference point, we are likely to see additive errors related to the slight imprecision of our calculations -- the result might be either a gap or an overlap with the final segment.

Using piechart.py
When you start piechart.py, you first get a requester asking for the filename to save to. Whatever you enter, ".svg" will be appended to your name.

Next a requester appears asking for data -- your data values from which the calculations and pie chart will be created. After you enter one number, the requester appears again and will keep reappearing until you press Enter with no entry, or enter "0" (the number).

A message box appears telling you that the file has been created.

While there is an undocumented importSVG command in Scripter, I have commented this out in the script below. The reason is that, first of all, it does not work in Scribus versions < 1.3.x, and secondly, even when it works, it creates a new page, whose dimensions are different from the current document, so it does not seem especially useful at this time. Since it's an undocumented command, there may be other parameters which might fix this behavior.

But wait! There's more!
What about a key for our piechart? Easy. Somewhere around the line lasty = 0 add this line: ykey = 25 Then just before the line lastx = nextx add these two lines: L.append('\n') ykey = ykey + 35 So now, when we run this new modified script, we get: If for some reason you may not want a key, and will simply add annotations to the pie itself, you can ungroup your SVG and delete these key elements. Alternatively, add another requester at the beginning asking if a key is desired, then turn the L.append(' statement into a conditional with an if depending on the requester response. If you are not making a key, the assignment and changes in the ykey variable do not matter.

Could there POSSIBLY be more?
Sure, but consider this your homework.

Look at this fragment from Creating a Graph, Part 2: caption = "Scale for this graph\n\n" "X: " + str(xmark) + "units/mark\n" + "Y: " caption = caption + str(ymark) + "units/mark\n" + str(xscale) + " pts/unit (X)\n" caption = caption + str(yscale) + " pts/unit (Y)" S = scribus.createText(200, 120, 150, 80) scribus.setTextColor("Blue", S)   scribus.setText(caption, S)    scribus.setTextAlignment(1, S)    scribus.setFont("Nimbus Roman No9 L Bold", S)    scribus.setFontSize(8, S) With some modifications you could add a text frame to piechart.py, giving you the numbers you added and the percentages of the total they represent, just in case you need that for your annotations. Just remember, you will print the text frame on your page, not add it to the SVG.
 * 1) These caption statements can be combined to one line