The concerns you bring up are some of the most common ones I hear from my company's clients when we discuss using the API, so you are hardly alone.
Nominally, there is a way to access a static version of the API, but it's not recommended for deployment in a production environment. If you build your charts based on the published, stable feature list (and avoid using anything labeled as "experimental"), then you shouldn't have to worry about feature changes. On Monday, March 11, 2013 2:07:06 PM UTC-4, Stefan Falk wrote: > > Hi asgallant! > > Thank you for your response! > > Am Montag, 11. März 2013 17:47:53 UTC+1 schrieb asgallant: >> >> It is possible that changes to the API could break existing code, though >> this happens infrequently (and is usually the result of a bug rather than a >> planned feature deprecation). Announcements concerning feature deprecation >> are typically made in this forum. > > > Okay. I think this is something anyone got to life with if he uses APIs > like this one. The only thing I am afraid of is that maybe in two or three > years nothing works anymore.. and since this website is created for > students who will use it for the lecture as some kind of guide this would > not be such a great thing if changes are made which affect those parts I am > going to use. In a few years I might won't have time to maintain this page. > > >> Currently, to the best of my knowledge, there is no limit on API requests >> for the Visualization API. In any event, such a limit would apply only to >> the number of requests made to Google's servers and not to the total number >> of charts you draw per page load (the interactive charts are drawn entirely >> in javascript - you load the API only once on the page and then draw as >> many charts as you like). >> > > Alright, then this should not be a problem since there won't be so many > students who're going to use is. > > >> >> As to whether it is a good idea to use the Visualization API or not, my >> opinion is that for the combination of versatility, simplicity of use, and >> cost, you can't beat the Visualization API. There are other tools which >> are, perhaps, more powerful or more flexible, but they are either more >> complicated to implement or you have to pay for them. >> > > And exactly this is the point why I really want to use Google's API. I > didn't get much into this API but I think I judged not to fast and I really > think this one might be the fastest and easiest way to create charts and > other visualizations. > > > Though it still would be really nice if there was something like a second > interface which is guranteed to be not changing in ways that could affect > the usability. Google should know about this argument. I wonder why there > is nothing like this for people who don't want to keep an eye on what > changes are being made on the API. > -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-visualization-api?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
