playground
/
pygal
mirror of https://github.com/Kozea/pygal.git
1
0
Fork 0
Code Issues Releases Activity
Python to generate nice looking SVG graph http://pygal.org/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
13 Commits
6 Branches
24 Tags
8.5 MiB
Tree: 66500ac573
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '66500ac573'
${ noResults }
pygal/testing.py

45 lines
1.1 KiB
Raw Normal View History Unescape

Updated SVG to fix some bugs. Compatability is about 90% with Ruby version.
19 years ago
import sys, os
Added the build script. Fixed handling of a specified date interval for the x-axis in TimeSeries. It turns out, the problem was the child get_x_values was not being called because I was calling the parent get_data_values( 'x' ) explicitly in Plot.py. Generalized the data_max and data_min operations. Fixed get_time_range method to properly return both end points.
19 years ago
#sys.path.insert( 0, 'c:\documents and settings\jaraco\my documents\projects\jaraco' )
Updated SVG to fix some bugs. Compatability is about 90% with Ruby version.
19 years ago
import SVG
from SVG import Plot
reload( SVG )
reload( Plot )
Fixed more bugs. Testing now shows high correlation with Ruby code for Plot. Fixed some bugs in TimeSeries, and re-wired the date-handling so it now uses integers for the x-axis. These may be converted back to date/time later, but not unless the datetime module can handle timedelta division correctly. Even the dateutil module doesn't handle this.
19 years ago
g = Plot.Plot( {
'min_x_value': 0,
'min_y_value': 0,
'area_fill': True,
'stagger_x_labels': True,
'stagger_y_labels': True,
'show_x_guidelines': True
})
g.add_data( { 'data': [ 1, 25, 2, 30, 3, 45 ], 'title': 'foo' } )
g.add_data( { 'data': [ 1,30, 2, 31, 3, 40 ], 'title': 'foo2' } )
g.add_data( { 'data': [ .5,35, 1, 20, 3, 10.5 ], 'title': 'foo2' } )
Updated SVG to fix some bugs. Compatability is about 90% with Ruby version.
19 years ago
res = g.burn()
f = open( r'c:\sample.svg', 'w' )
f.write( res )
f.close()
Fixed more bugs. Testing now shows high correlation with Ruby code for Plot. Fixed some bugs in TimeSeries, and re-wired the date-handling so it now uses integers for the x-axis. These may be converted back to date/time later, but not unless the datetime module can handle timedelta division correctly. Even the dateutil module doesn't handle this.
19 years ago
from SVG import TimeSeries
reload( TimeSeries )
g = TimeSeries.Plot( { } )
Added the build script. Fixed handling of a specified date interval for the x-axis in TimeSeries. It turns out, the problem was the child get_x_values was not being called because I was calling the parent get_data_values( 'x' ) explicitly in Plot.py. Generalized the data_max and data_min operations. Fixed get_time_range method to properly return both end points.
19 years ago
g.timescale_divisions = '4 hours'
Fixed more bugs. Testing now shows high correlation with Ruby code for Plot. Fixed some bugs in TimeSeries, and re-wired the date-handling so it now uses integers for the x-axis. These may be converted back to date/time later, but not unless the datetime module can handle timedelta division correctly. Even the dateutil module doesn't handle this.
19 years ago
g.stagger_x_labels = True
Added the build script. Fixed handling of a specified date interval for the x-axis in TimeSeries. It turns out, the problem was the child get_x_values was not being called because I was calling the parent get_data_values( 'x' ) explicitly in Plot.py. Generalized the data_max and data_min operations. Fixed get_time_range method to properly return both end points.
19 years ago
g.x_label_format = '%d-%b'
#g.max_y_value = 200
Fixed more bugs. Testing now shows high correlation with Ruby code for Plot. Fixed some bugs in TimeSeries, and re-wired the date-handling so it now uses integers for the x-axis. These may be converted back to date/time later, but not unless the datetime module can handle timedelta division correctly. Even the dateutil module doesn't handle this.
19 years ago
g.add_data( { 'data': [ '2005-12-21T00:00:00', 20, '2005-12-22T00:00:00', 21 ], 'title': 'foo' } )
res = g.burn()
Added the build script. Fixed handling of a specified date interval for the x-axis in TimeSeries. It turns out, the problem was the child get_x_values was not being called because I was calling the parent get_data_values( 'x' ) explicitly in Plot.py. Generalized the data_max and data_min operations. Fixed get_time_range method to properly return both end points.
19 years ago
print g.field_width
print g.font_size
print g.right_font
print g.right_align
print g.get_x_labels()
Fixed more bugs. Testing now shows high correlation with Ruby code for Plot. Fixed some bugs in TimeSeries, and re-wired the date-handling so it now uses integers for the x-axis. These may be converted back to date/time later, but not unless the datetime module can handle timedelta division correctly. Even the dateutil module doesn't handle this.
19 years ago
f = open( r'c:\timeseries.py.svg', 'w' )
f.write( res )
f.close()