I initially agreed with that, but then realized that you'd need to teach a Table how to aggregate the columns, which it doesn't know how to do. The DataTable, on the other hand, knows how to perform aggregations, so adding an totals row property to the DataTable and having the Table know how to present that row might be smoother.
Either way, while my preference is for the above, I don't see anything horrible with teaching the Table how to aggregate and then adding the feature there. thanks, -- 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.
