In my opinion, if you have the programming ability to quickly make a wrapper that will do what *you* want it to do and that *you* can update yourself, then I would say most definitely go this route. The base Chart API (not the Visualizations API or other Google code offerings that use the Chart API) is very simple and basic as APIs go and you'll get the best use out of the wrapper that does what you want.
~Elijah On Fri, Oct 22, 2010 at 10:22 PM, sam fox <[email protected]> wrote: > I am in two minds as to whether to alsway work direcrtly with the > Google API or to use a wrapper if that woudl simplify things. > > I won't use a wrapper which I am not confident will be continually > updated as new features are added to Google Charts. Three seemed to be > a rush of these when Goggle Charts first launched, but for most the > enthusiasm soon died off. > > I need soemthing that can be used commercially, so no GPL (although > LPGL woudl be ok, plu smost others). > > I strongly prefer POST over GET. > > It woudl be nice if the wrapper was adding some value, like > determining the axis scales basedon the data. > > Is there something that fits that bill? Shoudl I roll my own? Should I > just use the existing API? > > Thanks ina dvance for any help ... > > -- > You received this message because you are subscribed to the Google Groups > "Google Chart API" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-chart-api?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Chart API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-chart-api?hl=en.
