Ah, nice suggestions!  The second idea is pretty clever, that will
work best for me.  Thanks.

Regarding the dashboards - I was under the impression that the
dashboard stuff is still new and may be a little buggy.  I chose to
build my dashboard app using the regular visualization API, and
planned to reimplement it with the dashboard API later, once they were
more mature.  Is my perception correct, or are the dashboard tools as
mature as the regular visualizaton APIs ?

thanks again for the suggestions,





On Jun 10, 11:12 am, asgallant <[email protected]> wrote:
> Oh, I see your problem now.  If it isn't already implemented or in planning,
> this should be addressed by the new chart dashboards.
>
> In the meantime, I see two potential ways to get around the problem,
> depending on how you need to use the charts:
>
> 1) If you need to draw the charts only once for a given set of data, draw
> the pie chart first, then apply the formatter and draw the table.
>
> 2) You can create your data table with the column to format in it twice.
>  Apply the formatter to one of the instances of that column, then create two
> data views: one which excludes the formatted column and one which excludes
> the unformatted column.  Draw your pie chart with the first view and the
> table with the second.
>
> The second method uses more memory than the first, but less than duplicating
> the entire dataTable object.

-- 
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