8 Responses to “Release Update”

1. Greg Says:
   December 20th, 2007 at 8:08 am

   Thanks for all the work in making pygooglechart. It is generating charts for me at http://genetify.com/graphs.php?domain=genetify.com&page=%2Fgenetify%2F&rand=226389 .
   I noticed a few bugs though. The most serious is that SimpleEncoding is being selected even when the data contains floats. http://code.google.com/apis/chart/#simple . Another problem is that data needs to be scaled to the max value of the encoding. This kind of defeats the purpose of automatically selecting the encoding. There were a few other issues if you’d like to hear about them.

2. Gerald Kaszuba Says:
   December 20th, 2007 at 8:57 am

   Greg,

   I am in the process of doing automatic scaling which will fix the problems you mentioned.

   What other issues did you have?

3. Greg Says:
   December 24th, 2007 at 8:43 am

   The only other real issue I had was that setting a bar width was necessary for a bar chart when this doesn’t seem to be true in the API docs http://code.google.com/apis/chart/#bar_charts .

   As for enhancements, I think that the API is crying out for declarative layer. Charts could be configured as a JSON object. For example:

   {’title’: ‘…’, ‘width’: ‘…’, ‘height’: ‘…’,
   ‘x-axis’: {’data’: [], ‘labels’: []},
   ‘y-axis’: {’data’: [], ‘labels’: []},
   }}

   Also, I’d like to see a strip chart class for producing charts like the left-hand column at
   http://genetify.com/graphs.php?domain=genetify.com&page=%2Fgenetify%2F .

4. Jim Musil Says:
   January 9th, 2008 at 12:04 pm

   Also, on the topic of encoding. Currently, the pygooglechart module bases the encoding type based on the size of the values — eg if value > 4000, then use ExtendedEncoding.

   This doesn’t really reflect the purpose of the different encodings. It’s really irrelevant what size the numbers are, but rather how many different values there are in the data set. If you have only 5 numbers, you want to use SimpleEncoding regardless of the size of those five numbers.

   Scaling is a must, but I’d also revisit the encoding selection method.

   Thanks for the good work!

5. Mike Kent Says:
   January 26th, 2008 at 11:06 am

   Greg,

   I’m putting pygooglechart to good use, but I also ran into the problem that SimpleData is selected even when the data are decimal numbers. I’m about to hack your source code to make it select TextData instead if the max value allows it. Hope to see a new version of pygooglechart soon. Thanks for writing it.

6. Klaus B Says:
   February 22nd, 2008 at 10:58 pm

   Hello!

   Thanks for this library!

   I am currently trying to use the svn trunk version to build a XYLineChart.

   So I came to think that you misunderstood the XY data set somehow.
   With alternating values, as in your code, you would write:
   http://chart.apis.google.com/chart?cht=lxy&chs=400×300&chd=t:0,50,30,12,60,40 (which draws nothing)
   where the actual data would look like this:
   http://chart.apis.google.com/chart?cht=lxy&chs=400×300&chd=t:0,30,60|50,12,40 (which draws a nice line)

   so chd is x1,x2,x3|y1,y2,y3 instead of x1,y1,x2,y2… etc.

   I’m gonna hack this a bit. Tell you if I came up with some code.

7. Klaus B Says:
   February 22nd, 2008 at 11:13 pm

   OK, never mind. I was just being stupid.

   Everything is all right ^^

8. Gerald Kaszuba Says:
   April 26th, 2008 at 5:33 pm

   Greg,

   The declarative layer is a good idea. I’ll make a ticket for it.

Leave a Reply

Name (required)

Mail (will not be published) (required)

Website