Parand, I'm not sure it matters for small-ish tables. I've had tables up to several hundred rows and tried both schemes. The memory usage and CPU usage don't show a significant difference. But I'd be interested in knowing what the developers say is the better way.
Bob On Feb 16, 6:50 pm, Parand <[email protected]> wrote: > Hello, > > What's the recommended method for dealing with updates to data and > hence updates to the rendered chart? For example, if you have an org > chart and the user adds a node, what's the best way to update the > display (assuming no page reload)? Is the only option to re-render the > whole chart using .draw or is there an update method? > > Also, if there are major changes to the data (say, most of the rows > change), is it better to do a DataTable.removeRows followed by an > addRows, or better to throw away the old DataTable and allocate a new > one? > > In general, what's the strategy for handling updates without a page > reload? > > Best, > > Parand -- 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.
