Hi Felix, BugChart

The notation shown at the "Creating a Table using JavaScript Object
Literal Notation" section of the reference  has more moving parts than
the "setValue" method.. I haven't seen that section before though,
thanks for the link..


As always, using a wrapper  implies an inherent overhead, however
small it might be..
I'm willing to sacrifice a hundred milliseconds or two if it really
eases my work.


On Jun 25, 7:16 am, Felix Halim <[email protected]> wrote:
> I think the API already provides a JavaScript object literal notation to
> speedup the performance and avoid too many calls to 
> "setValue()":http://code.google.com/apis/visualization/documentation/reference.html
>
> See section: "Example: Creating a Table using JavaScript Object Literal
> Notation"
>
> Although it's not as clean as your wrapper, I'm concerned about the
> performance overhead of using the wrapper.
>
> Felix Halim
>
> On Thu, Jun 25, 2009 at 12:46 PM, Indha-cadde <[email protected]> wrote:
>
> > While working on various projects using the API, particularly
> > motionchart and the timeline, I made this little library to ease some
> > of footwork required to generate these charts.. The library is
> > published as a opensource, have a look at it here:
>
> >http://www.smallmeans.com/data-visualizations/google-api-wrapper/
>
> > any thoughts?..
> > cheers.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Visualization 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-visualization-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to