Master list of generic options available to pass to draw method?

41 views
Skip to first unread message

David Goldsmith

unread,
Jan 25, 2018, 12:06:44 AM1/25/18
to Google Visualization API
I understand that many options only make sense for certain chart types, but other options, such as the margin between the edge of the graph (virtual) frame and the edge of where drawing actually takes place (I hope this is something one can control) seems to me to be globally applicable to all chart types: is there a "master list" of such options, i.e., their names, allowable values, and effect?  (I've been searching for about 30 minutes, to no avail.)  Thanks!

DLG

Daniel LaLiberte

unread,
Jan 25, 2018, 8:37:22 AM1/25/18
to Google Visualization API
Hi David,

We don't have such a list of all options. But a few years ago, we did a query to build such a list and found that there were no options common to all charts.  There probably should be a common core, as you suggest, but the charts have been developed over several years, some with very different purposes.

On Thu, Jan 25, 2018 at 12:06 AM, David Goldsmith <eulergau...@gmail.com> wrote:
I understand that many options only make sense for certain chart types, but other options, such as the margin between the edge of the graph (virtual) frame and the edge of where drawing actually takes place (I hope this is something one can control) seems to me to be globally applicable to all chart types: is there a "master list" of such options, i.e., their names, allowable values, and effect?  (I've been searching for about 30 minutes, to no avail.)  Thanks!

DLG

--
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 google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/17be9a76-f364-4814-a1f6-41aa21d8fa60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

David Goldsmith

unread,
Jan 25, 2018, 11:24:33 AM1/25/18
to Google Visualization API
Sounds like a major refactoring is in order; how did a premiere SW co. like Google--which reputedly has the best of the best on staff--let such a piecemeal architecture propagate?

Anyway, is there an (what is the) option to control the "buffer" between the edge of the graph and the edge of the frame? Thanks.

Daniel LaLiberte

unread,
Jan 25, 2018, 11:30:07 AM1/25/18
to Google Visualization API
Software evolution is often messy, especially as it matures.

The chartArea option specifies the width and height of the area within the graph, inside the axes.  The chartArea also has left, right, top, and bottom for specifying the sizes of those areas outside of the graph.

On Thu, Jan 25, 2018 at 11:24 AM, David Goldsmith <eulergau...@gmail.com> wrote:
Sounds like a major refactoring is in order; how did a premiere SW co. like Google--which reputedly has the best of the best on staff--let such a piecemeal architecture propagate?

Anyway, is there an (what is the) option to control the "buffer" between the edge of the graph and the edge of the frame?  Thanks.
--
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 google-visualization-api+unsub...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/023aa56b-f5e5-4290-b31d-4deab5487ecc%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

David Goldsmith

unread,
Jan 25, 2018, 11:46:44 AM1/25/18
to google-visua...@googlegroups.com
On Thu, Jan 25, 2018 at 8:30 AM 'Daniel LaLiberte' via Google Visualization API <google-visua...@googlegroups.com> wrote:
Software evolution is often messy, especially as it matures.

I'm well aware (my background is in custom software development for scientific use, in which sector essentially no pre-planning of SW architecture is, or at least has been, the norm).  I would have thought, however, that Google, given its rep, would actively strive to combat such entropy.  I guess even the best are not Second Law immune.

The chartArea option specifies the width and height of the area within the graph, inside the axes.  The chartArea also has left, right, top, and bottom for specifying the sizes of those areas outside of the graph.

Thanks, I'll give that a try (and, I guess, post whenever I can't readily find the option I want to control).

DLG


On Thu, Jan 25, 2018 at 11:24 AM, David Goldsmith <eulergau...@gmail.com> wrote:
Sounds like a major refactoring is in order; how did a premiere SW co. like Google--which reputedly has the best of the best on staff--let such a piecemeal architecture propagate?

Anyway, is there an (what is the) option to control the "buffer" between the edge of the graph and the edge of the frame?  Thanks.

--

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 google-visualizati...@googlegroups.com.

To post to this group, send email to google-visua...@googlegroups.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Google Visualization API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-visualization-api/3sgGWJDQG3I/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-visualizati...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.

Jean-Rémi Delteil

unread,
Jan 26, 2018, 4:23:44 AM1/26/18
to Google Visualization API
@David: Also the bigger the structure, the longer the project, the harder it becomes to maintain disciple.

David Goldsmith

unread,
Jan 26, 2018, 4:32:37 AM1/26/18
to Google Visualization API
"...discip[line]" while simultaneously maintaining a production schedule: it's a trade-off--one could maintain discipline as a project scales, but at the expense of development speed; unfortunately, most capitalist enterprises are incentivized to favor quantity over quality, but once again, I expect more from Google.
Reply all
Reply to author
Forward
0 new messages