[visualization-api] Re: Introducing Frozen Google Charts

[Ibrahim Pala]

Hello,

How can we make datefilter for Weekly, Quarterly, Yearly from Contents 
Daily Date JSON or Data?

For example:
I made this and you can choose your date type but which date type you 
choose it gives always daily range:

*http://adresyazilim.com/grafik/ *

For instance:
If i choose weekly, 13-2007 between 20-2017
it should be show and give sum of week 14, week 15,... week 19 (6 value)

If i choose quarter, Q2-2007 between Q2-2018
it should be show and give sum of Q3-2007, Q4-2008, Q1-2018 (3 value)

My json data contains daily values, how can i make group or other else?

Could you please give me an example and suggestion?

Best Regards

-- 
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+unsubscr...@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/9acbbadf-14f0-43ed-85ef-70de0523c8a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[carinlynchin]

>
> Here are some screenshots tho... one showing the callback  and the google 
> loads... the other showing the results of phantomjs... the "about to load" 
> refers  to the fact that google.charts.load is about to go... the finished 
> loading refers to the fact that the page has completed loading (that code 
> is in anohter file where the phantom stuff is)
>
 



 


-- 
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+unsubscr...@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/7e19403f-1052-49ee-a22b-583fe09386b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[carinlynchin]

I would love to show you a page, but its server side. I changed it to 45 
but it still doesn't call my callback. I'm not sure whats going on.

-- 
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+unsubscr...@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/44828ab0-c288-40fd-8a0c-abb9fc2c281c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

carinlynchin, if your problem is using the gstatic loader with PhantomJS,
you should try it now with the 'upcoming' release, which is v45 at this
time.  I've just updated it to support dynamic loading, and it should work
in all variations I could think of, at least regarding what happens in the
browser.  It's still not clear to me what happens on the server-side with
PhantomJS.

If it doesn't work, I would appreciate it if you could point me to a web
page that demonstrates the problem you are seeing.  Code won't help me in
this case, since I have to see what ends up in the browser.

On Mon, Aug 15, 2016 at 12:40 PM, carinlynchin 
wrote:

> If I set a timeout of 5 -10 seconds, then manually call the
> callback...then there is no visualization so the x = new
> google.visualization.DataTable doesn't exist
>
>
> On Monday, August 15, 2016 at 12:38:33 PM UTC-4, carinlynchin wrote:
>>
>> I know this is old...but i am having the same issue. I am using PHantomJS
>> and I get to the point where I want to load google. Google variable is an
>> object, but it never calls the callback. I have a console.log inside the
>> method for the callback which never shows up which tells me it is
>> definitely not calling the callback. I know you guys were going to take
>> this offline, but did you ever find a resolution. I have been trying to get
>> this to work for days.
>>
>>
>>
>>
>> On Tuesday, July 28, 2015 at 8:11:12 AM UTC-4, Daniel LaLiberte wrote:
>>>
>>> *Introducing Frozen Google Charts*
>>>
>>> When we push out new releases of Google Charts, some of the changes are
>>> big, like entirely new chart types, but other changes are small, like
>>> enhancements to the appearance or behavior of existing charts.
>>>
>>> Many Google Chart creators fine-tune the look and feel of their charts
>>> until it's exactly what they want. Some of those users might feel more
>>> comfortable knowing that their charts will never change, regardless of what
>>> improvements we make in the future.  For those users, we're proud to
>>> announce Frozen Google Charts.
>>>
>>> To load a frozen version, you must make some small changes in how you
>>> load the Google Charts packages.  For example, here is the usual way of
>>> loading the stable version and drawing a chart:
>>>
>>> >>
>>> src="https://www.google.com/jsapi";>
>>>
>>> 
>>>
>>>google.load('visualization', '1', {packages: ['corechart']});
>>>
>>>google.setOnLoadCallback(drawChart);
>>>
>>> 
>>>
>>> You'll need to change your code to be like this (changes highlighted in
>>> bold):
>>>
>>> >>
>>> src="*https://www.gstatic.com/charts/loader.js*
>>> <https://www.gstatic.com/charts/loader.js>">
>>>
>>> 
>>>
>>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>>
>>>*google.charts.setOnLoadCallback*(drawChart);
>>> 
>>>
>>>
>>> Note that when you call google.charts.load(), you should not include
>>> the ‘visualization’ parameter, and the version number is a string.
>>> Only version ‘41’ is supported at this time, which corresponds to the
>>> current stable release, and additional frozen versions will be
>>> announced as we push out each new stable release.  More details about
>>> using the frozen version loader will be available here
>>> 
>>> .
>>>
>>>
>>> When you use a frozen version of Google Charts, all charts and features
>>> should work the same as for the stable version it was created from.  But 
>>> there
>>> are two minor, though important, limitations with loading frozen versions,
>>> which we expect to resolve in the near future.
>>>
>>>1. You can only call google.charts.load() one time.  You can instead
>>>list all the packages that you'll need in one call, so there is usually 
>>> no
>>>need to make separate calls.
>>>2. If you are using a ChartWrapper, you must explicitly load all the
>>>packages you'll need rather than relying on the ChartWrapper to
>>>automatically load them for you.
>>>
>>> We expect that frozen versions will remain available indefinitely,
>>> though we may retire frozen versions that have security concerns.  We will
>>> typically not provide support for frozen versions, except to suggest
>>> upgrading to newer versions.
>>>
>>> Even if you don't plan to use the frozen version 41, it would help us
>>> if you could try it now with your charts and please let us know if you
>>> experience any problems.
>>>
>>> --
>>> Daniel LaLiberte 
>>>   - 978-394-1058
>>> dlali...@google.com   5CC, Cambridge MA
>>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Google Visualizatio

[visualization-api] Re: Introducing Frozen Google Charts

[carinlynchin]

If I set a timeout of 5 -10 seconds, then manually call the callback...then 
there is no visualization so the x = new google.visualization.DataTable 
doesn't exist

On Monday, August 15, 2016 at 12:38:33 PM UTC-4, carinlynchin wrote:
>
> I know this is old...but i am having the same issue. I am using PHantomJS 
> and I get to the point where I want to load google. Google variable is an 
> object, but it never calls the callback. I have a console.log inside the 
> method for the callback which never shows up which tells me it is 
> definitely not calling the callback. I know you guys were going to take 
> this offline, but did you ever find a resolution. I have been trying to get 
> this to work for days. 
>
>
>
>
> On Tuesday, July 28, 2015 at 8:11:12 AM UTC-4, Daniel LaLiberte wrote:
>>
>> *Introducing Frozen Google Charts*
>>
>> When we push out new releases of Google Charts, some of the changes are 
>> big, like entirely new chart types, but other changes are small, like 
>> enhancements to the appearance or behavior of existing charts.  
>>
>> Many Google Chart creators fine-tune the look and feel of their charts 
>> until it's exactly what they want. Some of those users might feel more 
>> comfortable knowing that their charts will never change, regardless of what 
>> improvements we make in the future.  For those users, we're proud to 
>> announce Frozen Google Charts.  
>>
>> To load a frozen version, you must make some small changes in how you 
>> load the Google Charts packages.  For example, here is the usual way of 
>> loading the stable version and drawing a chart:
>>
>> >
>> src="https://www.google.com/jsapi";>
>>
>> 
>>
>>google.load('visualization', '1', {packages: ['corechart']});
>>
>>google.setOnLoadCallback(drawChart);
>>
>> 
>>
>> You'll need to change your code to be like this (changes highlighted in 
>> bold):
>>
>> >
>> src="*https://www.gstatic.com/charts/loader.js* 
>> <https://www.gstatic.com/charts/loader.js>">
>>
>> 
>>
>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>
>>*google.charts.setOnLoadCallback*(drawChart);
>> 
>>
>>
>> Note that when you call google.charts.load(), you should not include the 
>> ‘visualization’ parameter, and the version number is a string.  Only 
>> version ‘41’ is supported at this time, which corresponds to the current 
>> stable release, and additional frozen versions will be announced as we 
>> push out each new stable release.  More details about using the frozen 
>> version 
>> loader will be available here 
>> 
>> .
>>
>>
>> When you use a frozen version of Google Charts, all charts and features 
>> should work the same as for the stable version it was created from.  But 
>> there 
>> are two minor, though important, limitations with loading frozen versions, 
>> which we expect to resolve in the near future.
>>
>>1. You can only call google.charts.load() one time.  You can instead 
>>list all the packages that you'll need in one call, so there is usually 
>> no 
>>need to make separate calls. 
>>2. If you are using a ChartWrapper, you must explicitly load all the 
>>packages you'll need rather than relying on the ChartWrapper to 
>>automatically load them for you. 
>>
>> We expect that frozen versions will remain available indefinitely, though 
>> we may retire frozen versions that have security concerns.  We will 
>> typically not provide support for frozen versions, except to suggest 
>> upgrading to newer versions.
>>
>> Even if you don't plan to use the frozen version 41, it would help us if 
>> you could try it now with your charts and please let us know if you 
>> experience any problems.
>>
>> -- 
>> Daniel LaLiberte  
>>  - 978-394-1058
>> dlali...@google.com   5CC, Cambridge MA
>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>
>

-- 
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+unsubscr...@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/3f67c898-4189-43b9-9aa8-fd2d1e37aeca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[visualization-api] Re: Introducing Frozen Google Charts

[carinlynchin]

I know this is old...but i am having the same issue. I am using PHantomJS 
and I get to the point where I want to load google. Google variable is an 
object, but it never calls the callback. I have a console.log inside the 
method for the callback which never shows up which tells me it is 
definitely not calling the callback. I know you guys were going to take 
this offline, but did you ever find a resolution. I have been trying to get 
this to work for days. 




On Tuesday, July 28, 2015 at 8:11:12 AM UTC-4, Daniel LaLiberte wrote:
>
> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes are 
> big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way of 
> loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted in 
> bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include the 
> ‘visualization’ parameter, and the version number is a string.  Only 
> version ‘41’ is supported at this time, which corresponds to the current 
> stable release, and additional frozen versions will be announced as we 
> push out each new stable release.  More details about using the frozen 
> version 
> loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and features 
> should work the same as for the stable version it was created from.  But 
> there 
> are two minor, though important, limitations with loading frozen versions, 
> which we expect to resolve in the near future.
>
>1. You can only call google.charts.load() one time.  You can instead 
>list all the packages that you'll need in one call, so there is usually no 
>need to make separate calls. 
>2. If you are using a ChartWrapper, you must explicitly load all the 
>packages you'll need rather than relying on the ChartWrapper to 
>automatically load them for you. 
>
> We expect that frozen versions will remain available indefinitely, though 
> we may retire frozen versions that have security concerns.  We will 
> typically not provide support for frozen versions, except to suggest 
> upgrading to newer versions.
>
> Even if you don't plan to use the frozen version 41, it would help us if 
> you could try it now with your charts and please let us know if you 
> experience any problems.
>
> -- 
> Daniel LaLiberte  
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>

-- 
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+unsubscr...@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/3153837d-90ba-43c2-af70-83b65dace1a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[visualization-api] Re: Introducing Frozen Google Charts

[Shravan Pintu]

>
> Hai daniel could you please post example for dynamic data for pie 
> charts.because i have gone through the previous replys but couldnt find 
> out proper answer for pie chart.
>
Please explain in detail manner.


Thanks in advance 

-- 
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+unsubscr...@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/5f7baf8a-44e4-410c-b0ce-d77bd4d25a74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[visualization-api] Re: Introducing Frozen Google Charts

[EC]

Hi, Daniel-
I noticed that my charts suddenly stopped working in UNIX, but remained 
functional in Windows yesterday.  I was stumped until I saw this post 
today.  You can see my thread at:
https://groups.google.com/forum/#!topic/google-visualization-api/F1MAY5Y47ZY
Thanks!

On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>
> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes are 
> big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way of 
> loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted in 
> bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include the 
> ‘visualization’ parameter, and the version number is a string.  Only 
> version ‘41’ is supported at this time, which corresponds to the current 
> stable release, and additional frozen versions will be announced as we 
> push out each new stable release.  More details about using the frozen 
> version 
> loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and features 
> should work the same as for the stable version it was created from.  But 
> there 
> are two minor, though important, limitations with loading frozen versions, 
> which we expect to resolve in the near future.
>
>1. You can only call google.charts.load() one time.  You can instead 
>list all the packages that you'll need in one call, so there is usually no 
>need to make separate calls. 
>2. If you are using a ChartWrapper, you must explicitly load all the 
>packages you'll need rather than relying on the ChartWrapper to 
>automatically load them for you. 
>
> We expect that frozen versions will remain available indefinitely, though 
> we may retire frozen versions that have security concerns.  We will 
> typically not provide support for frozen versions, except to suggest 
> upgrading to newer versions.
>
> Even if you don't plan to use the frozen version 41, it would help us if 
> you could try it now with your charts and please let us know if you 
> experience any problems.
>
> -- 
> Daniel LaLiberte  
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>

-- 
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+unsubscr...@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/c2d43d65-4922-4751-83e8-3b5ca591dee3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Sergey]

OK, so I did some snooping around, and it appears that there was language 
autodetection, but we won't be able to support it the same way, since we do 
not have a server.

I'm not really sure how to advise you on this. We do intend to do some 
language detection for frozen versions, but it will be done on the 
client-side, so I don't know if it will work as well.

On Wednesday, November 4, 2015 at 4:08:51 PM UTC-5, Sergey wrote:
>
> So the focusTarget:'category' issue should be fixed now, with the latest 
> frozen 43 push.
>
> As for the language autodetection... Which browser/OS are you using, and 
> do you have the browser configured in any special sort of way?
>
> I'm on a Mac, and I tried to reproduce by setting Chrome's primary 
> language, and by changing my region, to no avail.
>
> On Tuesday, November 3, 2015 at 7:46:56 PM UTC-5, Frédéric Gaye wrote:
>>
>> Hi Sergey,
>>
>> Thanks.
>> I  was thinking there was an autodetection (and a bug) because see theses 
>> 2 codes. 
>>
>>
>>- The first one (old jsapi) show tooltip in my language (french) 
>>without any language indication
>>
>>
>>  https://www.google.com/jsapi?autoload={'modules':[{'name':'visualization
>> ','version':'1','packages':['corechart']}]}">
>>  
>> google.setOnLoadCallback(drawChart);
>> function drawChart() {
>>
>>   var data = new google.visualization.DataTable();
>> data.addColumn({type:'date', role:'domain'});
>> data.addColumn('number', 'Sessions');
>> data.addColumn({type:'date', role:'domain'});
>> data.addColumn('number', 'Sessions');
>>
>> data.addRows([
>> [new Date("4/11/2015"),2189,new Date("3/11/2015"),2189],
>> [new Date("4/12/2015"),2389,new Date("3/12/2015"),2536],
>> [new Date("4/13/2015"),2189,new Date("3/13/2015"),2545],
>> [new Date("4/14/2015"),2129,new Date("3/14/2015"),2390],
>>  ]);
>>   var options = {
>> focusTarget:'category',
>> legend: { position: 'none' },
>> tooltip: {textStyle:{ color: '#333', fontSize:12 }},
>>   };
>>   var chart = new 
>> google.visualization.LineChart(document.getElementById('barchart_values3'));
>>   chart.draw(data, options);
>>   }
>> 
>> 
>>
>>
>>
>>- And the second (loader.js) , need to force/add  'language': 'fr' to 
>>see tooltip in french instead of en ("by default").
>>
>>
>> https://www.gstatic.com/charts/loader.js";> 
>> google.charts.load('43', {packages: 
>> ['corechart'], *'language': 'fr'*});
>> google.charts.setOnLoadCallback(drawChart);
>>  
>>
>>   function drawChart() {
>>   var data = new google.visualization.DataTable();
>> data.addColumn({type:'date', role:'domain'});
>> data.addColumn('number', 'Sessions');
>> data.addColumn({type:'date', role:'domain'});
>> data.addColumn('number', 'Sessions');
>>
>> data.addRows([
>> [new Date("4/11/2015"),2189,new Date("3/11/2015"),2189],
>> [new Date("4/12/2015"),2389,new Date("3/12/2015"),2536],
>> [new Date("4/13/2015"),2189,new Date("3/13/2015"),2545],
>> [new Date("4/14/2015"),2129,new Date("3/14/2015"),2390],
>>  ]);
>>   var options = {
>> focusTarget:'category',
>> legend: { position: 'none' },
>> tooltip: {textStyle:{ color: '#333', fontSize:12 }},
>>   };
>>   var chart = new 
>> google.visualization.LineChart(document.getElementById('barchart_values2'));
>>   chart.draw(data, options);
>>   }
>>   
>>
>> Any idea to show in the second code a "autodetected" french language 
>> without any 'language': 'fr' ?
>>
>> Regards
>>
>> Le mardi 3 novembre 2015 15:47:29 UTC+1, Sergey a écrit :
>>>
>>> As far as I know, we have never autodetected the language/locale and 
>>> automatically loaded the correct version. So, if anything, this is not a 
>>> bug, but a feature request. We have discussed how we would do this before, 
>>> and I think we have a plan for how to proceed. However, I don't have any 
>>> estimates for when we might do this, since the browser APIs for language 
>>> detection haven't really stabilized yet.
>>>
>>> On Tue, Nov 3, 2015 at 8:46 AM Frédéric Gaye <
>>> freder...@lereferencementnaturel.org> wrote:
>>>
 Hi Sergey,

 Thanks for your (quickly) anwsers.

 Note : there another "little" but boring bug. Now with frozen 42 and 
 43, date in  tooltip are by default in english. We need to 
 add  google.charts.load('42', {packages: ['corechart'], 'language': 
 'fr'}); 
 to have date in french. Is it possible to correct this to stay like before 
 frozen (that is to say, language are automatically detected and no need to 
 force with 'language': 'fr' to have french.

 Regards

 Le lundi 2 novembre 2015 22:05:24 UTC+1, Sergey a écrit :

> Thanks for notifying us of this bug! We will fix it soon.
>
> On Mon, Nov 2, 2015 at 4:02 PM Frédéric Gaye <
> freder...@lereferencementnaturel.org> wrote:
>
 Hi Daniel,
>>
>> It seems there a bug with Forzen 43 and  use of 
>> option focusTarget:'category'.
>> When w

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Sergey]

So the focusTarget:'category' issue should be fixed now, with the latest 
frozen 43 push.

As for the language autodetection... Which browser/OS are you using, and do 
you have the browser configured in any special sort of way?

I'm on a Mac, and I tried to reproduce by setting Chrome's primary 
language, and by changing my region, to no avail.

On Tuesday, November 3, 2015 at 7:46:56 PM UTC-5, Frédéric Gaye wrote:
>
> Hi Sergey,
>
> Thanks.
> I  was thinking there was an autodetection (and a bug) because see theses 
> 2 codes. 
>
>
>- The first one (old jsapi) show tooltip in my language (french) 
>without any language indication
>
>
>  https://www.google.com/jsapi?autoload={'modules':[{'name':'visualization
> ','version':'1','packages':['corechart']}]}">
>  
> google.setOnLoadCallback(drawChart);
> function drawChart() {
>
>   var data = new google.visualization.DataTable();
> data.addColumn({type:'date', role:'domain'});
> data.addColumn('number', 'Sessions');
> data.addColumn({type:'date', role:'domain'});
> data.addColumn('number', 'Sessions');
>
> data.addRows([
> [new Date("4/11/2015"),2189,new Date("3/11/2015"),2189],
> [new Date("4/12/2015"),2389,new Date("3/12/2015"),2536],
> [new Date("4/13/2015"),2189,new Date("3/13/2015"),2545],
> [new Date("4/14/2015"),2129,new Date("3/14/2015"),2390],
>  ]);
>   var options = {
> focusTarget:'category',
> legend: { position: 'none' },
> tooltip: {textStyle:{ color: '#333', fontSize:12 }},
>   };
>   var chart = new 
> google.visualization.LineChart(document.getElementById('barchart_values3'));
>   chart.draw(data, options);
>   }
> 
> 
>
>
>
>- And the second (loader.js) , need to force/add  'language': 'fr' to 
>see tooltip in french instead of en ("by default").
>
>
> https://www.gstatic.com/charts/loader.js";> 
> google.charts.load('43', {packages: 
> ['corechart'], *'language': 'fr'*});
> google.charts.setOnLoadCallback(drawChart);
>  
>
>   function drawChart() {
>   var data = new google.visualization.DataTable();
> data.addColumn({type:'date', role:'domain'});
> data.addColumn('number', 'Sessions');
> data.addColumn({type:'date', role:'domain'});
> data.addColumn('number', 'Sessions');
>
> data.addRows([
> [new Date("4/11/2015"),2189,new Date("3/11/2015"),2189],
> [new Date("4/12/2015"),2389,new Date("3/12/2015"),2536],
> [new Date("4/13/2015"),2189,new Date("3/13/2015"),2545],
> [new Date("4/14/2015"),2129,new Date("3/14/2015"),2390],
>  ]);
>   var options = {
> focusTarget:'category',
> legend: { position: 'none' },
> tooltip: {textStyle:{ color: '#333', fontSize:12 }},
>   };
>   var chart = new 
> google.visualization.LineChart(document.getElementById('barchart_values2'));
>   chart.draw(data, options);
>   }
>   
>
> Any idea to show in the second code a "autodetected" french language 
> without any 'language': 'fr' ?
>
> Regards
>
> Le mardi 3 novembre 2015 15:47:29 UTC+1, Sergey a écrit :
>>
>> As far as I know, we have never autodetected the language/locale and 
>> automatically loaded the correct version. So, if anything, this is not a 
>> bug, but a feature request. We have discussed how we would do this before, 
>> and I think we have a plan for how to proceed. However, I don't have any 
>> estimates for when we might do this, since the browser APIs for language 
>> detection haven't really stabilized yet.
>>
>> On Tue, Nov 3, 2015 at 8:46 AM Frédéric Gaye <
>> freder...@lereferencementnaturel.org> wrote:
>>
>>> Hi Sergey,
>>>
>>> Thanks for your (quickly) anwsers.
>>>
>>> Note : there another "little" but boring bug. Now with frozen 42 and 43, 
>>> date in  tooltip are by default in english. We need to 
>>> add  google.charts.load('42', {packages: ['corechart'], 'language': 'fr'}); 
>>> to have date in french. Is it possible to correct this to stay like before 
>>> frozen (that is to say, language are automatically detected and no need to 
>>> force with 'language': 'fr' to have french.
>>>
>>> Regards
>>>
>>> Le lundi 2 novembre 2015 22:05:24 UTC+1, Sergey a écrit :
>>>
 Thanks for notifying us of this bug! We will fix it soon.

 On Mon, Nov 2, 2015 at 4:02 PM Frédéric Gaye <
 freder...@lereferencementnaturel.org> wrote:

>>> Hi Daniel,
>
> It seems there a bug with Forzen 43 and  use of 
> option focusTarget:'category'.
> When we use both, it become impossible to mouse over a barchart to see 
> the tooltip (we see tooltip only if we put our mouse next to barchat) if 
> we 
> use frozen 42 all is fine.
>
> See this simple example 
>
> https://www.gstatic.com/charts/loader.js";>
>  google.charts.load('43', 
> {packages: ['corechart'], 'language': 'fr'});
> google.charts.setOnLoadCallback(drawChart);
>  
> function drawChart() {
>var data = google.visualization.arrayToDataTable([
>  ['Canaux', '28 derniers jours', { role: 'style' }

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Frédéric Gaye]

Hi Sergey,

Thanks.
I  was thinking there was an autodetection (and a bug) because see theses 2 
codes. 


   - The first one (old jsapi) show tooltip in my language (french) without 
   any language indication
   

 https://www.google.com/jsapi?autoload={'modules':[{'name':'visualization','version':'1','packages':['corechart']}]}">
 
google.setOnLoadCallback(drawChart);
function drawChart() {

  var data = new google.visualization.DataTable();
data.addColumn({type:'date', role:'domain'});
data.addColumn('number', 'Sessions');
data.addColumn({type:'date', role:'domain'});
data.addColumn('number', 'Sessions');

data.addRows([
[new Date("4/11/2015"),2189,new Date("3/11/2015"),2189],
[new Date("4/12/2015"),2389,new Date("3/12/2015"),2536],
[new Date("4/13/2015"),2189,new Date("3/13/2015"),2545],
[new Date("4/14/2015"),2129,new Date("3/14/2015"),2390],
 ]);
  var options = {
focusTarget:'category',
legend: { position: 'none' },
tooltip: {textStyle:{ color: '#333', fontSize:12 }},
  };
  var chart = new 
google.visualization.LineChart(document.getElementById('barchart_values3'));
  chart.draw(data, options);
  }





   - And the second (loader.js) , need to force/add  'language': 'fr' to 
   see tooltip in french instead of en ("by default").
   

https://www.gstatic.com/charts/loader.js";> 
google.charts.load('43', {packages: 
['corechart'], *'language': 'fr'*});
google.charts.setOnLoadCallback(drawChart);
 

  function drawChart() {
  var data = new google.visualization.DataTable();
data.addColumn({type:'date', role:'domain'});
data.addColumn('number', 'Sessions');
data.addColumn({type:'date', role:'domain'});
data.addColumn('number', 'Sessions');

data.addRows([
[new Date("4/11/2015"),2189,new Date("3/11/2015"),2189],
[new Date("4/12/2015"),2389,new Date("3/12/2015"),2536],
[new Date("4/13/2015"),2189,new Date("3/13/2015"),2545],
[new Date("4/14/2015"),2129,new Date("3/14/2015"),2390],
 ]);
  var options = {
focusTarget:'category',
legend: { position: 'none' },
tooltip: {textStyle:{ color: '#333', fontSize:12 }},
  };
  var chart = new 
google.visualization.LineChart(document.getElementById('barchart_values2'));
  chart.draw(data, options);
  }
  

Any idea to show in the second code a "autodetected" french language 
without any 'language': 'fr' ?

Regards

Le mardi 3 novembre 2015 15:47:29 UTC+1, Sergey a écrit :
>
> As far as I know, we have never autodetected the language/locale and 
> automatically loaded the correct version. So, if anything, this is not a 
> bug, but a feature request. We have discussed how we would do this before, 
> and I think we have a plan for how to proceed. However, I don't have any 
> estimates for when we might do this, since the browser APIs for language 
> detection haven't really stabilized yet.
>
> On Tue, Nov 3, 2015 at 8:46 AM Frédéric Gaye <
> freder...@lereferencementnaturel.org > wrote:
>
>> Hi Sergey,
>>
>> Thanks for your (quickly) anwsers.
>>
>> Note : there another "little" but boring bug. Now with frozen 42 and 43, 
>> date in  tooltip are by default in english. We need to 
>> add  google.charts.load('42', {packages: ['corechart'], 'language': 'fr'}); 
>> to have date in french. Is it possible to correct this to stay like before 
>> frozen (that is to say, language are automatically detected and no need to 
>> force with 'language': 'fr' to have french.
>>
>> Regards
>>
>> Le lundi 2 novembre 2015 22:05:24 UTC+1, Sergey a écrit :
>>
>>> Thanks for notifying us of this bug! We will fix it soon.
>>>
>>> On Mon, Nov 2, 2015 at 4:02 PM Frédéric Gaye <
>>> freder...@lereferencementnaturel.org> wrote:
>>>
>> Hi Daniel,

 It seems there a bug with Forzen 43 and  use of 
 option focusTarget:'category'.
 When we use both, it become impossible to mouse over a barchart to see 
 the tooltip (we see tooltip only if we put our mouse next to barchat) if 
 we 
 use frozen 42 all is fine.

 See this simple example 

 https://www.gstatic.com/charts/loader.js";>
  google.charts.load('43', 
 {packages: ['corechart'], 'language': 'fr'});
 google.charts.setOnLoadCallback(drawChart);
  
 function drawChart() {
var data = google.visualization.arrayToDataTable([
  ['Canaux', '28 derniers jours', { role: 'style' }, { role: 
 'annotation' }, 'Période précédente'],
  ['Organic Search', 59200, '#337ab7', -3130, 58750 ],
  ['Referral', 6450, '#337ab7', -387, 6837],
  ['Direct', 5874, '#337ab7', -424, 6298 ],
  ['Social', 113, '#337ab7', -78, 191],
  ['(other)', 20, '#337ab7', 3, 17]
  ]);
   var options = {
 title: "Density of Precious Metals, in g/cm^3",
 width: 600,
 height: 400,
   focusTarget:'category',
 legend: { position: 'none' },
 tooltip: {textStyle:{ color: '#333', fontSize:12 }},
   };
   var chart = n

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Sergey Grabkovsky' via Google Visualization API]

As far as I know, we have never autodetected the language/locale and
automatically loaded the correct version. So, if anything, this is not a
bug, but a feature request. We have discussed how we would do this before,
and I think we have a plan for how to proceed. However, I don't have any
estimates for when we might do this, since the browser APIs for language
detection haven't really stabilized yet.

On Tue, Nov 3, 2015 at 8:46 AM Frédéric Gaye <
frederic.g...@lereferencementnaturel.org> wrote:

> Hi Sergey,
>
> Thanks for your (quickly) anwsers.
>
> Note : there another "little" but boring bug. Now with frozen 42 and 43,
> date in  tooltip are by default in english. We need to
> add  google.charts.load('42', {packages: ['corechart'], 'language': 'fr'});
> to have date in french. Is it possible to correct this to stay like before
> frozen (that is to say, language are automatically detected and no need to
> force with 'language': 'fr' to have french.
>
> Regards
>
> Le lundi 2 novembre 2015 22:05:24 UTC+1, Sergey a écrit :
>
>> Thanks for notifying us of this bug! We will fix it soon.
>>
>> On Mon, Nov 2, 2015 at 4:02 PM Frédéric Gaye <
>> freder...@lereferencementnaturel.org> wrote:
>>
> Hi Daniel,
>>>
>>> It seems there a bug with Forzen 43 and  use of
>>> option focusTarget:'category'.
>>> When we use both, it become impossible to mouse over a barchart to see
>>> the tooltip (we see tooltip only if we put our mouse next to barchat) if we
>>> use frozen 42 all is fine.
>>>
>>> See this simple example
>>>
>>> https://www.gstatic.com/charts/loader.js";>
>>>  google.charts.load('43',
>>> {packages: ['corechart'], 'language': 'fr'});
>>> google.charts.setOnLoadCallback(drawChart);
>>>
>>> function drawChart() {
>>>var data = google.visualization.arrayToDataTable([
>>>  ['Canaux', '28 derniers jours', { role: 'style' }, { role: 'annotation'
>>> }, 'Période précédente'],
>>>  ['Organic Search', 59200, '#337ab7', -3130, 58750 ],
>>>  ['Referral', 6450, '#337ab7', -387, 6837],
>>>  ['Direct', 5874, '#337ab7', -424, 6298 ],
>>>  ['Social', 113, '#337ab7', -78, 191],
>>>  ['(other)', 20, '#337ab7', 3, 17]
>>>  ]);
>>>   var options = {
>>> title: "Density of Precious Metals, in g/cm^3",
>>> width: 600,
>>> height: 400,
>>>   focusTarget:'category',
>>> legend: { position: 'none' },
>>> tooltip: {textStyle:{ color: '#333', fontSize:12 }},
>>>   };
>>>   var chart = new
>>> google.visualization.BarChart(document.getElementById('barchart_values2'));
>>>   chart.draw(data, options);
>>>   }
>>>   
>>> 
>>>
>>> Any idea to correct this point ?
>>>
>>> Regards
>>>
>>> Le mardi 28 juillet 2015 14:11:12 UTC+2, Daniel LaLiberte a écrit :
>>>
 *Introducing Frozen Google Charts*

 When we push out new releases of Google Charts, some of the changes are
 big, like entirely new chart types, but other changes are small, like
 enhancements to the appearance or behavior of existing charts.

 Many Google Chart creators fine-tune the look and feel of their charts
 until it's exactly what they want. Some of those users might feel more
 comfortable knowing that their charts will never change, regardless of what
 improvements we make in the future.  For those users, we're proud to
 announce Frozen Google Charts.

 To load a frozen version, you must make some small changes in how you
 load the Google Charts packages.  For example, here is the usual way
 of loading the stable version and drawing a chart:

 >>>
 src="https://www.google.com/jsapi";>

 

google.load('visualization', '1', {packages: ['corechart']});

google.setOnLoadCallback(drawChart);

 

 You'll need to change your code to be like this (changes highlighted
 in bold):

 >>>
 src="*https://www.gstatic.com/charts/loader.js*
 <https://www.gstatic.com/charts/loader.js>">

 

*google.charts.load(**'41'**,* {packages: ['corechart']});

*google.charts.setOnLoadCallback*(drawChart);
 


 Note that when you call google.charts.load(), you should not include
 the ‘visualization’ parameter, and the version number is a string.
 Only version ‘41’ is supported at this time, which corresponds to the
 current stable release, and additional frozen versions will be
 announced as we push out each new stable release.  More details about
 using the frozen version loader will be available here
 
 .


 When you use a frozen version of Google Charts, all charts and
 features should work the same as for

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Frédéric Gaye]

Hi Sergey,

Thanks for your (quickly) anwsers.

Note : there another "little" but boring bug. Now with frozen 42 and 43, 
date in  tooltip are by default in english. We need to 
add  google.charts.load('42', {packages: ['corechart'], 'language': 'fr'}); 
to have date in french. Is it possible to correct this to stay like before 
frozen (that is to say, language are automatically detected and no need to 
force with 'language': 'fr' to have french.

Regards

Le lundi 2 novembre 2015 22:05:24 UTC+1, Sergey a écrit :
>
> Thanks for notifying us of this bug! We will fix it soon.
>
> On Mon, Nov 2, 2015 at 4:02 PM Frédéric Gaye <
> freder...@lereferencementnaturel.org > wrote:
>
>> Hi Daniel,
>>
>> It seems there a bug with Forzen 43 and  use of 
>> option focusTarget:'category'.
>> When we use both, it become impossible to mouse over a barchart to see 
>> the tooltip (we see tooltip only if we put our mouse next to barchat) if we 
>> use frozen 42 all is fine.
>>
>> See this simple example 
>>
>> https://www.gstatic.com/charts/loader.js";>
>>  google.charts.load('43', 
>> {packages: ['corechart'], 'language': 'fr'});
>> google.charts.setOnLoadCallback(drawChart);
>>  
>> function drawChart() {
>>var data = google.visualization.arrayToDataTable([
>>  ['Canaux', '28 derniers jours', { role: 'style' }, { role: 'annotation' 
>> }, 'Période précédente'],
>>  ['Organic Search', 59200, '#337ab7', -3130, 58750 ],
>>  ['Referral', 6450, '#337ab7', -387, 6837],
>>  ['Direct', 5874, '#337ab7', -424, 6298 ],
>>  ['Social', 113, '#337ab7', -78, 191],
>>  ['(other)', 20, '#337ab7', 3, 17]
>>  ]);
>>   var options = {
>> title: "Density of Precious Metals, in g/cm^3",
>> width: 600,
>> height: 400,
>>   focusTarget:'category',
>> legend: { position: 'none' },
>> tooltip: {textStyle:{ color: '#333', fontSize:12 }},
>>   };
>>   var chart = new 
>> google.visualization.BarChart(document.getElementById('barchart_values2'));
>>   chart.draw(data, options);
>>   }
>>   
>> 
>>
>> Any idea to correct this point ?
>>
>> Regards
>>
>> Le mardi 28 juillet 2015 14:11:12 UTC+2, Daniel LaLiberte a écrit :
>>
>>> *Introducing Frozen Google Charts*
>>>
>>> When we push out new releases of Google Charts, some of the changes are 
>>> big, like entirely new chart types, but other changes are small, like 
>>> enhancements to the appearance or behavior of existing charts.  
>>>
>>> Many Google Chart creators fine-tune the look and feel of their charts 
>>> until it's exactly what they want. Some of those users might feel more 
>>> comfortable knowing that their charts will never change, regardless of what 
>>> improvements we make in the future.  For those users, we're proud to 
>>> announce Frozen Google Charts.  
>>>
>>> To load a frozen version, you must make some small changes in how you 
>>> load the Google Charts packages.  For example, here is the usual way of 
>>> loading the stable version and drawing a chart:
>>>
>>> >>
>>> src="https://www.google.com/jsapi";>
>>>
>>> 
>>>
>>>google.load('visualization', '1', {packages: ['corechart']});
>>>
>>>google.setOnLoadCallback(drawChart);
>>>
>>> 
>>>
>>> You'll need to change your code to be like this (changes highlighted in 
>>> bold):
>>>
>>> >>
>>> src="*https://www.gstatic.com/charts/loader.js* 
>>> <https://www.gstatic.com/charts/loader.js>">
>>>
>>> 
>>>
>>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>>
>>>*google.charts.setOnLoadCallback*(drawChart);
>>> 
>>>
>>>
>>> Note that when you call google.charts.load(), you should not include 
>>> the ‘visualization’ parameter, and the version number is a string.  
>>> Only version ‘41’ is supported at this time, which corresponds to the 
>>> current stable release, and additional frozen versions will be 
>>> announced as we push out each new stable release.  More details about 
>>> using the frozen version loader will be available here 
>>> 
>>> .
>>>
>>>
>>> When you use a frozen version of Google Charts, all charts and features 
>>> should work the same as for the stable version it was created from.  But 
>>> there 
>>> are two minor, though important, limitations with loading frozen versions, 
>>> which we expect to resolve in the near future.
>>>
>>>1. You can only call google.charts.load() one time.  You can instead 
>>>list all the packages that you'll need in one call, so there is usually 
>>> no 
>>>need to make separate calls. 
>>>2. If you are using a ChartWrapper, you must explicitly load all the 
>>>packages you'll need rather than relying on the ChartWrapper to 
>>>automatically load them for you. 
>>>
>>> W

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Sergey Grabkovsky' via Google Visualization API]

Thanks for notifying us of this bug! We will fix it soon.

On Mon, Nov 2, 2015 at 4:02 PM Frédéric Gaye <
frederic.g...@lereferencementnaturel.org> wrote:

> Hi Daniel,
>
> It seems there a bug with Forzen 43 and  use of
> option focusTarget:'category'.
> When we use both, it become impossible to mouse over a barchart to see the
> tooltip (we see tooltip only if we put our mouse next to barchat) if we use
> frozen 42 all is fine.
>
> See this simple example
>
> https://www.gstatic.com/charts/loader.js";>
>  google.charts.load('43', {packages:
> ['corechart'], 'language': 'fr'});
> google.charts.setOnLoadCallback(drawChart);
>
> function drawChart() {
>var data = google.visualization.arrayToDataTable([
>  ['Canaux', '28 derniers jours', { role: 'style' }, { role: 'annotation'
> }, 'Période précédente'],
>  ['Organic Search', 59200, '#337ab7', -3130, 58750 ],
>  ['Referral', 6450, '#337ab7', -387, 6837],
>  ['Direct', 5874, '#337ab7', -424, 6298 ],
>  ['Social', 113, '#337ab7', -78, 191],
>  ['(other)', 20, '#337ab7', 3, 17]
>  ]);
>   var options = {
> title: "Density of Precious Metals, in g/cm^3",
> width: 600,
> height: 400,
>   focusTarget:'category',
> legend: { position: 'none' },
> tooltip: {textStyle:{ color: '#333', fontSize:12 }},
>   };
>   var chart = new
> google.visualization.BarChart(document.getElementById('barchart_values2'));
>   chart.draw(data, options);
>   }
>   
> 
>
> Any idea to correct this point ?
>
> Regards
>
> Le mardi 28 juillet 2015 14:11:12 UTC+2, Daniel LaLiberte a écrit :
>
>> *Introducing Frozen Google Charts*
>>
>> When we push out new releases of Google Charts, some of the changes are
>> big, like entirely new chart types, but other changes are small, like
>> enhancements to the appearance or behavior of existing charts.
>>
>> Many Google Chart creators fine-tune the look and feel of their charts
>> until it's exactly what they want. Some of those users might feel more
>> comfortable knowing that their charts will never change, regardless of what
>> improvements we make in the future.  For those users, we're proud to
>> announce Frozen Google Charts.
>>
>> To load a frozen version, you must make some small changes in how you
>> load the Google Charts packages.  For example, here is the usual way of
>> loading the stable version and drawing a chart:
>>
>> >
>> src="https://www.google.com/jsapi";>
>>
>> 
>>
>>google.load('visualization', '1', {packages: ['corechart']});
>>
>>google.setOnLoadCallback(drawChart);
>>
>> 
>>
>> You'll need to change your code to be like this (changes highlighted in
>> bold):
>>
>> >
>> src="*https://www.gstatic.com/charts/loader.js*
>> <https://www.gstatic.com/charts/loader.js>">
>>
>> 
>>
>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>
>>*google.charts.setOnLoadCallback*(drawChart);
>> 
>>
>>
>> Note that when you call google.charts.load(), you should not include the
>> ‘visualization’ parameter, and the version number is a string.  Only
>> version ‘41’ is supported at this time, which corresponds to the current
>> stable release, and additional frozen versions will be announced as we
>> push out each new stable release.  More details about using the frozen 
>> version
>> loader will be available here
>> 
>> .
>>
>>
>> When you use a frozen version of Google Charts, all charts and features
>> should work the same as for the stable version it was created from.  But 
>> there
>> are two minor, though important, limitations with loading frozen versions,
>> which we expect to resolve in the near future.
>>
>>1. You can only call google.charts.load() one time.  You can instead
>>list all the packages that you'll need in one call, so there is usually no
>>need to make separate calls.
>>2. If you are using a ChartWrapper, you must explicitly load all the
>>packages you'll need rather than relying on the ChartWrapper to
>>automatically load them for you.
>>
>> We expect that frozen versions will remain available indefinitely, though
>> we may retire frozen versions that have security concerns.  We will
>> typically not provide support for frozen versions, except to suggest
>> upgrading to newer versions.
>>
>> Even if you don't plan to use the frozen version 41, it would help us if
>> you could try it now with your charts and please let us know if you
>> experience any problems.
>>
>> --
>>
> Daniel LaLiberte 
>>  - 978-394-1058
>> dlali...@google.com   5CC, Cambridge MA
>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>
> --
> You received this message because you 

[visualization-api] Re: Introducing Frozen Google Charts

[Frédéric Gaye]

Hi Daniel,

It seems there a bug with Forzen 43 and  use of 
option focusTarget:'category'.
When we use both, it become impossible to mouse over a barchart to see the 
tooltip (we see tooltip only if we put our mouse next to barchat) if we use 
frozen 42 all is fine.

See this simple example 

https://www.gstatic.com/charts/loader.js";>
 google.charts.load('43', {packages: 
['corechart'], 'language': 'fr'});
google.charts.setOnLoadCallback(drawChart);
 
function drawChart() {
   var data = google.visualization.arrayToDataTable([
 ['Canaux', '28 derniers jours', { role: 'style' }, { role: 'annotation' }, 
'Période précédente'],
 ['Organic Search', 59200, '#337ab7', -3130, 58750 ],
 ['Referral', 6450, '#337ab7', -387, 6837],
 ['Direct', 5874, '#337ab7', -424, 6298 ],
 ['Social', 113, '#337ab7', -78, 191],
 ['(other)', 20, '#337ab7', 3, 17]
 ]);
  var options = {
title: "Density of Precious Metals, in g/cm^3",
width: 600,
height: 400,
  focusTarget:'category',
legend: { position: 'none' },
tooltip: {textStyle:{ color: '#333', fontSize:12 }},
  };
  var chart = new 
google.visualization.BarChart(document.getElementById('barchart_values2'));
  chart.draw(data, options);
  }
  


Any idea to correct this point ?

Regards

Le mardi 28 juillet 2015 14:11:12 UTC+2, Daniel LaLiberte a écrit :
>
> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes are 
> big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way of 
> loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted in 
> bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include the 
> ‘visualization’ parameter, and the version number is a string.  Only 
> version ‘41’ is supported at this time, which corresponds to the current 
> stable release, and additional frozen versions will be announced as we 
> push out each new stable release.  More details about using the frozen 
> version 
> loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and features 
> should work the same as for the stable version it was created from.  But 
> there 
> are two minor, though important, limitations with loading frozen versions, 
> which we expect to resolve in the near future.
>
>1. You can only call google.charts.load() one time.  You can instead 
>list all the packages that you'll need in one call, so there is usually no 
>need to make separate calls. 
>2. If you are using a ChartWrapper, you must explicitly load all the 
>packages you'll need rather than relying on the ChartWrapper to 
>automatically load them for you. 
>
> We expect that frozen versions will remain available indefinitely, though 
> we may retire frozen versions that have security concerns.  We will 
> typically not provide support for frozen versions, except to suggest 
> upgrading to newer versions.
>
> Even if you don't plan to use the frozen version 41, it would help us if 
> you could try it now with your charts and please let us know if you 
> experience any problems.
>
> -- 
> Daniel LaLiberte  
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegr

[visualization-api] Re: Introducing Frozen Google Charts

[Julian Claus]

I replaced "corechart" with "line" and it finally worked!

Am Donnerstag, 22. Oktober 2015 08:28:43 UTC+2 schrieb Julian Claus:
>
> I get the error:
>
> *Uncaught TypeError: google.charts.Line is not a function*
>
> I did the following:
>
>
> 
>
>
> Am Dienstag, 28. Juli 2015 14:11:12 UTC+2 schrieb Daniel LaLiberte:
>>
>> *Introducing Frozen Google Charts*
>>
>> When we push out new releases of Google Charts, some of the changes are 
>> big, like entirely new chart types, but other changes are small, like 
>> enhancements to the appearance or behavior of existing charts.  
>>
>> Many Google Chart creators fine-tune the look and feel of their charts 
>> until it's exactly what they want. Some of those users might feel more 
>> comfortable knowing that their charts will never change, regardless of what 
>> improvements we make in the future.  For those users, we're proud to 
>> announce Frozen Google Charts.  
>>
>> To load a frozen version, you must make some small changes in how you 
>> load the Google Charts packages.  For example, here is the usual way of 
>> loading the stable version and drawing a chart:
>>
>> >
>> src="https://www.google.com/jsapi";>
>>
>> 
>>
>>google.load('visualization', '1', {packages: ['corechart']});
>>
>>google.setOnLoadCallback(drawChart);
>>
>> 
>>
>> You'll need to change your code to be like this (changes highlighted in 
>> bold):
>>
>> >
>> src="*https://www.gstatic.com/charts/loader.js* 
>> <https://www.gstatic.com/charts/loader.js>">
>>
>> 
>>
>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>
>>*google.charts.setOnLoadCallback*(drawChart);
>> 
>>
>>
>> Note that when you call google.charts.load(), you should not include the 
>> ‘visualization’ parameter, and the version number is a string.  Only 
>> version ‘41’ is supported at this time, which corresponds to the current 
>> stable release, and additional frozen versions will be announced as we 
>> push out each new stable release.  More details about using the frozen 
>> version 
>> loader will be available here 
>> 
>> .
>>
>>
>> When you use a frozen version of Google Charts, all charts and features 
>> should work the same as for the stable version it was created from.  But 
>> there 
>> are two minor, though important, limitations with loading frozen versions, 
>> which we expect to resolve in the near future.
>>
>>1. You can only call google.charts.load() one time.  You can instead 
>>list all the packages that you'll need in one call, so there is usually 
>> no 
>>need to make separate calls. 
>>2. If you are using a ChartWrapper, you must explicitly load all the 
>>packages you'll need rather than relying on the ChartWrapper to 
>>automatically load them for you. 
>>
>> We expect that frozen versions will remain available indefinitely, though 
>> we may retire frozen versions that have security concerns.  We will 
>> typically not provide support for frozen versions, except to suggest 
>> upgrading to newer versions.
>>
>> Even if you don't plan to use the frozen version 41, it would help us if 
>> you could try it now with your charts and please let us know if you 
>> experience any problems.
>>
>> -- 
>> Daniel LaLiberte  
>>  - 978-394-1058
>> dlali...@google.com   5CC, Cambridge MA
>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/80e53d06-beed-4517-9c89-b52b5bbec796%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[visualization-api] Re: Introducing Frozen Google Charts

[Julian Claus]

I get the error:

*Uncaught TypeError: google.charts.Line is not a function*

I did the following:




Am Dienstag, 28. Juli 2015 14:11:12 UTC+2 schrieb Daniel LaLiberte:
>
> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes are 
> big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way of 
> loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted in 
> bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include the 
> ‘visualization’ parameter, and the version number is a string.  Only 
> version ‘41’ is supported at this time, which corresponds to the current 
> stable release, and additional frozen versions will be announced as we 
> push out each new stable release.  More details about using the frozen 
> version 
> loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and features 
> should work the same as for the stable version it was created from.  But 
> there 
> are two minor, though important, limitations with loading frozen versions, 
> which we expect to resolve in the near future.
>
>1. You can only call google.charts.load() one time.  You can instead 
>list all the packages that you'll need in one call, so there is usually no 
>need to make separate calls. 
>2. If you are using a ChartWrapper, you must explicitly load all the 
>packages you'll need rather than relying on the ChartWrapper to 
>automatically load them for you. 
>
> We expect that frozen versions will remain available indefinitely, though 
> we may retire frozen versions that have security concerns.  We will 
> typically not provide support for frozen versions, except to suggest 
> upgrading to newer versions.
>
> Even if you don't plan to use the frozen version 41, it would help us if 
> you could try it now with your charts and please let us know if you 
> experience any problems.
>
> -- 
> Daniel LaLiberte  
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/2aa43401-56a7-471d-a9d6-cfdfc611f143%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Stefano Colao]

Thanks, it was my mistake, everything is working.

On Thursday, October 8, 2015 at 2:02:19 PM UTC+2, Daniel LaLiberte wrote:
>
> There is no difference in how you use arrayToDataTable with Frozen Google 
> Charts.  There should be no difference in anything, except how you load.
>
> On Thu, Oct 8, 2015 at 7:59 AM, Stefano Colao  > wrote:
>
>> Hello, how to use DataTable arrayToDataTable with Frozen Google Charts? 
>>
>> On Tuesday, July 28, 2015 at 2:11:12 PM UTC+2, Daniel LaLiberte wrote:
>>>
>>> *Introducing Frozen Google Charts*
>>>
>>> When we push out new releases of Google Charts, some of the changes are 
>>> big, like entirely new chart types, but other changes are small, like 
>>> enhancements to the appearance or behavior of existing charts.  
>>>
>>> Many Google Chart creators fine-tune the look and feel of their charts 
>>> until it's exactly what they want. Some of those users might feel more 
>>> comfortable knowing that their charts will never change, regardless of what 
>>> improvements we make in the future.  For those users, we're proud to 
>>> announce Frozen Google Charts.  
>>>
>>> To load a frozen version, you must make some small changes in how you 
>>> load the Google Charts packages.  For example, here is the usual way of 
>>> loading the stable version and drawing a chart:
>>>
>>> >>
>>> src="https://www.google.com/jsapi";>
>>>
>>> 
>>>
>>>google.load('visualization', '1', {packages: ['corechart']});
>>>
>>>google.setOnLoadCallback(drawChart);
>>>
>>> 
>>>
>>> You'll need to change your code to be like this (changes highlighted in 
>>> bold):
>>>
>>> >>
>>> src="*https://www.gstatic.com/charts/loader.js* 
>>> <https://www.gstatic.com/charts/loader.js>">
>>>
>>> 
>>>
>>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>>
>>>*google.charts.setOnLoadCallback*(drawChart);
>>> 
>>>
>>>
>>> Note that when you call google.charts.load(), you should not include 
>>> the ‘visualization’ parameter, and the version number is a string.  
>>> Only version ‘41’ is supported at this time, which corresponds to the 
>>> current stable release, and additional frozen versions will be 
>>> announced as we push out each new stable release.  More details about 
>>> using the frozen version loader will be available here 
>>> 
>>> .
>>>
>>>
>>> When you use a frozen version of Google Charts, all charts and features 
>>> should work the same as for the stable version it was created from.  But 
>>> there 
>>> are two minor, though important, limitations with loading frozen versions, 
>>> which we expect to resolve in the near future.
>>>
>>>1. You can only call google.charts.load() one time.  You can instead 
>>>list all the packages that you'll need in one call, so there is usually 
>>> no 
>>>need to make separate calls. 
>>>2. If you are using a ChartWrapper, you must explicitly load all the 
>>>packages you'll need rather than relying on the ChartWrapper to 
>>>automatically load them for you. 
>>>
>>> We expect that frozen versions will remain available indefinitely, 
>>> though we may retire frozen versions that have security concerns.  We will 
>>> typically not provide support for frozen versions, except to suggest 
>>> upgrading to newer versions.
>>>
>>> Even if you don't plan to use the frozen version 41, it would help us 
>>> if you could try it now with your charts and please let us know if you 
>>> experience any problems.
>>>
>>> -- 
>>> Daniel LaLiberte 
>>>   - 978-394-1058
>>> dlali...@google.com   5CC, Cambridge MA
>>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>>
>> -- 
>> 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+unsubscr...@googlegroups.com 
>> .
>> To post to this group, send email to google-visua...@googlegroups.com 
>> .
>> Visit this group at 
>> http://groups.google.com/group/google-visualization-api.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-visualization-api/c94b9714-e65c-42dc-9ed6-3ebe2df2de60%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Daniel LaLiberte  
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Act

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

There is no difference in how you use arrayToDataTable with Frozen Google
Charts.  There should be no difference in anything, except how you load.

On Thu, Oct 8, 2015 at 7:59 AM, Stefano Colao  wrote:

> Hello, how to use DataTable arrayToDataTable with Frozen Google Charts?
>
> On Tuesday, July 28, 2015 at 2:11:12 PM UTC+2, Daniel LaLiberte wrote:
>>
>> *Introducing Frozen Google Charts*
>>
>> When we push out new releases of Google Charts, some of the changes are
>> big, like entirely new chart types, but other changes are small, like
>> enhancements to the appearance or behavior of existing charts.
>>
>> Many Google Chart creators fine-tune the look and feel of their charts
>> until it's exactly what they want. Some of those users might feel more
>> comfortable knowing that their charts will never change, regardless of what
>> improvements we make in the future.  For those users, we're proud to
>> announce Frozen Google Charts.
>>
>> To load a frozen version, you must make some small changes in how you
>> load the Google Charts packages.  For example, here is the usual way of
>> loading the stable version and drawing a chart:
>>
>> >
>> src="https://www.google.com/jsapi";>
>>
>> 
>>
>>google.load('visualization', '1', {packages: ['corechart']});
>>
>>google.setOnLoadCallback(drawChart);
>>
>> 
>>
>> You'll need to change your code to be like this (changes highlighted in
>> bold):
>>
>> >
>> src="*https://www.gstatic.com/charts/loader.js*
>> <https://www.gstatic.com/charts/loader.js>">
>>
>> 
>>
>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>
>>*google.charts.setOnLoadCallback*(drawChart);
>> 
>>
>>
>> Note that when you call google.charts.load(), you should not include the
>> ‘visualization’ parameter, and the version number is a string.  Only
>> version ‘41’ is supported at this time, which corresponds to the current
>> stable release, and additional frozen versions will be announced as we
>> push out each new stable release.  More details about using the frozen 
>> version
>> loader will be available here
>> 
>> .
>>
>>
>> When you use a frozen version of Google Charts, all charts and features
>> should work the same as for the stable version it was created from.  But 
>> there
>> are two minor, though important, limitations with loading frozen versions,
>> which we expect to resolve in the near future.
>>
>>1. You can only call google.charts.load() one time.  You can instead
>>list all the packages that you'll need in one call, so there is usually no
>>need to make separate calls.
>>2. If you are using a ChartWrapper, you must explicitly load all the
>>packages you'll need rather than relying on the ChartWrapper to
>>automatically load them for you.
>>
>> We expect that frozen versions will remain available indefinitely, though
>> we may retire frozen versions that have security concerns.  We will
>> typically not provide support for frozen versions, except to suggest
>> upgrading to newer versions.
>>
>> Even if you don't plan to use the frozen version 41, it would help us if
>> you could try it now with your charts and please let us know if you
>> experience any problems.
>>
>> --
>> Daniel LaLiberte 
>>  - 978-394-1058
>> dlali...@google.com   5CC, Cambridge MA
>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/c94b9714-e65c-42dc-9ed6-3ebe2df2de60%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email 

[visualization-api] Re: Introducing Frozen Google Charts

[Stefano Colao]

Hello, how to use DataTable arrayToDataTable with Frozen Google Charts? 

On Tuesday, July 28, 2015 at 2:11:12 PM UTC+2, Daniel LaLiberte wrote:
>
> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes are 
> big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way of 
> loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted in 
> bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include the 
> ‘visualization’ parameter, and the version number is a string.  Only 
> version ‘41’ is supported at this time, which corresponds to the current 
> stable release, and additional frozen versions will be announced as we 
> push out each new stable release.  More details about using the frozen 
> version 
> loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and features 
> should work the same as for the stable version it was created from.  But 
> there 
> are two minor, though important, limitations with loading frozen versions, 
> which we expect to resolve in the near future.
>
>1. You can only call google.charts.load() one time.  You can instead 
>list all the packages that you'll need in one call, so there is usually no 
>need to make separate calls. 
>2. If you are using a ChartWrapper, you must explicitly load all the 
>packages you'll need rather than relying on the ChartWrapper to 
>automatically load them for you. 
>
> We expect that frozen versions will remain available indefinitely, though 
> we may retire frozen versions that have security concerns.  We will 
> typically not provide support for frozen versions, except to suggest 
> upgrading to newer versions.
>
> Even if you don't plan to use the frozen version 41, it would help us if 
> you could try it now with your charts and please let us know if you 
> experience any problems.
>
> -- 
> Daniel LaLiberte  
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/c94b9714-e65c-42dc-9ed6-3ebe2df2de60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Google Charts version 42 can now be loaded via the frozen code loader.
Just replace "41" with "42" in your google.charts.load() call to get that
version.

In upcoming releases, we expect to make the "frozen" version available even
sooner after the public release of the "stable" version.   In fact, we will
probably make the next version available even before starting the normal
release cycle, thus allowing people to use our very latest development
version and help us test it out that much sooner.   Watch for upcoming
announcements about that.

On Mon, Sep 14, 2015 at 11:01 AM, Daniel LaLiberte 
wrote:

> Yes, using style.visibility = 'hidden' does everything the same as
> 'visible' except it's just not visible.  So text measuring works OK.
>
> On Mon, Sep 14, 2015 at 10:17 AM, Thomas 
> wrote:
>
>> thanks a lot!
>>
>> but it is okay to use *only* style.visibility, right?
>>
>>
>>
>>
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To post to this group, send email to
>> google-visualization-api@googlegroups.com.
>> Visit this group at
>> http://groups.google.com/group/google-visualization-api.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-visualization-api/92b62d42-7d6e-488c-95bc-2ef7cc46d140%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Daniel LaLiberte 
>  - 978-394-1058
> dlalibe...@google.com5CC, Cambridge MA
> daniel.lalibe...@gmail.com  9 Juniper Ridge
> Road, Acton MA
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMXAA5AGUEszqfe69JnxVa24-1t9noW76CCL7zmhWm2gg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Yes, using style.visibility = 'hidden' does everything the same as
'visible' except it's just not visible.  So text measuring works OK.

On Mon, Sep 14, 2015 at 10:17 AM, Thomas 
wrote:

> thanks a lot!
>
> but it is okay to use *only* style.visibility, right?
>
>
>
>
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/92b62d42-7d6e-488c-95bc-2ef7cc46d140%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJP112%2BhT8asr7ciTKKGMpoXiPqeHSqOzhAYv0286goi0g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Thomas]

thanks a lot!

but it is okay to use *only* style.visibility, right?


 
 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/92b62d42-7d6e-488c-95bc-2ef7cc46d140%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Thomas,

I believe that pages fetched via http can load resources via https without
concern, but not the other way around.  In other words, loading secure
resources in an insecure page is OK, but loading insecure resources in a
secure page would compromise the security of the page. If the Google Charts
internal use of https causes problems for anyone, I'm sure we'll hear about
it.

Version 43 will be frozen sometime before version 44 is released, but more
likely, soon after version 43 is released to production which could be in
about 1 month. We hope to start the v43 release cycle this week.

Regarding the problem with setting the container style.display to 'none',
this will continue to be a problem since Google Charts doesn't know how big
your text labels are when you draw a chart unless the chart is being
displayed, even if it is invisible (via style.visibility).

You should be able to call setOnLoadCallback multiple times, at least with
the google.charts.setOnLoadCallback.  The answer is less clear with
google.setOnLoadCallback.


On Mon, Sep 14, 2015 at 8:05 AM, Thomas  wrote:

> hi
>
> *https*
>> works, thx.
>>
>
>
>> *http*
>> would be an asset. some html pages have to use http throughout (e.g.,
>>
> taking account of additional 3rd party libraries).
>>
>
>
>> *tooltip.css*
>> thx for the info. when will google "freeze" 43 (provide a frozen
>> version)? 2015? 2016? an exact
>>
> answer is not necessary, of course.
>>
>
>
>> *"overlap problem"*
>> if the stable version draws a line chart while style.display of div is
>> 'none' (initially), the line chart will be *okay*.
>> if the frozen version draws a line chart while style.display of div is
>> 'none' (initially), the line chart will be *NOT okay*: the
>> vertical labels overlap (a picture is in this thread, above).
>> approach (subject to tests): use style.visibility rather than
>> style.display.
>>
>
>
>> *besides, another question*
>> Is it in order to call setOnLoadCallback several times and draw several
>> charts?
>>
>> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/b41e7e50-ad3b-4d7b-87b5-2fc0aac2a020%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJOgrCb%3Dh3E2efon%2B74vXK68%2BF5u7SdNL%2B8aR%3DN_TqR-mQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Thomas]

hi 

*https*
> works, thx.
>
 

> *http*
> would be an asset. some html pages have to use http throughout (e.g., 
>
taking account of additional 3rd party libraries).
>
 

> *tooltip.css*
> thx for the info. when will google "freeze" 43 (provide a frozen version)? 
> 2015? 2016? an exact
>
answer is not necessary, of course.
>
 

> *"overlap problem"*
> if the stable version draws a line chart while style.display of div is 
> 'none' (initially), the line chart will be *okay*.
> if the frozen version draws a line chart while style.display of div is 
> 'none' (initially), the line chart will be *NOT okay*: the
> vertical labels overlap (a picture is in this thread, above).
> approach (subject to tests): use style.visibility rather than 
> style.display.
>
 

> *besides, another question*
> Is it in order to call setOnLoadCallback several times and draw several 
> charts?
>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/b41e7e50-ad3b-4d7b-87b5-2fc0aac2a020%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Kevin Crawley]

Daniel,

Okay, we can do that. Let me know how I can assist in getting this issue
put to bed.

On Tue, Sep 8, 2015 at 10:57 AM, 'Daniel LaLiberte' via Google
Visualization API  wrote:

> Kevin,
>
> Sounds like the css load detection is failing then.   The frozen code
> loader actually waits for the css files to be loaded before proceeding,
> which would be better than not waiting, but that means it has to be able to
> detect that the files are loaded.   Let's communicate by direct email about
> how we might be able to fix this.
>
> On Tue, Sep 8, 2015 at 11:43 AM, Kevin Crawley 
> wrote:
>
>> Daniel,
>>
>> Seems to get to util.css (which loads successfully) and then nothing more.
>>
>> On Tue, Sep 8, 2015 at 10:17 AM, 'Daniel LaLiberte' via Google
>> Visualization API  wrote:
>>
>>> Kevin,
>>>
>>> OK, a silent failure means it may be more challenging to get clues about
>>> what is happening.  You say the loader appear to never finish loading, but
>>> does it start?  Is it loading any files?  It would start by loading css
>>> files, then js files.  If it does appear to load all the files, but then
>>> never calls the callback to proceed, that would indicate it doesn't know
>>> the document has finished loading.
>>>
>>> On Tue, Sep 8, 2015 at 11:08 AM, Kevin Crawley 
>>> wrote:
>>>
 Daniel,

 There isn't an error, the loader appears to never finish executing. The
 library appears to be there `google.charts` is an object, but
 `visualization` is conspicuously absent.


 



 


 On Tuesday, September 8, 2015 at 9:40:57 AM UTC-5, Daniel LaLiberte
 wrote:
>
> Kevin,
>
> Sorry, no, I haven't had time to investigate further.   Can you try
> again and send me an email with the details of the error message?  I might
> be able to guess at this point.
>
> On Tue, Sep 8, 2015 at 10:21 AM, Kevin Crawley 
> wrote:
>
>> Daniel,
>>
>> Has there been any progress on determining why the loader will not
>> work in PhantomJS?
>>
>> Thanks,
>> Kevin
>> ke...@raventools.com
>>
>>
>> On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>>>
>>> *Introducing Frozen Google Charts*
>>>
>>> When we push out new releases of Google Charts, some of the changes
>>> are big, like entirely new chart types, but other changes are small, 
>>> like
>>> enhancements to the appearance or behavior of existing charts.
>>>
>>> Many Google Chart creators fine-tune the look and feel of their
>>> charts until it's exactly what they want. Some of those users might feel
>>> more comfortable knowing that their charts will never change, 
>>> regardless of
>>> what improvements we make in the future.  For those users, we're proud 
>>> to
>>> announce Frozen Google Charts.
>>>
>>> To load a frozen version, you must make some small changes in how
>>> you load the Google Charts packages.  For example, here is the
>>> usual way of loading the stable version and drawing a chart:
>>>
>>> >>
>>> src="https://www.google.com/jsapi";>
>>>
>>> 
>>>
>>>google.load('visualization', '1', {packages: ['corechart']});
>>>
>>>google.setOnLoadCallback(drawChart);
>>>
>>> 
>>>
>>> You'll need to change your code to be like this (changes
>>> highlighted in bold):
>>>
>>> >>
>>> src="*https://www.gstatic.com/charts/loader.js*
>>> <https://www.gstatic.com/charts/loader.js>">
>>>
>>> 
>>>
>>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>>
>>>*google.charts.setOnLoadCallback*(drawChart);
>>> 
>>>
>>>
>>> Note that when you call google.charts.load(), you should not
>>> include the ‘visualization’ parameter, and the version number is a
>>> string.  Only version ‘41’ is supported at this time, which corresponds 
>>> to
>>> the current stable release, and additional frozen versions will be
>>> announced as we push out each new stable release.  More details
>>> about using the frozen version loader will be available here
>>> 
>>> .
>>>
>>>
>>> When you use a frozen version of Google Charts, all charts and
>>> features should work the same as for the stable version it was cre

[visualization-api] Re: Introducing Frozen Google Charts

[Thomas Fantou]

>
> Hi,
>

Might be related to what Kevin is experiencing,
I was debugging, 5 seconds after the .load(), which script and style were 
living in the DOM: only the util.css

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/f58639a7-30f9-47ef-87d1-d7a849b4980c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Kevin,

Sounds like the css load detection is failing then.   The frozen code
loader actually waits for the css files to be loaded before proceeding,
which would be better than not waiting, but that means it has to be able to
detect that the files are loaded.   Let's communicate by direct email about
how we might be able to fix this.

On Tue, Sep 8, 2015 at 11:43 AM, Kevin Crawley  wrote:

> Daniel,
>
> Seems to get to util.css (which loads successfully) and then nothing more.
>
> On Tue, Sep 8, 2015 at 10:17 AM, 'Daniel LaLiberte' via Google
> Visualization API  wrote:
>
>> Kevin,
>>
>> OK, a silent failure means it may be more challenging to get clues about
>> what is happening.  You say the loader appear to never finish loading, but
>> does it start?  Is it loading any files?  It would start by loading css
>> files, then js files.  If it does appear to load all the files, but then
>> never calls the callback to proceed, that would indicate it doesn't know
>> the document has finished loading.
>>
>> On Tue, Sep 8, 2015 at 11:08 AM, Kevin Crawley 
>> wrote:
>>
>>> Daniel,
>>>
>>> There isn't an error, the loader appears to never finish executing. The
>>> library appears to be there `google.charts` is an object, but
>>> `visualization` is conspicuously absent.
>>>
>>>
>>> 
>>>
>>>
>>>
>>> 
>>>
>>>
>>> On Tuesday, September 8, 2015 at 9:40:57 AM UTC-5, Daniel LaLiberte
>>> wrote:

 Kevin,

 Sorry, no, I haven't had time to investigate further.   Can you try
 again and send me an email with the details of the error message?  I might
 be able to guess at this point.

 On Tue, Sep 8, 2015 at 10:21 AM, Kevin Crawley 
 wrote:

> Daniel,
>
> Has there been any progress on determining why the loader will not
> work in PhantomJS?
>
> Thanks,
> Kevin
> ke...@raventools.com
>
>
> On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>>
>> *Introducing Frozen Google Charts*
>>
>> When we push out new releases of Google Charts, some of the changes
>> are big, like entirely new chart types, but other changes are small, like
>> enhancements to the appearance or behavior of existing charts.
>>
>> Many Google Chart creators fine-tune the look and feel of their
>> charts until it's exactly what they want. Some of those users might feel
>> more comfortable knowing that their charts will never change, regardless 
>> of
>> what improvements we make in the future.  For those users, we're proud to
>> announce Frozen Google Charts.
>>
>> To load a frozen version, you must make some small changes in how
>> you load the Google Charts packages.  For example, here is the usual
>> way of loading the stable version and drawing a chart:
>>
>> >
>> src="https://www.google.com/jsapi";>
>>
>> 
>>
>>google.load('visualization', '1', {packages: ['corechart']});
>>
>>google.setOnLoadCallback(drawChart);
>>
>> 
>>
>> You'll need to change your code to be like this (changes highlighted
>> in bold):
>>
>> >
>> src="*https://www.gstatic.com/charts/loader.js*
>> <https://www.gstatic.com/charts/loader.js>">
>>
>> 
>>
>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>
>>*google.charts.setOnLoadCallback*(drawChart);
>> 
>>
>>
>> Note that when you call google.charts.load(), you should not include
>> the ‘visualization’ parameter, and the version number is a string.
>> Only version ‘41’ is supported at this time, which corresponds to the
>> current stable release, and additional frozen versions will be
>> announced as we push out each new stable release.  More details
>> about using the frozen version loader will be available here
>> 
>> .
>>
>>
>> When you use a frozen version of Google Charts, all charts and
>> features should work the same as for the stable version it was created
>> from.  But there are two minor, though important, limitations with
>> loading frozen versions, which we expect to resolve in the near
>> future.
>>
>>1. You can only call google.charts.load() one time.  You can
>>instead list all the packages that you'll need in one call, so there 
>> is
>>usu

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Kevin Crawley]

Daniel,

Seems to get to util.css (which loads successfully) and then nothing more.

On Tue, Sep 8, 2015 at 10:17 AM, 'Daniel LaLiberte' via Google
Visualization API  wrote:

> Kevin,
>
> OK, a silent failure means it may be more challenging to get clues about
> what is happening.  You say the loader appear to never finish loading, but
> does it start?  Is it loading any files?  It would start by loading css
> files, then js files.  If it does appear to load all the files, but then
> never calls the callback to proceed, that would indicate it doesn't know
> the document has finished loading.
>
> On Tue, Sep 8, 2015 at 11:08 AM, Kevin Crawley 
> wrote:
>
>> Daniel,
>>
>> There isn't an error, the loader appears to never finish executing. The
>> library appears to be there `google.charts` is an object, but
>> `visualization` is conspicuously absent.
>>
>>
>> 
>>
>>
>>
>> 
>>
>>
>> On Tuesday, September 8, 2015 at 9:40:57 AM UTC-5, Daniel LaLiberte wrote:
>>>
>>> Kevin,
>>>
>>> Sorry, no, I haven't had time to investigate further.   Can you try
>>> again and send me an email with the details of the error message?  I might
>>> be able to guess at this point.
>>>
>>> On Tue, Sep 8, 2015 at 10:21 AM, Kevin Crawley 
>>> wrote:
>>>
 Daniel,

 Has there been any progress on determining why the loader will not work
 in PhantomJS?

 Thanks,
 Kevin
 ke...@raventools.com


 On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>
> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes
> are big, like entirely new chart types, but other changes are small, like
> enhancements to the appearance or behavior of existing charts.
>
> Many Google Chart creators fine-tune the look and feel of their charts
> until it's exactly what they want. Some of those users might feel more
> comfortable knowing that their charts will never change, regardless of 
> what
> improvements we make in the future.  For those users, we're proud to
> announce Frozen Google Charts.
>
> To load a frozen version, you must make some small changes in how you
> load the Google Charts packages.  For example, here is the usual way
> of loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted
> in bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js*
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include
> the ‘visualization’ parameter, and the version number is a string.
> Only version ‘41’ is supported at this time, which corresponds to the
> current stable release, and additional frozen versions will be
> announced as we push out each new stable release.  More details about
> using the frozen version loader will be available here
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and
> features should work the same as for the stable version it was created
> from.  But there are two minor, though important, limitations with
> loading frozen versions, which we expect to resolve in the near
> future.
>
>1. You can only call google.charts.load() one time.  You can
>instead list all the packages that you'll need in one call, so there is
>usually no need to make separate calls.
>2. If you are using a ChartWrapper, you must explicitly load all
>the packages you'll need rather than relying on the ChartWrapper to
>automatically load them for you.
>
> We expect that frozen versions will remain available indefinitely,
> though we may retire frozen versions that have security concerns.  We will
> typically not provide support for frozen versions, except to suggest
> upgrading to newer versions.
>
> Even if you don't

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Kevin,

OK, a silent failure means it may be more challenging to get clues about
what is happening.  You say the loader appear to never finish loading, but
does it start?  Is it loading any files?  It would start by loading css
files, then js files.  If it does appear to load all the files, but then
never calls the callback to proceed, that would indicate it doesn't know
the document has finished loading.

On Tue, Sep 8, 2015 at 11:08 AM, Kevin Crawley  wrote:

> Daniel,
>
> There isn't an error, the loader appears to never finish executing. The
> library appears to be there `google.charts` is an object, but
> `visualization` is conspicuously absent.
>
>
> 
>
>
>
> 
>
>
> On Tuesday, September 8, 2015 at 9:40:57 AM UTC-5, Daniel LaLiberte wrote:
>>
>> Kevin,
>>
>> Sorry, no, I haven't had time to investigate further.   Can you try again
>> and send me an email with the details of the error message?  I might be
>> able to guess at this point.
>>
>> On Tue, Sep 8, 2015 at 10:21 AM, Kevin Crawley 
>> wrote:
>>
>>> Daniel,
>>>
>>> Has there been any progress on determining why the loader will not work
>>> in PhantomJS?
>>>
>>> Thanks,
>>> Kevin
>>> ke...@raventools.com
>>>
>>>
>>> On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:

 *Introducing Frozen Google Charts*

 When we push out new releases of Google Charts, some of the changes are
 big, like entirely new chart types, but other changes are small, like
 enhancements to the appearance or behavior of existing charts.

 Many Google Chart creators fine-tune the look and feel of their charts
 until it's exactly what they want. Some of those users might feel more
 comfortable knowing that their charts will never change, regardless of what
 improvements we make in the future.  For those users, we're proud to
 announce Frozen Google Charts.

 To load a frozen version, you must make some small changes in how you
 load the Google Charts packages.  For example, here is the usual way
 of loading the stable version and drawing a chart:

 >>>
 src="https://www.google.com/jsapi";>

 

google.load('visualization', '1', {packages: ['corechart']});

google.setOnLoadCallback(drawChart);

 

 You'll need to change your code to be like this (changes highlighted
 in bold):

 >>>
 src="*https://www.gstatic.com/charts/loader.js*
 <https://www.gstatic.com/charts/loader.js>">

 

*google.charts.load(**'41'**,* {packages: ['corechart']});

*google.charts.setOnLoadCallback*(drawChart);
 


 Note that when you call google.charts.load(), you should not include
 the ‘visualization’ parameter, and the version number is a string.
 Only version ‘41’ is supported at this time, which corresponds to the
 current stable release, and additional frozen versions will be
 announced as we push out each new stable release.  More details about
 using the frozen version loader will be available here
 
 .


 When you use a frozen version of Google Charts, all charts and
 features should work the same as for the stable version it was created
 from.  But there are two minor, though important, limitations with
 loading frozen versions, which we expect to resolve in the near future.

1. You can only call google.charts.load() one time.  You can
instead list all the packages that you'll need in one call, so there is
usually no need to make separate calls.
2. If you are using a ChartWrapper, you must explicitly load all
the packages you'll need rather than relying on the ChartWrapper to
automatically load them for you.

 We expect that frozen versions will remain available indefinitely,
 though we may retire frozen versions that have security concerns.  We will
 typically not provide support for frozen versions, except to suggest
 upgrading to newer versions.

 Even if you don't plan to use the frozen version 41, it would help us
 if you could try it now with your charts and please let us know if you
 experience any problems.

 --
 Daniel LaLiberte
   - 978-394-1058
 dlali...@google.com   5CC, Cambridge MA
>>

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Kevin Crawley]

Daniel,

There isn't an error, the loader appears to never finish executing. The 
library appears to be there `google.charts` is an object, but 
`visualization` is conspicuously absent.







On Tuesday, September 8, 2015 at 9:40:57 AM UTC-5, Daniel LaLiberte wrote:
>
> Kevin,
>
> Sorry, no, I haven't had time to investigate further.   Can you try again 
> and send me an email with the details of the error message?  I might be 
> able to guess at this point. 
>
> On Tue, Sep 8, 2015 at 10:21 AM, Kevin Crawley  > wrote:
>
>> Daniel,
>>
>> Has there been any progress on determining why the loader will not work 
>> in PhantomJS?
>>
>> Thanks,
>> Kevin
>> ke...@raventools.com 
>>
>> On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>>>
>>> *Introducing Frozen Google Charts*
>>>
>>> When we push out new releases of Google Charts, some of the changes are 
>>> big, like entirely new chart types, but other changes are small, like 
>>> enhancements to the appearance or behavior of existing charts.  
>>>
>>> Many Google Chart creators fine-tune the look and feel of their charts 
>>> until it's exactly what they want. Some of those users might feel more 
>>> comfortable knowing that their charts will never change, regardless of what 
>>> improvements we make in the future.  For those users, we're proud to 
>>> announce Frozen Google Charts.  
>>>
>>> To load a frozen version, you must make some small changes in how you 
>>> load the Google Charts packages.  For example, here is the usual way of 
>>> loading the stable version and drawing a chart:
>>>
>>> >>
>>> src="https://www.google.com/jsapi";>
>>>
>>> 
>>>
>>>google.load('visualization', '1', {packages: ['corechart']});
>>>
>>>google.setOnLoadCallback(drawChart);
>>>
>>> 
>>>
>>> You'll need to change your code to be like this (changes highlighted in 
>>> bold):
>>>
>>> >>
>>> src="*https://www.gstatic.com/charts/loader.js* 
>>> <https://www.gstatic.com/charts/loader.js>">
>>>
>>> 
>>>
>>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>>
>>>*google.charts.setOnLoadCallback*(drawChart);
>>> 
>>>
>>>
>>> Note that when you call google.charts.load(), you should not include 
>>> the ‘visualization’ parameter, and the version number is a string.  
>>> Only version ‘41’ is supported at this time, which corresponds to the 
>>> current stable release, and additional frozen versions will be 
>>> announced as we push out each new stable release.  More details about 
>>> using the frozen version loader will be available here 
>>> 
>>> .
>>>
>>>
>>> When you use a frozen version of Google Charts, all charts and features 
>>> should work the same as for the stable version it was created from.  But 
>>> there 
>>> are two minor, though important, limitations with loading frozen versions, 
>>> which we expect to resolve in the near future.
>>>
>>>1. You can only call google.charts.load() one time.  You can instead 
>>>list all the packages that you'll need in one call, so there is usually 
>>> no 
>>>need to make separate calls. 
>>>2. If you are using a ChartWrapper, you must explicitly load all the 
>>>packages you'll need rather than relying on the ChartWrapper to 
>>>automatically load them for you. 
>>>
>>> We expect that frozen versions will remain available indefinitely, 
>>> though we may retire frozen versions that have security concerns.  We will 
>>> typically not provide support for frozen versions, except to suggest 
>>> upgrading to newer versions.
>>>
>>> Even if you don't plan to use the frozen version 41, it would help us 
>>> if you could try it now with your charts and please let us know if you 
>>> experience any problems.
>>>
>>> -- 
>>> Daniel LaLiberte 
>>>   - 978-394-1058
>>> dlali...@google.com   5CC, Cambridge MA
>>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>>
>> -- 
>> 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+unsubscr...@googlegroups.com 
>> .
>> To post to this group, send email to google-visua...@googlegroups.com 
>> .
>> Visit this group at 
>> http://groups.google.com/group/google-visualization-api.
>> To view this discussion on the web visit 
>

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Kevin,

Sorry, no, I haven't had time to investigate further.   Can you try again
and send me an email with the details of the error message?  I might be
able to guess at this point.

On Tue, Sep 8, 2015 at 10:21 AM, Kevin Crawley  wrote:

> Daniel,
>
> Has there been any progress on determining why the loader will not work in
> PhantomJS?
>
> Thanks,
> Kevin
> ke...@raventools.com
>
> On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>>
>> *Introducing Frozen Google Charts*
>>
>> When we push out new releases of Google Charts, some of the changes are
>> big, like entirely new chart types, but other changes are small, like
>> enhancements to the appearance or behavior of existing charts.
>>
>> Many Google Chart creators fine-tune the look and feel of their charts
>> until it's exactly what they want. Some of those users might feel more
>> comfortable knowing that their charts will never change, regardless of what
>> improvements we make in the future.  For those users, we're proud to
>> announce Frozen Google Charts.
>>
>> To load a frozen version, you must make some small changes in how you
>> load the Google Charts packages.  For example, here is the usual way of
>> loading the stable version and drawing a chart:
>>
>> >
>> src="https://www.google.com/jsapi";>
>>
>> 
>>
>>google.load('visualization', '1', {packages: ['corechart']});
>>
>>google.setOnLoadCallback(drawChart);
>>
>> 
>>
>> You'll need to change your code to be like this (changes highlighted in
>> bold):
>>
>> >
>> src="*https://www.gstatic.com/charts/loader.js*
>> <https://www.gstatic.com/charts/loader.js>">
>>
>> 
>>
>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>
>>*google.charts.setOnLoadCallback*(drawChart);
>> 
>>
>>
>> Note that when you call google.charts.load(), you should not include the
>> ‘visualization’ parameter, and the version number is a string.  Only
>> version ‘41’ is supported at this time, which corresponds to the current
>> stable release, and additional frozen versions will be announced as we
>> push out each new stable release.  More details about using the frozen 
>> version
>> loader will be available here
>> 
>> .
>>
>>
>> When you use a frozen version of Google Charts, all charts and features
>> should work the same as for the stable version it was created from.  But 
>> there
>> are two minor, though important, limitations with loading frozen versions,
>> which we expect to resolve in the near future.
>>
>>1. You can only call google.charts.load() one time.  You can instead
>>list all the packages that you'll need in one call, so there is usually no
>>need to make separate calls.
>>2. If you are using a ChartWrapper, you must explicitly load all the
>>packages you'll need rather than relying on the ChartWrapper to
>>automatically load them for you.
>>
>> We expect that frozen versions will remain available indefinitely, though
>> we may retire frozen versions that have security concerns.  We will
>> typically not provide support for frozen versions, except to suggest
>> upgrading to newer versions.
>>
>> Even if you don't plan to use the frozen version 41, it would help us if
>> you could try it now with your charts and please let us know if you
>> experience any problems.
>>
>> --
>> Daniel LaLiberte 
>>  - 978-394-1058
>> dlali...@google.com   5CC, Cambridge MA
>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/8d5173e5-2160-43c9-80cd-57dc0070ab1b%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

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

[visualization-api] Re: Introducing Frozen Google Charts

[Kevin Crawley]

Daniel,

Has there been any progress on determining why the loader will not work in 
PhantomJS?

Thanks,
Kevin
ke...@raventools.com

On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>
> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes are 
> big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way of 
> loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted in 
> bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include the 
> ‘visualization’ parameter, and the version number is a string.  Only 
> version ‘41’ is supported at this time, which corresponds to the current 
> stable release, and additional frozen versions will be announced as we 
> push out each new stable release.  More details about using the frozen 
> version 
> loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and features 
> should work the same as for the stable version it was created from.  But 
> there 
> are two minor, though important, limitations with loading frozen versions, 
> which we expect to resolve in the near future.
>
>1. You can only call google.charts.load() one time.  You can instead 
>list all the packages that you'll need in one call, so there is usually no 
>need to make separate calls. 
>2. If you are using a ChartWrapper, you must explicitly load all the 
>packages you'll need rather than relying on the ChartWrapper to 
>automatically load them for you. 
>
> We expect that frozen versions will remain available indefinitely, though 
> we may retire frozen versions that have security concerns.  We will 
> typically not provide support for frozen versions, except to suggest 
> upgrading to newer versions.
>
> Even if you don't plan to use the frozen version 41, it would help us if 
> you could try it now with your charts and please let us know if you 
> experience any problems.
>
> -- 
> Daniel LaLiberte  
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/8d5173e5-2160-43c9-80cd-57dc0070ab1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Thomas,

I poked around on http://wkhtmltopdf.org/index.html and didn't find out how
it works.  It would help if someone could explain what this tool does with
dynamic http/https requests and generated DOM elements.

On Tue, Sep 8, 2015 at 9:59 AM, Thomas Fantou  wrote:

> I would like to add that I have tried to overwrite the callback like this:
>>
> google.charts.load('41', { 'callback': function () { console.log("koko");
> }, 'packages': ['corechart', 'table'] });
>
> It actually doesn't overwrite setOnLoadCallback, but there is now 2
> callbacks. The log "koko" is showing just fine in browser, but not with the
> tool
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/2def6b9f-2fb8-456f-b8dc-b9ff52f2a8ba%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMvv68Pz2kGg2kwoE34ep16iLhCvUJgviy9gZjvhQ6AKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[visualization-api] Re: Introducing Frozen Google Charts

[Thomas Fantou]

>
> I would like to add that I have tried to overwrite the callback like this:
>
google.charts.load('41', { 'callback': function () { console.log("koko"); 
}, 'packages': ['corechart', 'table'] });

It actually doesn't overwrite setOnLoadCallback, but there is now 2 
callbacks. The log "koko" is showing just fine in browser, but not with the 
tool 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/2def6b9f-2fb8-456f-b8dc-b9ff52f2a8ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Thomas Fantou]

Hi,

Oh sorry about that, I believe it is the loading crashing; as I have tried 
to give long delay to the javascript and let it try to load, but 
"google.visualization" would always be undefined. (google = { charts: {} })

On Tuesday, 8 September 2015 13:07:34 UTC+1, Daniel LaLiberte wrote:
>
> Hi Thomas,
>
> First, google.charts.load() always uses https now.
>
> My question was whether you can tell what is loaded by wkhtmltopdf after 
> google.charts.load() is called?  If it loads the packages fine but just 
> doesn't call the callback, then the problem is most likely that the loader 
> doesn't know everything has finished loading.
>
> On Tue, Sep 8, 2015 at 4:28 AM, Thomas Fantou  > wrote:
>
>> Hi Daniel,
>>
>> Well we haven't seen any problems with the rest. Also, like I said, the 
>> loading works fine with the non-frozen versions. 
>> I am not sure I've followed the issue about the loader attempting to load 
>> the same scheme as the page, but since the request is not done through a 
>> web browser, would that make a difference?
>>
>> On Monday, 7 September 2015 19:53:56 UTC+1, Daniel LaLiberte wrote:
>>>
>>> Hi Thomas,
>>>
>>> I can't imagine what might be happening when the Google Charts frozen 
>>> v41 is loaded view wkhtmltopdf, but it sounds like that tool doesn't work 
>>> with the dynamic loading mechanism that we depend on.  Does anything get 
>>> loaded beyond the loader itself?
>>>
>>> On Mon, Sep 7, 2015 at 10:52 AM, Thomas Fantou  
>>> wrote:
>>>
 Hi Daniel,

 We are using the Google Chart API, and rendering our html view with 
 wkhtmltopdf tool (converter html to pdf). 
 It has always been working fine even now with the last stable version, 
 however there is a strange behaviour with the new Frozen version; As far 
 as 
 I have been able to debug, the google.charts.load() method never returns. 
 (Callback method is never triggered/google.visualization.DataTable() is 
 'undefined')

 The frozen version works with our browsers, but not with the third 
 party tool as stated above. I am not sure how I can investigate further; 
 is 
 there any reasons that would ring a bell about this ? (e.g. if platform 
 isn't a browser, the .load() will be stuck somewhere?)

 Thanks,
 Thomas


 On Tuesday, 28 July 2015 13:11:12 UTC+1, Daniel LaLiberte wrote:

> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes 
> are big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of 
> what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way 
> of loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted 
> in bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include 
> the ‘visualization’ parameter, and the version number is a string.  
> Only version ‘41’ is supported at this time, which corresponds to the 
> current stable release, and additional frozen versions will be 
> announced as we push out each new stable release.  More details about 
> using the frozen version loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and 
> features should work the same as for the stable version it was created 
> from.  But there are two minor, though important, limitations with 
> loading frozen versions, which we expect to resolve in the near 
> future.
>
>1. You can only call google.charts.load() one time.  Yo

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Hi Thomas,

First, google.charts.load() always uses https now.

My question was whether you can tell what is loaded by wkhtmltopdf after
google.charts.load() is called?  If it loads the packages fine but just
doesn't call the callback, then the problem is most likely that the loader
doesn't know everything has finished loading.

On Tue, Sep 8, 2015 at 4:28 AM, Thomas Fantou  wrote:

> Hi Daniel,
>
> Well we haven't seen any problems with the rest. Also, like I said, the
> loading works fine with the non-frozen versions.
> I am not sure I've followed the issue about the loader attempting to load
> the same scheme as the page, but since the request is not done through a
> web browser, would that make a difference?
>
> On Monday, 7 September 2015 19:53:56 UTC+1, Daniel LaLiberte wrote:
>>
>> Hi Thomas,
>>
>> I can't imagine what might be happening when the Google Charts frozen v41
>> is loaded view wkhtmltopdf, but it sounds like that tool doesn't work with
>> the dynamic loading mechanism that we depend on.  Does anything get loaded
>> beyond the loader itself?
>>
>> On Mon, Sep 7, 2015 at 10:52 AM, Thomas Fantou  wrote:
>>
>>> Hi Daniel,
>>>
>>> We are using the Google Chart API, and rendering our html view with
>>> wkhtmltopdf tool (converter html to pdf).
>>> It has always been working fine even now with the last stable version,
>>> however there is a strange behaviour with the new Frozen version; As far as
>>> I have been able to debug, the google.charts.load() method never returns.
>>> (Callback method is never triggered/google.visualization.DataTable() is
>>> 'undefined')
>>>
>>> The frozen version works with our browsers, but not with the third party
>>> tool as stated above. I am not sure how I can investigate further; is there
>>> any reasons that would ring a bell about this ? (e.g. if platform isn't a
>>> browser, the .load() will be stuck somewhere?)
>>>
>>> Thanks,
>>> Thomas
>>>
>>>
>>> On Tuesday, 28 July 2015 13:11:12 UTC+1, Daniel LaLiberte wrote:
>>>
 *Introducing Frozen Google Charts*

 When we push out new releases of Google Charts, some of the changes are
 big, like entirely new chart types, but other changes are small, like
 enhancements to the appearance or behavior of existing charts.

 Many Google Chart creators fine-tune the look and feel of their charts
 until it's exactly what they want. Some of those users might feel more
 comfortable knowing that their charts will never change, regardless of what
 improvements we make in the future.  For those users, we're proud to
 announce Frozen Google Charts.

 To load a frozen version, you must make some small changes in how you
 load the Google Charts packages.  For example, here is the usual way
 of loading the stable version and drawing a chart:

 >>>
 src="https://www.google.com/jsapi";>

 

google.load('visualization', '1', {packages: ['corechart']});

google.setOnLoadCallback(drawChart);

 

 You'll need to change your code to be like this (changes highlighted
 in bold):

 >>>
 src="*https://www.gstatic.com/charts/loader.js*
 <https://www.gstatic.com/charts/loader.js>">

 

*google.charts.load(**'41'**,* {packages: ['corechart']});

*google.charts.setOnLoadCallback*(drawChart);
 


 Note that when you call google.charts.load(), you should not include
 the ‘visualization’ parameter, and the version number is a string.
 Only version ‘41’ is supported at this time, which corresponds to the
 current stable release, and additional frozen versions will be
 announced as we push out each new stable release.  More details about
 using the frozen version loader will be available here
 
 .


 When you use a frozen version of Google Charts, all charts and
 features should work the same as for the stable version it was created
 from.  But there are two minor, though important, limitations with
 loading frozen versions, which we expect to resolve in the near future.

1. You can only call google.charts.load() one time.  You can
instead list all the packages that you'll need in one call, so there is
usually no need to make separate calls.
2. If you are using a ChartWrapper, you must explicitly load all
the packages you'll need rather than relying on the ChartWrapper to
automatically load them for you.

 We expect that frozen versions will remain available indefinitely,
 though we may retire frozen versions that have security concerns.  We will
 typ

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Thomas Fantou]

Hi Daniel,

Well we haven't seen any problems with the rest. Also, like I said, the 
loading works fine with the non-frozen versions. 
I am not sure I've followed the issue about the loader attempting to load 
the same scheme as the page, but since the request is not done through a 
web browser, would that make a difference?

On Monday, 7 September 2015 19:53:56 UTC+1, Daniel LaLiberte wrote:
>
> Hi Thomas,
>
> I can't imagine what might be happening when the Google Charts frozen v41 
> is loaded view wkhtmltopdf, but it sounds like that tool doesn't work with 
> the dynamic loading mechanism that we depend on.  Does anything get loaded 
> beyond the loader itself?
>
> On Mon, Sep 7, 2015 at 10:52 AM, Thomas Fantou  > wrote:
>
>> Hi Daniel,
>>
>> We are using the Google Chart API, and rendering our html view with 
>> wkhtmltopdf tool (converter html to pdf). 
>> It has always been working fine even now with the last stable version, 
>> however there is a strange behaviour with the new Frozen version; As far as 
>> I have been able to debug, the google.charts.load() method never returns. 
>> (Callback method is never triggered/google.visualization.DataTable() is 
>> 'undefined')
>>
>> The frozen version works with our browsers, but not with the third party 
>> tool as stated above. I am not sure how I can investigate further; is there 
>> any reasons that would ring a bell about this ? (e.g. if platform isn't a 
>> browser, the .load() will be stuck somewhere?)
>>
>> Thanks,
>> Thomas
>>
>>
>> On Tuesday, 28 July 2015 13:11:12 UTC+1, Daniel LaLiberte wrote:
>>
>>> *Introducing Frozen Google Charts*
>>>
>>> When we push out new releases of Google Charts, some of the changes are 
>>> big, like entirely new chart types, but other changes are small, like 
>>> enhancements to the appearance or behavior of existing charts.  
>>>
>>> Many Google Chart creators fine-tune the look and feel of their charts 
>>> until it's exactly what they want. Some of those users might feel more 
>>> comfortable knowing that their charts will never change, regardless of what 
>>> improvements we make in the future.  For those users, we're proud to 
>>> announce Frozen Google Charts.  
>>>
>>> To load a frozen version, you must make some small changes in how you 
>>> load the Google Charts packages.  For example, here is the usual way of 
>>> loading the stable version and drawing a chart:
>>>
>>> >>
>>> src="https://www.google.com/jsapi";>
>>>
>>> 
>>>
>>>google.load('visualization', '1', {packages: ['corechart']});
>>>
>>>google.setOnLoadCallback(drawChart);
>>>
>>> 
>>>
>>> You'll need to change your code to be like this (changes highlighted in 
>>> bold):
>>>
>>> >>
>>> src="*https://www.gstatic.com/charts/loader.js* 
>>> <https://www.gstatic.com/charts/loader.js>">
>>>
>>> 
>>>
>>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>>
>>>*google.charts.setOnLoadCallback*(drawChart);
>>> 
>>>
>>>
>>> Note that when you call google.charts.load(), you should not include 
>>> the ‘visualization’ parameter, and the version number is a string.  
>>> Only version ‘41’ is supported at this time, which corresponds to the 
>>> current stable release, and additional frozen versions will be 
>>> announced as we push out each new stable release.  More details about 
>>> using the frozen version loader will be available here 
>>> 
>>> .
>>>
>>>
>>> When you use a frozen version of Google Charts, all charts and features 
>>> should work the same as for the stable version it was created from.  But 
>>> there 
>>> are two minor, though important, limitations with loading frozen versions, 
>>> which we expect to resolve in the near future.
>>>
>>>1. You can only call google.charts.load() one time.  You can instead 
>>>list all the packages that you'll need in one call, so there is usually 
>>> no 
>>>need to make separate calls. 
>>>2. If you are using a ChartWrapper, you must explicitly load all the 
>>>packages you'll need rather than relying on the ChartWrapper to 
>>>automatically load them for you. 
>>>
>>> We expect that frozen versions will remain available indefinitely, 
>>> though we may retire frozen versions that have security concerns.  We will 
>>> typically not provide support for frozen versions, except to suggest 
>>> upgrading to newer versions.
>>>
>>> Even if you don't plan to use the frozen version 41, it would help us 
>>> if you could try it now with your charts and please let us know if you 
>>> experience any problems.
>>>
>>> -- 
>>> Daniel LaLiberte 
>>>   - 978-394-1058
>>> dlali...@google.com   5CC, Cambridge MA
>>> 

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Hi Thomas,

I can't imagine what might be happening when the Google Charts frozen v41
is loaded view wkhtmltopdf, but it sounds like that tool doesn't work with
the dynamic loading mechanism that we depend on.  Does anything get loaded
beyond the loader itself?

On Mon, Sep 7, 2015 at 10:52 AM, Thomas Fantou  wrote:

> Hi Daniel,
>
> We are using the Google Chart API, and rendering our html view with
> wkhtmltopdf tool (converter html to pdf).
> It has always been working fine even now with the last stable version,
> however there is a strange behaviour with the new Frozen version; As far as
> I have been able to debug, the google.charts.load() method never returns.
> (Callback method is never triggered/google.visualization.DataTable() is
> 'undefined')
>
> The frozen version works with our browsers, but not with the third party
> tool as stated above. I am not sure how I can investigate further; is there
> any reasons that would ring a bell about this ? (e.g. if platform isn't a
> browser, the .load() will be stuck somewhere?)
>
> Thanks,
> Thomas
>
>
> On Tuesday, 28 July 2015 13:11:12 UTC+1, Daniel LaLiberte wrote:
>
>> *Introducing Frozen Google Charts*
>>
>> When we push out new releases of Google Charts, some of the changes are
>> big, like entirely new chart types, but other changes are small, like
>> enhancements to the appearance or behavior of existing charts.
>>
>> Many Google Chart creators fine-tune the look and feel of their charts
>> until it's exactly what they want. Some of those users might feel more
>> comfortable knowing that their charts will never change, regardless of what
>> improvements we make in the future.  For those users, we're proud to
>> announce Frozen Google Charts.
>>
>> To load a frozen version, you must make some small changes in how you
>> load the Google Charts packages.  For example, here is the usual way of
>> loading the stable version and drawing a chart:
>>
>> >
>> src="https://www.google.com/jsapi";>
>>
>> 
>>
>>google.load('visualization', '1', {packages: ['corechart']});
>>
>>google.setOnLoadCallback(drawChart);
>>
>> 
>>
>> You'll need to change your code to be like this (changes highlighted in
>> bold):
>>
>> >
>> src="*https://www.gstatic.com/charts/loader.js*
>> <https://www.gstatic.com/charts/loader.js>">
>>
>> 
>>
>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>
>>*google.charts.setOnLoadCallback*(drawChart);
>> 
>>
>>
>> Note that when you call google.charts.load(), you should not include the
>> ‘visualization’ parameter, and the version number is a string.  Only
>> version ‘41’ is supported at this time, which corresponds to the current
>> stable release, and additional frozen versions will be announced as we
>> push out each new stable release.  More details about using the frozen 
>> version
>> loader will be available here
>> 
>> .
>>
>>
>> When you use a frozen version of Google Charts, all charts and features
>> should work the same as for the stable version it was created from.  But 
>> there
>> are two minor, though important, limitations with loading frozen versions,
>> which we expect to resolve in the near future.
>>
>>1. You can only call google.charts.load() one time.  You can instead
>>list all the packages that you'll need in one call, so there is usually no
>>need to make separate calls.
>>2. If you are using a ChartWrapper, you must explicitly load all the
>>packages you'll need rather than relying on the ChartWrapper to
>>automatically load them for you.
>>
>> We expect that frozen versions will remain available indefinitely, though
>> we may retire frozen versions that have security concerns.  We will
>> typically not provide support for frozen versions, except to suggest
>> upgrading to newer versions.
>>
>> Even if you don't plan to use the frozen version 41, it would help us if
>> you could try it now with your charts and please let us know if you
>> experience any problems.
>>
>> --
>> Daniel LaLiberte 
>>  - 978-394-1058
>> dlali...@google.com   5CC, Cambridge MA
>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Thomas,

Yes, the extra attempt to load tooltip.css from the wrong place will
remain, since it is hard-coded into the frozen version rather than being
part of the loader configuration.  This will be fixed in version 43.

On Mon, Sep 7, 2015 at 3:02 AM, Thomas  wrote:

> Okay, thank you.
>
> Chrome loads tooltip.css!
>
>
> Chrome shows a second reference to a file called tooltip.css, now.
> Chrome cannot resolve this second reference (> Open chart html file from
> local directory > F12 > Tab “Network”).
>
> Furthermore, if a browser loads the chart resources using http, it loads
> some files using http, others files using https.
> Would be great if browsers could use http respectively tls all the way
> down.
>
>
> (If the reference changes will not solve the “overlap problem” => a very
> special case!, then I will try to prepare a fiddle, later.)
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/33b40443-d265-427a-ae0c-e5a76aa13cc3%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMHv%2B8C2h3T4prRJt5jzD9Bou7%2B_G_EVRJ7wyFgKP%3DyWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[visualization-api] Re: Introducing Frozen Google Charts

[Thomas Fantou]

Hi Daniel,

We are using the Google Chart API, and rendering our html view with 
wkhtmltopdf tool (converter html to pdf). 
It has always been working fine even now with the last stable version, 
however there is a strange behaviour with the new Frozen version; As far as 
I have been able to debug, the google.charts.load() method never returns. 
(Callback method is never triggered/google.visualization.DataTable() is 
'undefined')

The frozen version works with our browsers, but not with the third party 
tool as stated above. I am not sure how I can investigate further; is there 
any reasons that would ring a bell about this ? (e.g. if platform isn't a 
browser, the .load() will be stuck somewhere?)

Thanks,
Thomas

On Tuesday, 28 July 2015 13:11:12 UTC+1, Daniel LaLiberte wrote:
>
> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes are 
> big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way of 
> loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted in 
> bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include the 
> ‘visualization’ parameter, and the version number is a string.  Only 
> version ‘41’ is supported at this time, which corresponds to the current 
> stable release, and additional frozen versions will be announced as we 
> push out each new stable release.  More details about using the frozen 
> version 
> loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and features 
> should work the same as for the stable version it was created from.  But 
> there 
> are two minor, though important, limitations with loading frozen versions, 
> which we expect to resolve in the near future.
>
>1. You can only call google.charts.load() one time.  You can instead 
>list all the packages that you'll need in one call, so there is usually no 
>need to make separate calls. 
>2. If you are using a ChartWrapper, you must explicitly load all the 
>packages you'll need rather than relying on the ChartWrapper to 
>automatically load them for you. 
>
> We expect that frozen versions will remain available indefinitely, though 
> we may retire frozen versions that have security concerns.  We will 
> typically not provide support for frozen versions, except to suggest 
> upgrading to newer versions.
>
> Even if you don't plan to use the frozen version 41, it would help us if 
> you could try it now with your charts and please let us know if you 
> experience any problems.
>
> -- 
> Daniel LaLiberte  
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/5eb56be5-e779-489e-bdd5-1ae727e4e4c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Thomas]

Okay, thank you.

Chrome loads tooltip.css!


Chrome shows a second reference to a file called tooltip.css, now.
Chrome cannot resolve this second reference (> Open chart html file from 
local directory > F12 > Tab “Network”).

Furthermore, if a browser loads the chart resources using http, it loads 
some files using http, others files using https.
Would be great if browsers could use http respectively tls all the way down.


(If the reference changes will not solve the “overlap problem” => a very 
special case!, then I will try to prepare a fiddle, later.)

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/33b40443-d265-427a-ae0c-e5a76aa13cc3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Thomas,

The missing tooltip.css problem should be fixed now.

Not sure how you are seeing the overlap of the axis title and tick labels.
Can you give us a link, or create a jsfiddle to demonstrate it?  Thanks.

On Sat, Sep 5, 2015 at 9:26 AM, Thomas  wrote:

>
> Okay. Thx. Sometimes, some labels overlap. This might be the result of
> missing files, a "chain reaction".
>
>
>
>
>
> 
>
>
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/440705f0-feeb-43c6-949b-f4301447%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMjg1eLWU3X8kWVObtGw2D5oYowOqZ3pfh_OOy64u1UzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Thomas]

Okay. Thx. Sometimes, some labels overlap. This might be the result of 
missing files, a "chain reaction".


 





-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/440705f0-feeb-43c6-949b-f4301447%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Hi Thomas,

The tooltip.css file has a worse problem in that it is being loaded from
the wrong place entirely.  I'll have a fix for that as soon as I can get it
in.  Perhaps today.

On Fri, Sep 4, 2015 at 9:55 AM, Thomas  wrote:

> Hi Daniel
> I guess tooltip.css does have the "scheme problem", too. (There may be
> additional files.)
> Regards, Thomas
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/4d917679-2cef-48f6-b5c8-f379e299265d%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJPzokWDcgKTuh8PtBMx3N7M1peT-UykCfMZp%3DAx%3D_YeTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Thomas]

Hi Daniel
I guess tooltip.css does have the "scheme problem", too. (There may be 
additional files.)
Regards, Thomas

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/4d917679-2cef-48f6-b5c8-f379e299265d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Hi Rishu,

What you got when you loaded "1.0" up until sometime between Tuesday and
Wednesday (the rollout may have taken 24 hours this time) was v41, but now
it is v42.v41 is available via the frozen loader, as described in this
email announcement.

On Thu, Aug 27, 2015 at 1:03 PM, rishu oberoi  wrote:

> Hi,
>
> Changing to 1.0 version from 1 is no more showing up old UI of google
> tables. Do we have to use the frozen version for that?
>
> On Thursday, 27 August 2015 07:56:23 UTC-5, Daniel LaLiberte wrote:
>>
>> You can call google.charts.setOnLoadCallback() multiple times.  For the
>> same reason, I suppose we could allow google.charts.load() to be called
>> multiple times now if you only specify the 'callback' property rather than
>> load more packages.
>>
>> On Thu, Aug 27, 2015 at 8:43 AM, Henry Harrison 
>> wrote:
>>
>>> Legacy application that we haven't had the time to rewrite yet.  We have
>>> multiple charts on the same page with different functions that we use
>>> on callback. Definite room for improvement but the ability to use
>>> google.charts.load more than once was a simple workaround for us.
>>>
>>> --
>>> Date: Thu, 27 Aug 2015 08:28:32 -0400
>>> Subject: Re: [visualization-api] Re: Introducing Frozen Google Charts
>>> From: google-visua...@googlegroups.com
>>> To: google-visua...@googlegroups.com
>>>
>>>
>>> On Thu, Aug 27, 2015 at 8:15 AM, Henry Harrison 
>>> wrote:
>>>
>>> Hi Daniel
>>>
>>> Is there any timeline for a resolution on point 1 of using the frozen
>>> versions?
>>>   1. You can only call google.charts.load() one time.  You can instead
>>> list all the packages that you'll need in one call, so there is usually no
>>> need to make separate calls.
>>>
>>>
>>> No resolution yet.   It's been a lower priority since there is an easy
>>> workaround for most applications.  I'm curious why you need it.
>>>
>>> --
>>> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
>>>   - 978-394-1058
>>> dlali...@google.com   5CC, Cambridge MA
>>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>>
>>> --
>>> 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/hBCwxtXYNZ8/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> google-visualization-api+unsubscr...@googlegroups.com.
>>> To post to this group, send email to google-visua...@googlegroups.com.
>>> Visit this group at
>>> http://groups.google.com/group/google-visualization-api.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMJRkRir0s1apYf5uKnkD_ay_UEiqvA1Nv%2BJCZvSeePfg%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMJRkRir0s1apYf5uKnkD_ay_UEiqvA1Nv%2BJCZvSeePfg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>>> 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+unsubscr...@googlegroups.com.
>>> To post to this group, send email to google-visua...@googlegroups.com.
>>> Visit this group at
>>> http://groups.google.com/group/google-visualization-api.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-visualization-api/DUB131-W352569F494C552C3988F88A36F0%40phx.gbl
>>> <https://groups.google.com/d/msgid/google-visualization-api/DUB131-W352569F494C552C3988F88A36F0%40phx.gbl?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
>>  - 978-394-1058
>> dlali...@google.com   5CC, Cambridge MA
>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>
> --
> You received this message because you are subscribed to the Google Gro

Re: [visualization-api] Re: Introducing Frozen Google Charts

[rishu oberoi]

Hi, 

Changing to 1.0 version from 1 is no more showing up old UI of google 
tables. Do we have to use the frozen version for that?

On Thursday, 27 August 2015 07:56:23 UTC-5, Daniel LaLiberte wrote:
>
> You can call google.charts.setOnLoadCallback() multiple times.  For the 
> same reason, I suppose we could allow google.charts.load() to be called 
> multiple times now if you only specify the 'callback' property rather than 
> load more packages.
>
> On Thu, Aug 27, 2015 at 8:43 AM, Henry Harrison  > wrote:
>
>> Legacy application that we haven't had the time to rewrite yet.  We have 
>> multiple charts on the same page with different functions that we use 
>> on callback. Definite room for improvement but the ability to use 
>> google.charts.load more than once was a simple workaround for us.
>>  
>> ----------
>> Date: Thu, 27 Aug 2015 08:28:32 -0400
>> Subject: Re: [visualization-api] Re: Introducing Frozen Google Charts
>> From: google-visua...@googlegroups.com 
>> To: google-visua...@googlegroups.com 
>>
>>
>> On Thu, Aug 27, 2015 at 8:15 AM, Henry Harrison > > wrote:
>>
>> Hi Daniel
>>
>> Is there any timeline for a resolution on point 1 of using the frozen 
>> versions?
>>   1. You can only call google.charts.load() one time.  You can instead 
>> list all the packages that you'll need in one call, so there is usually no 
>> need to make separate calls. 
>>
>>
>> No resolution yet.   It's been a lower priority since there is an easy 
>> workaround for most applications.  I'm curious why you need it.
>>
>> -- 
>> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2> 
>>  - 978-394-1058
>> dlali...@google.com5CC, Cambridge MA
>> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>>
>> -- 
>> 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/hBCwxtXYNZ8/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> google-visualization-api+unsubscr...@googlegroups.com .
>> To post to this group, send email to google-visua...@googlegroups.com 
>> .
>> Visit this group at 
>> http://groups.google.com/group/google-visualization-api.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMJRkRir0s1apYf5uKnkD_ay_UEiqvA1Nv%2BJCZvSeePfg%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMJRkRir0s1apYf5uKnkD_ay_UEiqvA1Nv%2BJCZvSeePfg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>> -- 
>> 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+unsubscr...@googlegroups.com 
>> .
>> To post to this group, send email to google-visua...@googlegroups.com 
>> .
>> Visit this group at 
>> http://groups.google.com/group/google-visualization-api.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-visualization-api/DUB131-W352569F494C552C3988F88A36F0%40phx.gbl
>>  
>> <https://groups.google.com/d/msgid/google-visualization-api/DUB131-W352569F494C552C3988F88A36F0%40phx.gbl?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2> 
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/2377b13a-0762-4597-bbc4-323b01118819%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

You can call google.charts.setOnLoadCallback() multiple times.  For the
same reason, I suppose we could allow google.charts.load() to be called
multiple times now if you only specify the 'callback' property rather than
load more packages.

On Thu, Aug 27, 2015 at 8:43 AM, Henry Harrison  wrote:

> Legacy application that we haven't had the time to rewrite yet.  We have
> multiple charts on the same page with different functions that we use
> on callback. Definite room for improvement but the ability to use
> google.charts.load more than once was a simple workaround for us.
>
> --
> Date: Thu, 27 Aug 2015 08:28:32 -0400
> Subject: Re: [visualization-api] Re: Introducing Frozen Google Charts
> From: google-visualization-api@googlegroups.com
> To: google-visualization-api@googlegroups.com
>
>
> On Thu, Aug 27, 2015 at 8:15 AM, Henry Harrison  wrote:
>
> Hi Daniel
>
> Is there any timeline for a resolution on point 1 of using the frozen
> versions?
>   1. You can only call google.charts.load() one time.  You can instead
> list all the packages that you'll need in one call, so there is usually no
> need to make separate calls.
>
>
> No resolution yet.   It's been a lower priority since there is an easy
> workaround for most applications.  I'm curious why you need it.
>
> --
> Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
>  - 978-394-1058
> dlalibe...@google.com5CC, Cambridge MA
> daniel.lalibe...@gmail.com  9 Juniper Ridge
> Road, Acton MA
>
> --
> 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/hBCwxtXYNZ8/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-visualization-api+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMJRkRir0s1apYf5uKnkD_ay_UEiqvA1Nv%2BJCZvSeePfg%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMJRkRir0s1apYf5uKnkD_ay_UEiqvA1Nv%2BJCZvSeePfg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/DUB131-W352569F494C552C3988F88A36F0%40phx.gbl
> <https://groups.google.com/d/msgid/google-visualization-api/DUB131-W352569F494C552C3988F88A36F0%40phx.gbl?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>  -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJNFX1vFoNs_wfcT5aFuD22z%3DAhAk%3DiyGNGWaj3d%3DDCwXg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: [visualization-api] Re: Introducing Frozen Google Charts

[Henry Harrison]

Legacy application that we haven't had the time to rewrite yet.  We have 
multiple charts on the same page with different functions that we use on 
callback. Definite room for improvement but the ability to use 
google.charts.load more than once was a simple workaround for us.
 
Date: Thu, 27 Aug 2015 08:28:32 -0400
Subject: Re: [visualization-api] Re: Introducing Frozen Google Charts
From: google-visualization-api@googlegroups.com
To: google-visualization-api@googlegroups.com

On Thu, Aug 27, 2015 at 8:15 AM, Henry Harrison  wrote:
Hi Daniel
Is there any timeline for a resolution on point 1 of using the frozen versions? 
 1. You can only call google.charts.load() one time.  You can instead list all 
the packages that you'll need in one call, so there is usually no need to make 
separate calls. 

No resolution yet.   It's been a lower priority since there is an easy 
workaround for most applications.  I'm curious why you need it.
-- 
Daniel LaLiberte  - 978-394-1058
dlalibe...@google.com   5CC, Cambridge madaniel.lalibe...@gmail.com 9 Juniper 
Ridge Road, Acton MA





-- 

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/hBCwxtXYNZ8/unsubscribe.

To unsubscribe from this group and all its topics, send an email to 
google-visualization-api+unsubscr...@googlegroups.com.

To post to this group, send email to google-visualization-api@googlegroups.com.

Visit this group at http://groups.google.com/group/google-visualization-api.

To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMJRkRir0s1apYf5uKnkD_ay_UEiqvA1Nv%2BJCZvSeePfg%40mail.gmail.com.

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

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/DUB131-W352569F494C552C3988F88A36F0%40phx.gbl.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

On Thu, Aug 27, 2015 at 8:15 AM, Henry Harrison  wrote:

> Hi Daniel
>
> Is there any timeline for a resolution on point 1 of using the frozen
> versions?
>   1. You can only call google.charts.load() one time.  You can instead
> list all the packages that you'll need in one call, so there is usually no
> need to make separate calls.
>
>
No resolution yet.   It's been a lower priority since there is an easy
workaround for most applications.  I'm curious why you need it.

-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMJRkRir0s1apYf5uKnkD_ay_UEiqvA1Nv%2BJCZvSeePfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[visualization-api] Re: Introducing Frozen Google Charts

[Henry Harrison]

Hi Daniel

Is there any timeline for a resolution on point 1 of using the frozen 
versions?
  1. You can only call google.charts.load() one time.  You can instead list 
all the packages that you'll need in one call, so there is usually no need 
to make separate calls. 

Regards
Henry

On Tuesday, July 28, 2015 at 2:11:12 PM UTC+2, Daniel LaLiberte wrote:

> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes are 
> big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way of 
> loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted in 
> bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include the 
> ‘visualization’ parameter, and the version number is a string.  Only 
> version ‘41’ is supported at this time, which corresponds to the current 
> stable release, and additional frozen versions will be announced as we 
> push out each new stable release.  More details about using the frozen 
> version 
> loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and features 
> should work the same as for the stable version it was created from.  But 
> there 
> are two minor, though important, limitations with loading frozen versions, 
> which we expect to resolve in the near future.
>
>1. You can only call google.charts.load() one time.  You can instead 
>list all the packages that you'll need in one call, so there is usually no 
>need to make separate calls. 
>2. If you are using a ChartWrapper, you must explicitly load all the 
>packages you'll need rather than relying on the ChartWrapper to 
>automatically load them for you. 
>
> We expect that frozen versions will remain available indefinitely, though 
> we may retire frozen versions that have security concerns.  We will 
> typically not provide support for frozen versions, except to suggest 
> upgrading to newer versions.
>
> Even if you don't plan to use the frozen version 41, it would help us if 
> you could try it now with your charts and please let us know if you 
> experience any problems.
>
> -- 
> Daniel LaLiberte  
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/baca862b-882d-4d4e-befe-907650dea860%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Kevin Crawley]

Still having the same issue, loader.js fails at line 60. As noted, we're 
loading a page from our live servers with PhantomJS, so the protocol it's 
using should be http/https. I haven't tried Phantom 2.0, but 1.9.8 is not 
working.

On Wednesday, August 26, 2015 at 10:00:21 AM UTC-5, Daniel LaLiberte wrote:
>
> Kevin,
>
> I believe I fixed the problem of loading pages with schemes other than 
> http or https, so loading via PhantomJS might work now.
>
> On Wed, Aug 26, 2015 at 10:50 AM, Kevin Crawley  > wrote:
>
>> @Daniel
>>
>> Do you have any feedback regarding this issue. We are unable to deploy 
>> the frozen loader until it will work in PhantomJS. The file *is *being 
>> loaded from a web server; so I believe the problem we're experiencing is 
>> unrelated to the issue Thomas was having.
>>
>> Regards
>> -Kevin
>>
>>
>> On Monday, August 24, 2015 at 9:51:20 AM UTC-5, Kevin Crawley wrote:
>>>
>>> We're actually loading the page from a web server and PhantomJS has 
>>> outside network access. I managed to get the PhantomJS remote debugger 
>>> going and got some feedback from the loader.
>>>
>>> TypeError: 'undefined' is not an object (evaluating 'a[L]') [loader.js:
>>> 60]
>>>
>>>
>>> 'loadGoogleVisLibrary': function() {
>>> var deferred = Q.defer();
>>>
>>> google.charts.load("visualization", "1", {
>>> packages: ['corechart', 'table', 'gauge']
>>> });
>>>
>>> google.charts.setOnLoadCallback(function() {
>>> console.log('this will never happen');
>>> });
>>>
>>> setTimeout(function() {
>>> console('logically, google.load callback should have happened by now');
>>> }, 1500);
>>>
>>> return deferred.promise;
>>> },
>>>
>>>
>>>
>>>
>>>
>>> On Monday, August 24, 2015 at 7:23:17 AM UTC-5, Daniel LaLiberte wrote:

 Kevin,

 If you are using PhantomJS outside of a web page, that would explain 
 why the new loader is having a problem.  It currently assumes it can load 
 using the same scheme (http or https) as the page itself. This is similar 
 to the problem Thomas Schwab reported regarding charts in email.

 On Fri, Aug 21, 2015 at 4:43 PM, Kevin Crawley  
 wrote:

> We're having some trouble using the new loader in PhantomJS. It 
> appears the loader will not execute, and it's not giving any 
> feedback/errors.
>
>
> On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>
>> *Introducing Frozen Google Charts*
>>
>> When we push out new releases of Google Charts, some of the changes 
>> are big, like entirely new chart types, but other changes are small, 
>> like 
>> enhancements to the appearance or behavior of existing charts.  
>>
>> Many Google Chart creators fine-tune the look and feel of their 
>> charts until it's exactly what they want. Some of those users might feel 
>> more comfortable knowing that their charts will never change, regardless 
>> of 
>> what improvements we make in the future.  For those users, we're proud 
>> to 
>> announce Frozen Google Charts.  
>>
>> To load a frozen version, you must make some small changes in how you 
>> load the Google Charts packages.  For example, here is the usual way 
>> of loading the stable version and drawing a chart:
>>
>> >
>> src="https://www.google.com/jsapi";>
>>
>> 
>>
>>google.load('visualization', '1', {packages: ['corechart']});
>>
>>google.setOnLoadCallback(drawChart);
>>
>> 
>>
>> You'll need to change your code to be like this (changes highlighted 
>> in bold):
>>
>> >
>> src="*https://www.gstatic.com/charts/loader.js* 
>> <https://www.gstatic.com/charts/loader.js>">
>>
>> 
>>
>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>
>>*google.charts.setOnLoadCallback*(drawChart);
>> 
>>
>>
>> Note that when you call google.charts.load(), you should not include 
>> the ‘visualization’ parameter, and the version number is a string.  
>> Only version ‘41’ is supported at this time, which corresponds to the 
>> current stable release, and additional frozen versions will be 
>> announced as we push out each new stable release.  More details 
>> about using the frozen version loader will be available here 
>> 
>> .
>>
>>
>> When you use a frozen version of Google Charts, all charts and 
>> features should work the same as for the stable version it was created 
>> from.  But there are two minor, though important, limitations with 
>> loading frozen versions, which we expect to resolve in the near

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Kevin,

I believe I fixed the problem of loading pages with schemes other than http
or https, so loading via PhantomJS might work now.

On Wed, Aug 26, 2015 at 10:50 AM, Kevin Crawley 
wrote:

> @Daniel
>
> Do you have any feedback regarding this issue. We are unable to deploy the
> frozen loader until it will work in PhantomJS. The file *is *being loaded
> from a web server; so I believe the problem we're experiencing is unrelated
> to the issue Thomas was having.
>
> Regards
> -Kevin
>
>
> On Monday, August 24, 2015 at 9:51:20 AM UTC-5, Kevin Crawley wrote:
>>
>> We're actually loading the page from a web server and PhantomJS has
>> outside network access. I managed to get the PhantomJS remote debugger
>> going and got some feedback from the loader.
>>
>> TypeError: 'undefined' is not an object (evaluating 'a[L]') [loader.js:60
>> ]
>>
>>
>> 'loadGoogleVisLibrary': function() {
>> var deferred = Q.defer();
>>
>> google.charts.load("visualization", "1", {
>> packages: ['corechart', 'table', 'gauge']
>> });
>>
>> google.charts.setOnLoadCallback(function() {
>> console.log('this will never happen');
>> });
>>
>> setTimeout(function() {
>> console('logically, google.load callback should have happened by now');
>> }, 1500);
>>
>> return deferred.promise;
>> },
>>
>>
>>
>>
>>
>> On Monday, August 24, 2015 at 7:23:17 AM UTC-5, Daniel LaLiberte wrote:
>>>
>>> Kevin,
>>>
>>> If you are using PhantomJS outside of a web page, that would explain why
>>> the new loader is having a problem.  It currently assumes it can load using
>>> the same scheme (http or https) as the page itself. This is similar to the
>>> problem Thomas Schwab reported regarding charts in email.
>>>
>>> On Fri, Aug 21, 2015 at 4:43 PM, Kevin Crawley 
>>> wrote:
>>>
 We're having some trouble using the new loader in PhantomJS. It appears
 the loader will not execute, and it's not giving any feedback/errors.


 On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:

> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes
> are big, like entirely new chart types, but other changes are small, like
> enhancements to the appearance or behavior of existing charts.
>
> Many Google Chart creators fine-tune the look and feel of their charts
> until it's exactly what they want. Some of those users might feel more
> comfortable knowing that their charts will never change, regardless of 
> what
> improvements we make in the future.  For those users, we're proud to
> announce Frozen Google Charts.
>
> To load a frozen version, you must make some small changes in how you
> load the Google Charts packages.  For example, here is the usual way
> of loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted
> in bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js*
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include
> the ‘visualization’ parameter, and the version number is a string.
> Only version ‘41’ is supported at this time, which corresponds to the
> current stable release, and additional frozen versions will be
> announced as we push out each new stable release.  More details about
> using the frozen version loader will be available here
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and
> features should work the same as for the stable version it was created
> from.  But there are two minor, though important, limitations with
> loading frozen versions, which we expect to resolve in the near
> future.
>
>1. You can only call google.charts.load() one time.  You can
>instead list all the packages that you'll need in one call, so there is
>usually no need to make separate calls.
>2. If you are using a ChartWrapper, you must explicitly load all
>the packages you'll need rather than relying on the ChartWrapper to
>automatically load them for you.
>
> We expect that frozen versions will remain available indefinitely,
> thou

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Kevin Crawley]

@Daniel

Do you have any feedback regarding this issue. We are unable to deploy the 
frozen loader until it will work in PhantomJS. The file *is *being loaded 
from a web server; so I believe the problem we're experiencing is unrelated 
to the issue Thomas was having.

Regards
-Kevin

On Monday, August 24, 2015 at 9:51:20 AM UTC-5, Kevin Crawley wrote:
>
> We're actually loading the page from a web server and PhantomJS has 
> outside network access. I managed to get the PhantomJS remote debugger 
> going and got some feedback from the loader.
>
> TypeError: 'undefined' is not an object (evaluating 'a[L]') [loader.js:60]
>
>
> 'loadGoogleVisLibrary': function() {
> var deferred = Q.defer();
>
> google.charts.load("visualization", "1", {
> packages: ['corechart', 'table', 'gauge']
> });
>
> google.charts.setOnLoadCallback(function() {
> console.log('this will never happen');
> });
>
> setTimeout(function() {
> console('logically, google.load callback should have happened by now');
> }, 1500);
>
> return deferred.promise;
> },
>
>
>
>
>
> On Monday, August 24, 2015 at 7:23:17 AM UTC-5, Daniel LaLiberte wrote:
>>
>> Kevin,
>>
>> If you are using PhantomJS outside of a web page, that would explain why 
>> the new loader is having a problem.  It currently assumes it can load using 
>> the same scheme (http or https) as the page itself. This is similar to the 
>> problem Thomas Schwab reported regarding charts in email.
>>
>> On Fri, Aug 21, 2015 at 4:43 PM, Kevin Crawley  
>> wrote:
>>
>>> We're having some trouble using the new loader in PhantomJS. It appears 
>>> the loader will not execute, and it's not giving any feedback/errors.
>>>
>>>
>>> On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>>>
 *Introducing Frozen Google Charts*

 When we push out new releases of Google Charts, some of the changes are 
 big, like entirely new chart types, but other changes are small, like 
 enhancements to the appearance or behavior of existing charts.  

 Many Google Chart creators fine-tune the look and feel of their charts 
 until it's exactly what they want. Some of those users might feel more 
 comfortable knowing that their charts will never change, regardless of 
 what 
 improvements we make in the future.  For those users, we're proud to 
 announce Frozen Google Charts.  

 To load a frozen version, you must make some small changes in how you 
 load the Google Charts packages.  For example, here is the usual way 
 of loading the stable version and drawing a chart:

 >>>
 src="https://www.google.com/jsapi";>

 

google.load('visualization', '1', {packages: ['corechart']});

google.setOnLoadCallback(drawChart);

 

 You'll need to change your code to be like this (changes highlighted in 
 bold):

 >>>
 src="*https://www.gstatic.com/charts/loader.js* 
 <https://www.gstatic.com/charts/loader.js>">

 

*google.charts.load(**'41'**,* {packages: ['corechart']});

*google.charts.setOnLoadCallback*(drawChart);
 


 Note that when you call google.charts.load(), you should not include 
 the ‘visualization’ parameter, and the version number is a string.  
 Only version ‘41’ is supported at this time, which corresponds to the 
 current stable release, and additional frozen versions will be 
 announced as we push out each new stable release.  More details about 
 using the frozen version loader will be available here 
 
 .


 When you use a frozen version of Google Charts, all charts and 
 features should work the same as for the stable version it was created 
 from.  But there are two minor, though important, limitations with 
 loading frozen versions, which we expect to resolve in the near future.

1. You can only call google.charts.load() one time.  You can 
instead list all the packages that you'll need in one call, so there is 
usually no need to make separate calls. 
2. If you are using a ChartWrapper, you must explicitly load all 
the packages you'll need rather than relying on the ChartWrapper to 
automatically load them for you. 

 We expect that frozen versions will remain available indefinitely, 
 though we may retire frozen versions that have security concerns.  We will 
 typically not provide support for frozen versions, except to suggest 
 upgrading to newer versions.

 Even if you don't plan to use the frozen version 41, it would help us 
 if you could try it now with your

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Thomas]

Works ... thank you! Thomas



-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/af4516dc-0ef8-4ea6-aadb-417f0fad45b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

The frozen version (in your first jsfiddle) appears to be loading find
then.  We can deal with your issues with the table chart in the other
thread.

On Mon, Aug 24, 2015 at 5:06 PM, Paul Benson  wrote:

> Daniel, I might be doing something wrong, but in the mean time here is my
> issue.
>
>
> In this example, I set up using jfiddle to show how it used to work. If I
> have 4 rows, it will show 4 rows with a normal row height.
> https://jsfiddle.net/zftetxa3/
>
> With the latest version it will fit the rows to the chart height, which
> gives it an odd look
> https://jsfiddle.net/5ed4oeLe/
>
> On Monday, August 24, 2015 at 3:58:00 PM UTC-5, Daniel LaLiberte wrote:
>>
>> Hi Paul,
>>
>> I don't understand why you can't call
>> google.charts.setOnLoadCallback(drawTable) when you want the drawTable
>> function to be called (once the Google Charts code has been loaded).  How
>> is this different from when you would use google.load() and
>> google.setOnLoadCallback()?
>>
>> On Mon, Aug 24, 2015 at 4:53 PM, Paul Benson  wrote:
>>
>>> We are using dynamic chart creation, so I can not specify
>>> "google.charts.setOnLoadCallback(drawTable);" so javascript is failing when
>>> I try to reference google.visualization.DateTable, or anything else using
>>> google.visualization
>>>
>>> I am using the google.charts.load() as well as the other changes
>>> highlighted above.
>>>
>>> On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:

 *Introducing Frozen Google Charts*

 When we push out new releases of Google Charts, some of the changes are
 big, like entirely new chart types, but other changes are small, like
 enhancements to the appearance or behavior of existing charts.

 Many Google Chart creators fine-tune the look and feel of their charts
 until it's exactly what they want. Some of those users might feel more
 comfortable knowing that their charts will never change, regardless of what
 improvements we make in the future.  For those users, we're proud to
 announce Frozen Google Charts.

 To load a frozen version, you must make some small changes in how you
 load the Google Charts packages.  For example, here is the usual way
 of loading the stable version and drawing a chart:

 >>>
 src="https://www.google.com/jsapi";>

 

google.load('visualization', '1', {packages: ['corechart']});

google.setOnLoadCallback(drawChart);

 

 You'll need to change your code to be like this (changes highlighted
 in bold):

 >>>
 src="*https://www.gstatic.com/charts/loader.js*
 <https://www.gstatic.com/charts/loader.js>">

 

*google.charts.load(**'41'**,* {packages: ['corechart']});

*google.charts.setOnLoadCallback*(drawChart);
 


 Note that when you call google.charts.load(), you should not include
 the ‘visualization’ parameter, and the version number is a string.
 Only version ‘41’ is supported at this time, which corresponds to the
 current stable release, and additional frozen versions will be
 announced as we push out each new stable release.  More details about
 using the frozen version loader will be available here
 
 .


 When you use a frozen version of Google Charts, all charts and
 features should work the same as for the stable version it was created
 from.  But there are two minor, though important, limitations with
 loading frozen versions, which we expect to resolve in the near future.

1. You can only call google.charts.load() one time.  You can
instead list all the packages that you'll need in one call, so there is
usually no need to make separate calls.
2. If you are using a ChartWrapper, you must explicitly load all
the packages you'll need rather than relying on the ChartWrapper to
automatically load them for you.

 We expect that frozen versions will remain available indefinitely,
 though we may retire frozen versions that have security concerns.  We will
 typically not provide support for frozen versions, except to suggest
 upgrading to newer versions.

 Even if you don't plan to use the frozen version 41, it would help us
 if you could try it now with your charts and please let us know if you
 experience any problems.

 --
 Daniel LaLiberte
   - 978-394-1058
 dlali...@google.com   5CC, Cambridge MA
 daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA

>>> --
>>> You received this 

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Paul Benson]

Daniel, I might be doing something wrong, but in the mean time here is my 
issue.


In this example, I set up using jfiddle to show how it used to work. If I 
have 4 rows, it will show 4 rows with a normal row height. 
https://jsfiddle.net/zftetxa3/

With the latest version it will fit the rows to the chart height, which 
gives it an odd look
https://jsfiddle.net/5ed4oeLe/

On Monday, August 24, 2015 at 3:58:00 PM UTC-5, Daniel LaLiberte wrote:
>
> Hi Paul,
>
> I don't understand why you can't call 
> google.charts.setOnLoadCallback(drawTable) when you want the drawTable 
> function to be called (once the Google Charts code has been loaded).  How 
> is this different from when you would use google.load() and 
> google.setOnLoadCallback()?
>
> On Mon, Aug 24, 2015 at 4:53 PM, Paul Benson  > wrote:
>
>> We are using dynamic chart creation, so I can not specify 
>> "google.charts.setOnLoadCallback(drawTable);" so javascript is failing when 
>> I try to reference google.visualization.DateTable, or anything else using 
>> google.visualization
>>
>> I am using the google.charts.load() as well as the other changes 
>> highlighted above.
>>
>> On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>>>
>>> *Introducing Frozen Google Charts*
>>>
>>> When we push out new releases of Google Charts, some of the changes are 
>>> big, like entirely new chart types, but other changes are small, like 
>>> enhancements to the appearance or behavior of existing charts.  
>>>
>>> Many Google Chart creators fine-tune the look and feel of their charts 
>>> until it's exactly what they want. Some of those users might feel more 
>>> comfortable knowing that their charts will never change, regardless of what 
>>> improvements we make in the future.  For those users, we're proud to 
>>> announce Frozen Google Charts.  
>>>
>>> To load a frozen version, you must make some small changes in how you 
>>> load the Google Charts packages.  For example, here is the usual way of 
>>> loading the stable version and drawing a chart:
>>>
>>> >>
>>> src="https://www.google.com/jsapi";>
>>>
>>> 
>>>
>>>google.load('visualization', '1', {packages: ['corechart']});
>>>
>>>google.setOnLoadCallback(drawChart);
>>>
>>> 
>>>
>>> You'll need to change your code to be like this (changes highlighted in 
>>> bold):
>>>
>>> >>
>>> src="*https://www.gstatic.com/charts/loader.js* 
>>> <https://www.gstatic.com/charts/loader.js>">
>>>
>>> 
>>>
>>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>>
>>>*google.charts.setOnLoadCallback*(drawChart);
>>> 
>>>
>>>
>>> Note that when you call google.charts.load(), you should not include 
>>> the ‘visualization’ parameter, and the version number is a string.  
>>> Only version ‘41’ is supported at this time, which corresponds to the 
>>> current stable release, and additional frozen versions will be 
>>> announced as we push out each new stable release.  More details about 
>>> using the frozen version loader will be available here 
>>> 
>>> .
>>>
>>>
>>> When you use a frozen version of Google Charts, all charts and features 
>>> should work the same as for the stable version it was created from.  But 
>>> there 
>>> are two minor, though important, limitations with loading frozen versions, 
>>> which we expect to resolve in the near future.
>>>
>>>1. You can only call google.charts.load() one time.  You can instead 
>>>list all the packages that you'll need in one call, so there is usually 
>>> no 
>>>need to make separate calls. 
>>>2. If you are using a ChartWrapper, you must explicitly load all the 
>>>packages you'll need rather than relying on the ChartWrapper to 
>>>automatically load them for you. 
>>>
>>> We expect that frozen versions will remain available indefinitely, 
>>> though we may retire frozen versions that have security concerns.  We will 
>>> typically not provide support for frozen versions, except to suggest 
>>> upgrading to newer versions.
>>>
>>> Even if you don't plan to use the frozen version 41, it would help us 
>>> if you could try it now with your charts and please let us know if you 
>>> experience any problems.
>>>
>>> -- 
>>> Daniel LaLiberte 
>>>   - 978-394-1058
>>> dlali...@google.com   5CC, Cambridge MA
>>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>>
>> -- 
>> 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+unsubscr...@googlegroups.com 
>> .
>> To post to this group

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Hi Paul,

I don't understand why you can't call
google.charts.setOnLoadCallback(drawTable) when you want the drawTable
function to be called (once the Google Charts code has been loaded).  How
is this different from when you would use google.load() and
google.setOnLoadCallback()?

On Mon, Aug 24, 2015 at 4:53 PM, Paul Benson  wrote:

> We are using dynamic chart creation, so I can not specify
> "google.charts.setOnLoadCallback(drawTable);" so javascript is failing when
> I try to reference google.visualization.DateTable, or anything else using
> google.visualization
>
> I am using the google.charts.load() as well as the other changes
> highlighted above.
>
> On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>>
>> *Introducing Frozen Google Charts*
>>
>> When we push out new releases of Google Charts, some of the changes are
>> big, like entirely new chart types, but other changes are small, like
>> enhancements to the appearance or behavior of existing charts.
>>
>> Many Google Chart creators fine-tune the look and feel of their charts
>> until it's exactly what they want. Some of those users might feel more
>> comfortable knowing that their charts will never change, regardless of what
>> improvements we make in the future.  For those users, we're proud to
>> announce Frozen Google Charts.
>>
>> To load a frozen version, you must make some small changes in how you
>> load the Google Charts packages.  For example, here is the usual way of
>> loading the stable version and drawing a chart:
>>
>> >
>> src="https://www.google.com/jsapi";>
>>
>> 
>>
>>google.load('visualization', '1', {packages: ['corechart']});
>>
>>google.setOnLoadCallback(drawChart);
>>
>> 
>>
>> You'll need to change your code to be like this (changes highlighted in
>> bold):
>>
>> >
>> src="*https://www.gstatic.com/charts/loader.js*
>> <https://www.gstatic.com/charts/loader.js>">
>>
>> 
>>
>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>
>>*google.charts.setOnLoadCallback*(drawChart);
>> 
>>
>>
>> Note that when you call google.charts.load(), you should not include the
>> ‘visualization’ parameter, and the version number is a string.  Only
>> version ‘41’ is supported at this time, which corresponds to the current
>> stable release, and additional frozen versions will be announced as we
>> push out each new stable release.  More details about using the frozen 
>> version
>> loader will be available here
>> 
>> .
>>
>>
>> When you use a frozen version of Google Charts, all charts and features
>> should work the same as for the stable version it was created from.  But 
>> there
>> are two minor, though important, limitations with loading frozen versions,
>> which we expect to resolve in the near future.
>>
>>1. You can only call google.charts.load() one time.  You can instead
>>list all the packages that you'll need in one call, so there is usually no
>>need to make separate calls.
>>2. If you are using a ChartWrapper, you must explicitly load all the
>>packages you'll need rather than relying on the ChartWrapper to
>>automatically load them for you.
>>
>> We expect that frozen versions will remain available indefinitely, though
>> we may retire frozen versions that have security concerns.  We will
>> typically not provide support for frozen versions, except to suggest
>> upgrading to newer versions.
>>
>> Even if you don't plan to use the frozen version 41, it would help us if
>> you could try it now with your charts and please let us know if you
>> experience any problems.
>>
>> --
>> Daniel LaLiberte 
>>  - 978-394-1058
>> dlali...@google.com   5CC, Cambridge MA
>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/de90d1cf-ec12-4f4f-a963-ca1ed450c212%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058

[visualization-api] Re: Introducing Frozen Google Charts

[Paul Benson]

We are using dynamic chart creation, so I can not specify 
"google.charts.setOnLoadCallback(drawTable);" so javascript is failing when 
I try to reference google.visualization.DateTable, or anything else using 
google.visualization

I am using the google.charts.load() as well as the other changes 
highlighted above.

On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>
> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes are 
> big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way of 
> loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted in 
> bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include the 
> ‘visualization’ parameter, and the version number is a string.  Only 
> version ‘41’ is supported at this time, which corresponds to the current 
> stable release, and additional frozen versions will be announced as we 
> push out each new stable release.  More details about using the frozen 
> version 
> loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and features 
> should work the same as for the stable version it was created from.  But 
> there 
> are two minor, though important, limitations with loading frozen versions, 
> which we expect to resolve in the near future.
>
>1. You can only call google.charts.load() one time.  You can instead 
>list all the packages that you'll need in one call, so there is usually no 
>need to make separate calls. 
>2. If you are using a ChartWrapper, you must explicitly load all the 
>packages you'll need rather than relying on the ChartWrapper to 
>automatically load them for you. 
>
> We expect that frozen versions will remain available indefinitely, though 
> we may retire frozen versions that have security concerns.  We will 
> typically not provide support for frozen versions, except to suggest 
> upgrading to newer versions.
>
> Even if you don't plan to use the frozen version 41, it would help us if 
> you could try it now with your charts and please let us know if you 
> experience any problems.
>
> -- 
> Daniel LaLiberte  
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/de90d1cf-ec12-4f4f-a963-ca1ed450c212%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Kevin Crawley]

We're actually loading the page from a web server and PhantomJS has outside 
network access. I managed to get the PhantomJS remote debugger going and 
got some feedback from the loader.

TypeError: 'undefined' is not an object (evaluating 'a[L]') [loader.js:60]


'loadGoogleVisLibrary': function() {
var deferred = Q.defer();

google.charts.load("visualization", "1", {
packages: ['corechart', 'table', 'gauge']
});

google.charts.setOnLoadCallback(function() {
console.log('this will never happen');
});

setTimeout(function() {
console('logically, google.load callback should have happened by now');
}, 1500);

return deferred.promise;
},





On Monday, August 24, 2015 at 7:23:17 AM UTC-5, Daniel LaLiberte wrote:
>
> Kevin,
>
> If you are using PhantomJS outside of a web page, that would explain why 
> the new loader is having a problem.  It currently assumes it can load using 
> the same scheme (http or https) as the page itself. This is similar to the 
> problem Thomas Schwab reported regarding charts in email.
>
> On Fri, Aug 21, 2015 at 4:43 PM, Kevin Crawley  > wrote:
>
>> We're having some trouble using the new loader in PhantomJS. It appears 
>> the loader will not execute, and it's not giving any feedback/errors.
>>
>>
>> On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>>
>>> *Introducing Frozen Google Charts*
>>>
>>> When we push out new releases of Google Charts, some of the changes are 
>>> big, like entirely new chart types, but other changes are small, like 
>>> enhancements to the appearance or behavior of existing charts.  
>>>
>>> Many Google Chart creators fine-tune the look and feel of their charts 
>>> until it's exactly what they want. Some of those users might feel more 
>>> comfortable knowing that their charts will never change, regardless of what 
>>> improvements we make in the future.  For those users, we're proud to 
>>> announce Frozen Google Charts.  
>>>
>>> To load a frozen version, you must make some small changes in how you 
>>> load the Google Charts packages.  For example, here is the usual way of 
>>> loading the stable version and drawing a chart:
>>>
>>> >>
>>> src="https://www.google.com/jsapi";>
>>>
>>> 
>>>
>>>google.load('visualization', '1', {packages: ['corechart']});
>>>
>>>google.setOnLoadCallback(drawChart);
>>>
>>> 
>>>
>>> You'll need to change your code to be like this (changes highlighted in 
>>> bold):
>>>
>>> >>
>>> src="*https://www.gstatic.com/charts/loader.js* 
>>> <https://www.gstatic.com/charts/loader.js>">
>>>
>>> 
>>>
>>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>>
>>>*google.charts.setOnLoadCallback*(drawChart);
>>> 
>>>
>>>
>>> Note that when you call google.charts.load(), you should not include 
>>> the ‘visualization’ parameter, and the version number is a string.  
>>> Only version ‘41’ is supported at this time, which corresponds to the 
>>> current stable release, and additional frozen versions will be 
>>> announced as we push out each new stable release.  More details about 
>>> using the frozen version loader will be available here 
>>> 
>>> .
>>>
>>>
>>> When you use a frozen version of Google Charts, all charts and features 
>>> should work the same as for the stable version it was created from.  But 
>>> there 
>>> are two minor, though important, limitations with loading frozen versions, 
>>> which we expect to resolve in the near future.
>>>
>>>1. You can only call google.charts.load() one time.  You can instead 
>>>list all the packages that you'll need in one call, so there is usually 
>>> no 
>>>need to make separate calls. 
>>>2. If you are using a ChartWrapper, you must explicitly load all the 
>>>packages you'll need rather than relying on the ChartWrapper to 
>>>automatically load them for you. 
>>>
>>> We expect that frozen versions will remain available indefinitely, 
>>> though we may retire frozen versions that have security concerns.  We will 
>>> typically not provide support for frozen versions, except to suggest 
>>> upgrading to newer versions.
>>>
>>> Even if you don't plan to use the frozen version 41, it would help us if 
>>> you could try it now with your charts and please let us know if you 
>>> experience any problems.
>>>
>>> -- 
>>> Daniel LaLiberte 
>>>   - 978-394-1058
>>> dlali...@google.com   5CC, Cambridge MA
>>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>>
>> -- 
>> 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 

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Kevin,

If you are using PhantomJS outside of a web page, that would explain why
the new loader is having a problem.  It currently assumes it can load using
the same scheme (http or https) as the page itself. This is similar to the
problem Thomas Schwab reported regarding charts in email.

On Fri, Aug 21, 2015 at 4:43 PM, Kevin Crawley  wrote:

> We're having some trouble using the new loader in PhantomJS. It appears
> the loader will not execute, and it's not giving any feedback/errors.
>
>
> On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>
>> *Introducing Frozen Google Charts*
>>
>> When we push out new releases of Google Charts, some of the changes are
>> big, like entirely new chart types, but other changes are small, like
>> enhancements to the appearance or behavior of existing charts.
>>
>> Many Google Chart creators fine-tune the look and feel of their charts
>> until it's exactly what they want. Some of those users might feel more
>> comfortable knowing that their charts will never change, regardless of what
>> improvements we make in the future.  For those users, we're proud to
>> announce Frozen Google Charts.
>>
>> To load a frozen version, you must make some small changes in how you
>> load the Google Charts packages.  For example, here is the usual way of
>> loading the stable version and drawing a chart:
>>
>> >
>> src="https://www.google.com/jsapi";>
>>
>> 
>>
>>google.load('visualization', '1', {packages: ['corechart']});
>>
>>google.setOnLoadCallback(drawChart);
>>
>> 
>>
>> You'll need to change your code to be like this (changes highlighted in
>> bold):
>>
>> >
>> src="*https://www.gstatic.com/charts/loader.js*
>> <https://www.gstatic.com/charts/loader.js>">
>>
>> 
>>
>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>
>>*google.charts.setOnLoadCallback*(drawChart);
>> 
>>
>>
>> Note that when you call google.charts.load(), you should not include the
>> ‘visualization’ parameter, and the version number is a string.  Only
>> version ‘41’ is supported at this time, which corresponds to the current
>> stable release, and additional frozen versions will be announced as we
>> push out each new stable release.  More details about using the frozen 
>> version
>> loader will be available here
>> 
>> .
>>
>>
>> When you use a frozen version of Google Charts, all charts and features
>> should work the same as for the stable version it was created from.  But 
>> there
>> are two minor, though important, limitations with loading frozen versions,
>> which we expect to resolve in the near future.
>>
>>1. You can only call google.charts.load() one time.  You can instead
>>list all the packages that you'll need in one call, so there is usually no
>>need to make separate calls.
>>2. If you are using a ChartWrapper, you must explicitly load all the
>>packages you'll need rather than relying on the ChartWrapper to
>>automatically load them for you.
>>
>> We expect that frozen versions will remain available indefinitely, though
>> we may retire frozen versions that have security concerns.  We will
>> typically not provide support for frozen versions, except to suggest
>> upgrading to newer versions.
>>
>> Even if you don't plan to use the frozen version 41, it would help us if
>> you could try it now with your charts and please let us know if you
>> experience any problems.
>>
>> --
>> Daniel LaLiberte 
>>  - 978-394-1058
>> dlali...@google.com   5CC, Cambridge MA
>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/2bcf2637-da51-4513-a61c-6209d2f7a432%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
You received this message because you are subscribed to the Googl

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Thomas, thanks for your report.  I see that the reason this fails is that
the loader is attempting to load using the same scheme as the page, which
would be fine for web pages, but we should use the same scheme as the
loader itself was loaded with.  I should be able to fix this in a couple
hours.


On Mon, Aug 24, 2015 at 7:25 AM, Thomas  wrote:

> The frozen version works if the chart html file is hosted on a web server.
>
> However, if a user opens the same chart html file from a local directory,
> loader cannot load util.css.
> Chrome > F12 shows:
>
>
>
> 
>
>
>
> The loader fails.
> This behavior of frozen version (41) differs from behavior of “maintained
> version” (1).
> A chart html file may be hosted but not mailed.
> => Would be great if frozen version would behave like maintained version
> (for http and https).
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/0bb62d14-0927-44d4-b9f9-2492d530cc98%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJOcD0QUBCG0ZbsGzwXy-89zCZpK8aD3O1vdhcNuuzyuEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[visualization-api] Re: Introducing Frozen Google Charts

[Thomas]

The frozen version works if the chart html file is hosted on a web server.

However, if a user opens the same chart html file from a local directory, 
loader cannot load util.css.
Chrome > F12 shows:






The loader fails.
This behavior of frozen version (41) differs from behavior of “maintained 
version” (1).
A chart html file may be hosted but not mailed.
=> Would be great if frozen version would behave like maintained version 
(for http and https).   

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/0bb62d14-0927-44d4-b9f9-2492d530cc98%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[visualization-api] Re: Introducing Frozen Google Charts

[Kevin Crawley]

We're having some trouble using the new loader in PhantomJS. It appears the 
loader will not execute, and it's not giving any feedback/errors.

On Tuesday, July 28, 2015 at 7:11:12 AM UTC-5, Daniel LaLiberte wrote:
>
> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes are 
> big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way of 
> loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted in 
> bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include the 
> ‘visualization’ parameter, and the version number is a string.  Only 
> version ‘41’ is supported at this time, which corresponds to the current 
> stable release, and additional frozen versions will be announced as we 
> push out each new stable release.  More details about using the frozen 
> version 
> loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and features 
> should work the same as for the stable version it was created from.  But 
> there 
> are two minor, though important, limitations with loading frozen versions, 
> which we expect to resolve in the near future.
>
>1. You can only call google.charts.load() one time.  You can instead 
>list all the packages that you'll need in one call, so there is usually no 
>need to make separate calls. 
>2. If you are using a ChartWrapper, you must explicitly load all the 
>packages you'll need rather than relying on the ChartWrapper to 
>automatically load them for you. 
>
> We expect that frozen versions will remain available indefinitely, though 
> we may retire frozen versions that have security concerns.  We will 
> typically not provide support for frozen versions, except to suggest 
> upgrading to newer versions.
>
> Even if you don't plan to use the frozen version 41, it would help us if 
> you could try it now with your charts and please let us know if you 
> experience any problems.
>
> -- 
> Daniel LaLiberte  
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/2bcf2637-da51-4513-a61c-6209d2f7a432%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Mark]

Works! Thanks Daniel!

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/fa26910c-6afb-40b9-86e8-5a4e5051c777%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Mark,

It sounds like you are still using google.load().  If you are trying to use
the frozen version, you need to change that too google.charts.load(), and
follow the rest of the instructions as well.

On Thu, Aug 20, 2015 at 6:20 AM, Mark  wrote:

> Hi,
>>
>
> I'm getting the following:
>
> Uncaught Error: Module: 'visualization' with version: '41' not found!
>
> var error = new Error("Module: 'visualization' with version: '41' not
> found!");
> error.toString = function() { return this.message; }
> throw error;
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/8f474e03-adf1-48d8-a606-a23f45e36c44%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJO2%3DNEXBgH-7UAJ9ZwfNJTfp9wKawxCGODmHgbQhrvECQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[visualization-api] Re: Introducing Frozen Google Charts

[Mark]

>
> Hi,
>

I'm getting the following:

Uncaught Error: Module: 'visualization' with version: '41' not found!

var error = new Error("Module: 'visualization' with version: '41' not 
found!");
error.toString = function() { return this.message; }
throw error;

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/8f474e03-adf1-48d8-a606-a23f45e36c44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Patrick Beaudan]

Daniel, thanks very much for your attention. It now all works, with the
current chart library. What I did is put in the call to multiple chart
types in each of my javascript functions calling the charts eg below. This
way the first of these functions on each page calls all the necessary
packages that become available to all other function calls. The reason that
my charts were working on some pages and not on others seemed to have been
the order in which "gauge" and 'corechart" where called. If gauge was
called first, I got the gauges but no line or bar charts, and if corechart
was called first it was the reverse. by calling all packages in all
functions, the order no longer matters.

Thanks!

google.load("visualization", "1.0", {packages:["gauge, corechart"]});

google.setOnLoadCallback(drawChart);
function drawChart() {
$.ajax({
url: "/charts/chart_handler.php?chart=risk_return_gauge",
dataType:"json",
success: function (jsonData) {
 var data = new google.visualization.DataTable(jsonData);   //
Create our data table out of JSON data loaded from server.
 var options = {
  width: 150, height: 150,
  yellowFrom: 75, yellowTo: 100,
  greenFrom: 25, greenTo: 75,
  minorTicks: 5
  };

var chart = new
google.visualization.Gauge(document.getElementById('chart_riskReturnGauge'));
chart.draw(data, options);
}
});
}

On Wed, Aug 19, 2015 at 10:19 AM, 'Daniel LaLiberte' via Google
Visualization API  wrote:

> I should qualify that a bit.  Mixing google.load('visualization', ...) and
> google.charts.load() on the same page will cause problems because they are
> both trying to load code into the same symbols, google.visualization and
> google.charts.  However, you could reasonably load (with google.load())
> other libraries other than 'visualization'.
>
> On Wed, Aug 19, 2015 at 12:36 PM, Daniel LaLiberte 
> wrote:
>
>> Patrick,
>>
>> Mixing google.load() and google.charts.load() in the same page is bound
>> to cause problems.  I wouldn't recommend even trying it.
>>
>> The packages property is an array, so just list all the packages you
>> need.  e.g. packages: ['corechart', 'gauge'].
>>
>>
>> On Wed, Aug 19, 2015 at 12:27 PM, Patrick Beaudan 
>> wrote:
>>
>>> Daniel, thanks very much for taking a look. What would be the way to
>>> call all at once for bar charts, bubble charts, line charts? Can I have a
>>> call to the frozen library and the current library on the same page (that
>>> seems to work but only partially)?
>>>
>>> All seems to work as before on some pages (for instance see
>>> http://www.beladv.com/strategySummary.php?strategy=AllWeatherUltra_BA),
>>> where the charts are called using the following script on the page:
>>>
>>>  https://www.google.com/jsapi";>
>>>
>>>  >> src="charts/portfolioAnalyzer/call_rollingQuarterly.php">
>>>  >> src="charts/portfolioAnalyzer/call_quarterlyZscore.php">
>>>
>>> etc ...
>>> But on some other pages I'm getting "draw()" errors and tried to
>>> incorporate your frozen version with only partial success like so on our
>>> homepage (www.beladv.com)
>>>
>>> https://www.gstatic.com/charts/loader.js";>   
>>> https://www.google.com/jsapi";>
>>>   
>>> 
>>> 
>>> >> src="charts/homePage/call_subAssetAlloc.php">
>>> >> src="charts/homePage/call_NAVgrowth.php">
>>> >> src="charts/homePage/call_riskReturnGauge_small.php"> 
>>>
>>> To generate the charts we call individual functions for each chart, and
>>> each function has a call to load, for instance for the last in the list
>>> above the function is:
>>>
>>> google.charts.load("41", {packages:["gauge"]});
>>> google.charts.setOnLoadCallback(drawChart);
>>> // google.load("visualization", "1.0", {packages:["gauge"]});
>>> // google.setOnLoadCallback(drawChart);
>>>
>>> function drawChart() {
>>> $.ajax({
>>> url: "charts/chart_handler.php?chart=risk_return_gauge",
>>>
>>> dataType:"json",
>>> success: function (jsonData) {
>>>//var data = new
>>> google.visualization.arrayToDataTable(jsonData);   // Create our data
>>> table out of JSON data loaded from server.
>>>var data = new google.visualization.DataTable(jsonData);   //
>>> Create our data table out of JSON data loaded from server.
>>> var options = {
>>> width: 150, height: 150,
>>> yellowFrom: 75, yellowTo: 100,
>>> greenFrom: 25, greenTo: 75,
>>> minorTicks: 5
>>> };
>>>
>>> var chart = new
>>> google.visualization.Gauge(document.getElementById('chart_riskReturnGauge_small'));
>>> chart.draw(data, options);
>>> }
>>> });
>>> }
>>>
>>> while for the chart above that (call_NAVgrowth) the function (which
>>> still works) is:
>>>
>>> google.load('visualization', '1.0', {'packages':['corechart']}); //
>>> Load the

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

I should qualify that a bit.  Mixing google.load('visualization', ...) and
google.charts.load() on the same page will cause problems because they are
both trying to load code into the same symbols, google.visualization and
google.charts.  However, you could reasonably load (with google.load())
other libraries other than 'visualization'.

On Wed, Aug 19, 2015 at 12:36 PM, Daniel LaLiberte 
wrote:

> Patrick,
>
> Mixing google.load() and google.charts.load() in the same page is bound to
> cause problems.  I wouldn't recommend even trying it.
>
> The packages property is an array, so just list all the packages you need.
>  e.g. packages: ['corechart', 'gauge'].
>
>
> On Wed, Aug 19, 2015 at 12:27 PM, Patrick Beaudan 
> wrote:
>
>> Daniel, thanks very much for taking a look. What would be the way to call
>> all at once for bar charts, bubble charts, line charts? Can I have a call
>> to the frozen library and the current library on the same page (that seems
>> to work but only partially)?
>>
>> All seems to work as before on some pages (for instance see
>> http://www.beladv.com/strategySummary.php?strategy=AllWeatherUltra_BA),
>> where the charts are called using the following script on the page:
>>
>>  https://www.google.com/jsapi";>
>>
>>  > src="charts/portfolioAnalyzer/call_rollingQuarterly.php">
>>  > src="charts/portfolioAnalyzer/call_quarterlyZscore.php">
>>
>> etc ...
>> But on some other pages I'm getting "draw()" errors and tried to
>> incorporate your frozen version with only partial success like so on our
>> homepage (www.beladv.com)
>>
>> https://www.gstatic.com/charts/loader.js";>   
>> https://www.google.com/jsapi";>
>>   
>> 
>> 
>> > src="charts/homePage/call_subAssetAlloc.php">
>> > src="charts/homePage/call_NAVgrowth.php">
>> > src="charts/homePage/call_riskReturnGauge_small.php"> 
>>
>> To generate the charts we call individual functions for each chart, and
>> each function has a call to load, for instance for the last in the list
>> above the function is:
>>
>> google.charts.load("41", {packages:["gauge"]});
>> google.charts.setOnLoadCallback(drawChart);
>> // google.load("visualization", "1.0", {packages:["gauge"]});
>> // google.setOnLoadCallback(drawChart);
>>
>> function drawChart() {
>> $.ajax({
>> url: "charts/chart_handler.php?chart=risk_return_gauge",
>> dataType:"json",
>> success: function (jsonData) {
>>//var data = new
>> google.visualization.arrayToDataTable(jsonData);   // Create our data
>> table out of JSON data loaded from server.
>>var data = new google.visualization.DataTable(jsonData);   //
>> Create our data table out of JSON data loaded from server.
>> var options = {
>> width: 150, height: 150,
>> yellowFrom: 75, yellowTo: 100,
>> greenFrom: 25, greenTo: 75,
>> minorTicks: 5
>> };
>>
>> var chart = new
>> google.visualization.Gauge(document.getElementById('chart_riskReturnGauge_small'));
>> chart.draw(data, options);
>> }
>> });
>> }
>>
>> while for the chart above that (call_NAVgrowth) the function (which still
>> works) is:
>>
>> google.load('visualization', '1.0', {'packages':['corechart']}); //
>> Load the Visualization API and the piechart package.
>> google.setOnLoadCallback(drawChart); // Set a callback to run when
>> the Google Visualization API is loaded.
>>
>> // Callback that creates and populates a data table, instantiates the
>> chart, passes in the data and draws it.
>> function drawChart() {
>> var jsonData = $.ajax({
>> url: "charts/chart_handler.php?chart=chart_NAVgrowth",
>> dataType:"json",
>> success: function (jsonData) {
>> var data = new google.visualization.DataTable(jsonData);  //
>> Create our data table out of JSON data loaded from server.
>>
>> var options = {
>> 'lineWidth': 1,
>> 'legend': {position: 'top'},
>> 'backgroundColor':'#f8f8ea', // same color as background
>> box
>> 'width':850,
>> 'height':200,
>> 'hAxis': {textStyle: {fontSize:10, color:'black',
>> bold:'true'}, viewWindowMode: 'maximized', gridlines: {count:-1} },
>> 'vAxis': {textStyle: {fontSize:10, color:'black'},
>> logScale: 'true', gridlines: {count:-1} },
>> 'fontName':'Trebuchet MS'
>> };
>>
>> var chart = new
>> google.visualization.LineChart(document.getElementById('chart_NAVgrowth'));
>>  // Instantiate chart
>> chart.draw(data, options);   // draw chart, passing in some
>> options.
>> }
>> });
>> }
>>
>>
>> Any idea based on these why the current google chart version would not
>> work? We'd rather change the charts to keep current than use frozen
>> versions.  However if easy to use the frozen library, how would we change
>> the ca

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Patrick,

Mixing google.load() and google.charts.load() in the same page is bound to
cause problems.  I wouldn't recommend even trying it.

The packages property is an array, so just list all the packages you need.
 e.g. packages: ['corechart', 'gauge'].


On Wed, Aug 19, 2015 at 12:27 PM, Patrick Beaudan  wrote:

> Daniel, thanks very much for taking a look. What would be the way to call
> all at once for bar charts, bubble charts, line charts? Can I have a call
> to the frozen library and the current library on the same page (that seems
> to work but only partially)?
>
> All seems to work as before on some pages (for instance see
> http://www.beladv.com/strategySummary.php?strategy=AllWeatherUltra_BA),
> where the charts are called using the following script on the page:
>
>  https://www.google.com/jsapi";>
>
>   src="charts/portfolioAnalyzer/call_rollingQuarterly.php">
>   src="charts/portfolioAnalyzer/call_quarterlyZscore.php">
>
> etc ...
> But on some other pages I'm getting "draw()" errors and tried to
> incorporate your frozen version with only partial success like so on our
> homepage (www.beladv.com)
>
> https://www.gstatic.com/charts/loader.js";>   
> https://www.google.com/jsapi";>
>   
> 
> 
>  src="charts/homePage/call_subAssetAlloc.php">
>  src="charts/homePage/call_NAVgrowth.php">
>  src="charts/homePage/call_riskReturnGauge_small.php"> 
>
> To generate the charts we call individual functions for each chart, and
> each function has a call to load, for instance for the last in the list
> above the function is:
>
> google.charts.load("41", {packages:["gauge"]});
> google.charts.setOnLoadCallback(drawChart);
> // google.load("visualization", "1.0", {packages:["gauge"]});
> // google.setOnLoadCallback(drawChart);
>
> function drawChart() {
> $.ajax({
> url: "charts/chart_handler.php?chart=risk_return_gauge",
> dataType:"json",
> success: function (jsonData) {
>//var data = new
> google.visualization.arrayToDataTable(jsonData);   // Create our data
> table out of JSON data loaded from server.
>var data = new google.visualization.DataTable(jsonData);   //
> Create our data table out of JSON data loaded from server.
> var options = {
> width: 150, height: 150,
> yellowFrom: 75, yellowTo: 100,
> greenFrom: 25, greenTo: 75,
> minorTicks: 5
> };
>
> var chart = new
> google.visualization.Gauge(document.getElementById('chart_riskReturnGauge_small'));
> chart.draw(data, options);
> }
> });
> }
>
> while for the chart above that (call_NAVgrowth) the function (which still
> works) is:
>
> google.load('visualization', '1.0', {'packages':['corechart']}); //
> Load the Visualization API and the piechart package.
> google.setOnLoadCallback(drawChart); // Set a callback to run when
> the Google Visualization API is loaded.
>
> // Callback that creates and populates a data table, instantiates the
> chart, passes in the data and draws it.
> function drawChart() {
> var jsonData = $.ajax({
> url: "charts/chart_handler.php?chart=chart_NAVgrowth",
> dataType:"json",
> success: function (jsonData) {
> var data = new google.visualization.DataTable(jsonData);  //
> Create our data table out of JSON data loaded from server.
>
> var options = {
> 'lineWidth': 1,
> 'legend': {position: 'top'},
> 'backgroundColor':'#f8f8ea', // same color as background
> box
> 'width':850,
> 'height':200,
> 'hAxis': {textStyle: {fontSize:10, color:'black',
> bold:'true'}, viewWindowMode: 'maximized', gridlines: {count:-1} },
> 'vAxis': {textStyle: {fontSize:10, color:'black'},
> logScale: 'true', gridlines: {count:-1} },
> 'fontName':'Trebuchet MS'
> };
>
> var chart = new
> google.visualization.LineChart(document.getElementById('chart_NAVgrowth'));
>  // Instantiate chart
> chart.draw(data, options);   // draw chart, passing in some
> options.
> }
> });
> }
>
>
> Any idea based on these why the current google chart version would not
> work? We'd rather change the charts to keep current than use frozen
> versions.  However if easy to use the frozen library, how would we change
> the call to load corechart, Gauges etc all at once?
>
> Finally in your chart library, the calls to data tables seem to all be
> something like
> var data = new google.visualization.arrayToDataTable(jsonData);
>
>
> while they used to be simply
> var data = new google.visualization.DataTable(jsonData);
>
> Any reason to use .arrayToDataTable versus .DataTable  in these examples?
>
> Thanks very much for your help!
>
>
>
>
>
> On Wed, Aug 19, 2015 at 8:55 AM, 'Daniel LaLiberte' via Google
> Visualization API  wrote:
>
>> Patrick,
>>

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Patrick Beaudan]

Daniel, thanks very much for taking a look. What would be the way to call
all at once for bar charts, bubble charts, line charts? Can I have a call
to the frozen library and the current library on the same page (that seems
to work but only partially)?

All seems to work as before on some pages (for instance see
http://www.beladv.com/strategySummary.php?strategy=AllWeatherUltra_BA),
where the charts are called using the following script on the page:

 https://www.google.com/jsapi";>

 
 

etc ...
But on some other pages I'm getting "draw()" errors and tried to
incorporate your frozen version with only partial success like so on our
homepage (www.beladv.com)

https://www.gstatic.com/charts/loader.js";>
  
https://www.google.com/jsapi";>
  




 

To generate the charts we call individual functions for each chart, and
each function has a call to load, for instance for the last in the list
above the function is:

google.charts.load("41", {packages:["gauge"]});
google.charts.setOnLoadCallback(drawChart);
// google.load("visualization", "1.0", {packages:["gauge"]});
// google.setOnLoadCallback(drawChart);

function drawChart() {
$.ajax({
url: "charts/chart_handler.php?chart=risk_return_gauge",
dataType:"json",
success: function (jsonData) {
   //var data = new
google.visualization.arrayToDataTable(jsonData);   // Create our data table
out of JSON data loaded from server.
   var data = new google.visualization.DataTable(jsonData);   //
Create our data table out of JSON data loaded from server.
var options = {
width: 150, height: 150,
yellowFrom: 75, yellowTo: 100,
greenFrom: 25, greenTo: 75,
minorTicks: 5
};

var chart = new
google.visualization.Gauge(document.getElementById('chart_riskReturnGauge_small'));
chart.draw(data, options);
}
});
}

while for the chart above that (call_NAVgrowth) the function (which still
works) is:

google.load('visualization', '1.0', {'packages':['corechart']}); //
Load the Visualization API and the piechart package.
google.setOnLoadCallback(drawChart); // Set a callback to run when the
Google Visualization API is loaded.

// Callback that creates and populates a data table, instantiates the
chart, passes in the data and draws it.
function drawChart() {
var jsonData = $.ajax({
url: "charts/chart_handler.php?chart=chart_NAVgrowth",
dataType:"json",
success: function (jsonData) {
var data = new google.visualization.DataTable(jsonData);  //
Create our data table out of JSON data loaded from server.

var options = {
'lineWidth': 1,
'legend': {position: 'top'},
'backgroundColor':'#f8f8ea', // same color as background box
'width':850,
'height':200,
'hAxis': {textStyle: {fontSize:10, color:'black',
bold:'true'}, viewWindowMode: 'maximized', gridlines: {count:-1} },
'vAxis': {textStyle: {fontSize:10, color:'black'},
logScale: 'true', gridlines: {count:-1} },
'fontName':'Trebuchet MS'
};

var chart = new
google.visualization.LineChart(document.getElementById('chart_NAVgrowth'));
 // Instantiate chart
chart.draw(data, options);   // draw chart, passing in some
options.
}
});
}


Any idea based on these why the current google chart version would not
work? We'd rather change the charts to keep current than use frozen
versions.  However if easy to use the frozen library, how would we change
the call to load corechart, Gauges etc all at once?

Finally in your chart library, the calls to data tables seem to all be
something like
var data = new google.visualization.arrayToDataTable(jsonData);


while they used to be simply
var data = new google.visualization.DataTable(jsonData);

Any reason to use .arrayToDataTable versus .DataTable  in these examples?

Thanks very much for your help!





On Wed, Aug 19, 2015 at 8:55 AM, 'Daniel LaLiberte' via Google
Visualization API  wrote:

> Patrick,
>
> In the JavaScript console, I see you are getting the error message:
> "Uncaught Error: google.charts.load() cannot be called more than once."
>
> As it says, the current implementation of google.charts.load() can't be
> called more than one time in a page, so you'll have to arrange that all
> packages you'll need are loaded in the one call, and then don't call it
> again.  We'll fix that in a future version, but for now, it is a limitation
> you'll have to live with.
>
> On Wed, Aug 19, 2015 at 10:44 AM, Patrick Beaudan 
> wrote:
>
>> Thanks very much Daniel. I tire that and other variations on that theme,
>> but can't make it work in one instance on our site (home page at
>> www.beladv.com should have this gauge, but it does not come up.
>>
>> Strangely I use the same function  to create

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Patrick,

In the JavaScript console, I see you are getting the error message:
"Uncaught Error: google.charts.load() cannot be called more than once."

As it says, the current implementation of google.charts.load() can't be
called more than one time in a page, so you'll have to arrange that all
packages you'll need are loaded in the one call, and then don't call it
again.  We'll fix that in a future version, but for now, it is a limitation
you'll have to live with.

On Wed, Aug 19, 2015 at 10:44 AM, Patrick Beaudan  wrote:

> Thanks very much Daniel. I tire that and other variations on that theme,
> but can't make it work in one instance on our site (home page at
> www.beladv.com should have this gauge, but it does not come up.
>
> Strangely I use the same function  to create this gauge on other pages of
> my site, and the gauge comes up fine.
>
> I have similar issues with some line charts. The same line chart functions
> work on parts of the site, but no longer work on other parts. If anyone
> else is having similar issues I'd appreciate a pointer. I'll research this
> more and post a fix when I find what the problem was.
>
>
> On Wednesday, August 19, 2015 at 4:20:51 AM UTC-7, Daniel Buttery wrote:
>>
>> This isn't tested but from what I understand you would need to modify
>> your code as below:
>>
>> On Wednesday, 19 August 2015 03:02:14 UTC+1, Patrick Beaudan wrote:
>>>
>>> Does the  *google.charts.load(**'41'**,* {packages: ['corechart']});
>>> work for all packages? It seems to not work for me for a gauge chart for
>>> instance code below:
>>>
>>> google.charts.load("41", {packages:["corechart, gauge"]}); 
>>> google.charts.setOnLoadCallback(drawChart);
>>> function drawChart() { $.ajax({ url:
>>> "charts/chart_handler.php?chart=risk_return_gauge", dataType:"json",
>>> success: function (jsonData) { var data = new
>>> google.visualization.DataTable(jsonData); // Create our data table out of
>>> JSON data loaded from server. var options = { width: 150, height: 150,
>>> yellowFrom: 75, yellowTo: 100, greenFrom: 25, greenTo: 75, minorTicks: 5 };
>>> var chart = new
>>> google.visualization.Gauge(document.getElementById('chart_riskReturnGauge_small'));
>>> chart.draw(data, options); } }); }
>>>
>>>
>>>
>>>
>>>
>>> On Tuesday, July 28, 2015 at 5:11:12 AM UTC-7, Daniel LaLiberte wrote:

 *Introducing Frozen Google Charts*

 When we push out new releases of Google Charts, some of the changes are
 big, like entirely new chart types, but other changes are small, like
 enhancements to the appearance or behavior of existing charts.

 Many Google Chart creators fine-tune the look and feel of their charts
 until it's exactly what they want. Some of those users might feel more
 comfortable knowing that their charts will never change, regardless of what
 improvements we make in the future.  For those users, we're proud to
 announce Frozen Google Charts.

 To load a frozen version, you must make some small changes in how you
 load the Google Charts packages.  For example, here is the usual way
 of loading the stable version and drawing a chart:

 >>>
 src="https://www.google.com/jsapi";>

 

google.load('visualization', '1', {packages: ['corechart']});

google.setOnLoadCallback(drawChart);

 

 You'll need to change your code to be like this (changes highlighted
 in bold):

 >>>
 src="*https://www.gstatic.com/charts/loader.js*
 <https://www.gstatic.com/charts/loader.js>">

 

*google.charts.load(**'41'**,* {packages: ['corechart']});

*google.charts.setOnLoadCallback*(drawChart);
 


 Note that when you call google.charts.load(), you should not include
 the ‘visualization’ parameter, and the version number is a string.
 Only version ‘41’ is supported at this time, which corresponds to the
 current stable release, and additional frozen versions will be
 announced as we push out each new stable release.  More details about
 using the frozen version loader will be available here
 
 .


 When you use a frozen version of Google Charts, all charts and
 features should work the same as for the stable version it was created
 from.  But there are two minor, though important, limitations with
 loading frozen versions, which we expect to resolve in the near future.

1. You can only call google.charts.load() one time.  You can
instead list all the packages that you'll need in one call, so there is
usually no need to make separate calls.
2. If you are us

[visualization-api] Re: Introducing Frozen Google Charts

[Patrick Beaudan]

Thanks very much Daniel. I tire that and other variations on that theme, 
but can't make it work in one instance on our site (home page at 
www.beladv.com should have this gauge, but it does not come up.

Strangely I use the same function  to create this gauge on other pages of 
my site, and the gauge comes up fine.

I have similar issues with some line charts. The same line chart functions 
work on parts of the site, but no longer work on other parts. If anyone 
else is having similar issues I'd appreciate a pointer. I'll research this 
more and post a fix when I find what the problem was.


On Wednesday, August 19, 2015 at 4:20:51 AM UTC-7, Daniel Buttery wrote:
>
> This isn't tested but from what I understand you would need to modify your 
> code as below:
>
> On Wednesday, 19 August 2015 03:02:14 UTC+1, Patrick Beaudan wrote:
>>
>> Does the  *google.charts.load(**'41'**,* {packages: ['corechart']}); 
>> work for all packages? It seems to not work for me for a gauge chart for 
>> instance code below: 
>>
>> google.charts.load("41", {packages:["corechart, gauge"]}); 
>> google.charts.setOnLoadCallback(drawChart); 
>> function drawChart() { $.ajax({ url: 
>> "charts/chart_handler.php?chart=risk_return_gauge", dataType:"json", 
>> success: function (jsonData) { var data = new 
>> google.visualization.DataTable(jsonData); // Create our data table out of 
>> JSON data loaded from server. var options = { width: 150, height: 150, 
>> yellowFrom: 75, yellowTo: 100, greenFrom: 25, greenTo: 75, minorTicks: 5 }; 
>> var chart = new 
>> google.visualization.Gauge(document.getElementById('chart_riskReturnGauge_small'));
>>  
>> chart.draw(data, options); } }); } 
>>
>>
>>
>>
>>
>> On Tuesday, July 28, 2015 at 5:11:12 AM UTC-7, Daniel LaLiberte wrote:
>>>
>>> *Introducing Frozen Google Charts*
>>>
>>> When we push out new releases of Google Charts, some of the changes are 
>>> big, like entirely new chart types, but other changes are small, like 
>>> enhancements to the appearance or behavior of existing charts.  
>>>
>>> Many Google Chart creators fine-tune the look and feel of their charts 
>>> until it's exactly what they want. Some of those users might feel more 
>>> comfortable knowing that their charts will never change, regardless of what 
>>> improvements we make in the future.  For those users, we're proud to 
>>> announce Frozen Google Charts.  
>>>
>>> To load a frozen version, you must make some small changes in how you 
>>> load the Google Charts packages.  For example, here is the usual way of 
>>> loading the stable version and drawing a chart:
>>>
>>> >>
>>> src="https://www.google.com/jsapi";>
>>>
>>> 
>>>
>>>google.load('visualization', '1', {packages: ['corechart']});
>>>
>>>google.setOnLoadCallback(drawChart);
>>>
>>> 
>>>
>>> You'll need to change your code to be like this (changes highlighted in 
>>> bold):
>>>
>>> >>
>>> src="*https://www.gstatic.com/charts/loader.js* 
>>> <https://www.gstatic.com/charts/loader.js>">
>>>
>>> 
>>>
>>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>>
>>>*google.charts.setOnLoadCallback*(drawChart);
>>> 
>>>
>>>
>>> Note that when you call google.charts.load(), you should not include 
>>> the ‘visualization’ parameter, and the version number is a string.  
>>> Only version ‘41’ is supported at this time, which corresponds to the 
>>> current stable release, and additional frozen versions will be 
>>> announced as we push out each new stable release.  More details about 
>>> using the frozen version loader will be available here 
>>> 
>>> .
>>>
>>>
>>> When you use a frozen version of Google Charts, all charts and features 
>>> should work the same as for the stable version it was created from.  But 
>>> there 
>>> are two minor, though important, limitations with loading frozen versions, 
>>> which we expect to resolve in the near future.
>>>
>>>1. You can only call google.charts.load() one time.  You can instead 
>>>list all the packages that you'll need in one call, so there is usually 
>>> no 
>>>need to make separate calls. 
>>>2. If you are using a ChartWrapper, you must explicitly load all the 
>>>packages you'll need rather than relying on the ChartWrapper to 
>>>automatically load them for you. 
>>>
>>> We expect that frozen versions will remain available indefinitely, 
>>> though we may retire frozen versions that have security concerns.  We will 
>>> typically not provide support for frozen versions, except to suggest 
>>> upgrading to newer versions.
>>>
>>> Even if you don't plan to use the frozen version 41, it would help us 
>>> if you could try it now with your charts and please let us know if you

[visualization-api] Re: Introducing Frozen Google Charts

[Daniel Buttery]

This isn't tested but from what I understand you would need to modify your 
code as below:

On Wednesday, 19 August 2015 03:02:14 UTC+1, Patrick Beaudan wrote:
>
> Does the  *google.charts.load(**'41'**,* {packages: ['corechart']}); work 
> for all packages? It seems to not work for me for a gauge chart for 
> instance code below: 
>
> google.charts.load("41", {packages:["corechart, gauge"]}); 
> google.charts.setOnLoadCallback(drawChart); 
> function drawChart() { $.ajax({ url: 
> "charts/chart_handler.php?chart=risk_return_gauge", dataType:"json", 
> success: function (jsonData) { var data = new 
> google.visualization.DataTable(jsonData); // Create our data table out of 
> JSON data loaded from server. var options = { width: 150, height: 150, 
> yellowFrom: 75, yellowTo: 100, greenFrom: 25, greenTo: 75, minorTicks: 5 }; 
> var chart = new 
> google.visualization.Gauge(document.getElementById('chart_riskReturnGauge_small'));
>  
> chart.draw(data, options); } }); } 
>
>
>
>
>
> On Tuesday, July 28, 2015 at 5:11:12 AM UTC-7, Daniel LaLiberte wrote:
>>
>> *Introducing Frozen Google Charts*
>>
>> When we push out new releases of Google Charts, some of the changes are 
>> big, like entirely new chart types, but other changes are small, like 
>> enhancements to the appearance or behavior of existing charts.  
>>
>> Many Google Chart creators fine-tune the look and feel of their charts 
>> until it's exactly what they want. Some of those users might feel more 
>> comfortable knowing that their charts will never change, regardless of what 
>> improvements we make in the future.  For those users, we're proud to 
>> announce Frozen Google Charts.  
>>
>> To load a frozen version, you must make some small changes in how you 
>> load the Google Charts packages.  For example, here is the usual way of 
>> loading the stable version and drawing a chart:
>>
>> >
>> src="https://www.google.com/jsapi";>
>>
>> 
>>
>>google.load('visualization', '1', {packages: ['corechart']});
>>
>>google.setOnLoadCallback(drawChart);
>>
>> 
>>
>> You'll need to change your code to be like this (changes highlighted in 
>> bold):
>>
>> >
>> src="*https://www.gstatic.com/charts/loader.js* 
>> <https://www.gstatic.com/charts/loader.js>">
>>
>> 
>>
>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>
>>*google.charts.setOnLoadCallback*(drawChart);
>> 
>>
>>
>> Note that when you call google.charts.load(), you should not include the 
>> ‘visualization’ parameter, and the version number is a string.  Only 
>> version ‘41’ is supported at this time, which corresponds to the current 
>> stable release, and additional frozen versions will be announced as we 
>> push out each new stable release.  More details about using the frozen 
>> version 
>> loader will be available here 
>> 
>> .
>>
>>
>> When you use a frozen version of Google Charts, all charts and features 
>> should work the same as for the stable version it was created from.  But 
>> there 
>> are two minor, though important, limitations with loading frozen versions, 
>> which we expect to resolve in the near future.
>>
>>1. You can only call google.charts.load() one time.  You can instead 
>>list all the packages that you'll need in one call, so there is usually 
>> no 
>>need to make separate calls. 
>>2. If you are using a ChartWrapper, you must explicitly load all the 
>>packages you'll need rather than relying on the ChartWrapper to 
>>automatically load them for you. 
>>
>> We expect that frozen versions will remain available indefinitely, though 
>> we may retire frozen versions that have security concerns.  We will 
>> typically not provide support for frozen versions, except to suggest 
>> upgrading to newer versions.
>>
>> Even if you don't plan to use the frozen version 41, it would help us if 
>> you could try it now with your charts and please let us know if you 
>> experience any problems.
>>
>> -- 
>> Daniel LaLiberte  
>>  - 978-394-1058
>> dlali...@google.com   5CC, Cambridge MA
>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/a740f3f9-c6ba-46ef-88ef-4d

[visualization-api] Re: Introducing Frozen Google Charts

[Patrick Beaudan]

Does the  *google.charts.load(**'41'**,* {packages: ['corechart']}); work 
for all packages? It seems to not work for me for a gauge chart for 
instance code below: 

google.load("visualization", "1.0", {packages:["gauge"]}); 
google.setOnLoadCallback(drawChart); function drawChart() { $.ajax({ url: 
"charts/chart_handler.php?chart=risk_return_gauge", dataType:"json", 
success: function (jsonData) { var data = new 
google.visualization.DataTable(jsonData); // Create our data table out of 
JSON data loaded from server. var options = { width: 150, height: 150, 
yellowFrom: 75, yellowTo: 100, greenFrom: 25, greenTo: 75, minorTicks: 5 }; 
var chart = new 
google.visualization.Gauge(document.getElementById('chart_riskReturnGauge_small'));
 
chart.draw(data, options); } }); } 





On Tuesday, July 28, 2015 at 5:11:12 AM UTC-7, Daniel LaLiberte wrote:
>
> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes are 
> big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way of 
> loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted in 
> bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include the 
> ‘visualization’ parameter, and the version number is a string.  Only 
> version ‘41’ is supported at this time, which corresponds to the current 
> stable release, and additional frozen versions will be announced as we 
> push out each new stable release.  More details about using the frozen 
> version 
> loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and features 
> should work the same as for the stable version it was created from.  But 
> there 
> are two minor, though important, limitations with loading frozen versions, 
> which we expect to resolve in the near future.
>
>1. You can only call google.charts.load() one time.  You can instead 
>list all the packages that you'll need in one call, so there is usually no 
>need to make separate calls. 
>2. If you are using a ChartWrapper, you must explicitly load all the 
>packages you'll need rather than relying on the ChartWrapper to 
>automatically load them for you. 
>
> We expect that frozen versions will remain available indefinitely, though 
> we may retire frozen versions that have security concerns.  We will 
> typically not provide support for frozen versions, except to suggest 
> upgrading to newer versions.
>
> Even if you don't plan to use the frozen version 41, it would help us if 
> you could try it now with your charts and please let us know if you 
> experience any problems.
>
> -- 
> Daniel LaLiberte  
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/df4bbcb9-8a43-495d-bd00-001ba35ae16e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

We just discovered a problem with the frozen version 41 involving css for a
few features, including Table charts, if you have paging, and dashboard
controls.  The styles will generally be wrong or missing entirely.

We should have a fix for this within a day.

On Tue, Aug 18, 2015 at 2:28 PM, Lokesh Setia  wrote:

> Thanks Daniel, you rock!
>
> On Tue, Aug 18, 2015 at 6:52 PM, 'Daniel LaLiberte' via Google
> Visualization API  wrote:
>
>> Thanks for your report, Lokesh.  We should have a fix for this in about
>> an hour.
>>
>> On Tue, Aug 18, 2015 at 7:43 AM, Lokesh Setia 
>> wrote:
>>
>>> Hi Daniel,
>>>
>>> I see the following error on loading frozen charts over https:
>>>
>>> Mixed Content: The page at  was loaded over HTTPS, but requested an
>>> insecure stylesheet 'http://www.gstatic.com/charts/41/css/util/util.css'.
>>> This request has been blocked; the content must be served over HTTPS.
>>>
>>> Seems like loader.js is linking to the http version of this file
>>> directly: http://www.gstatic.com/charts/41/css/util/util.css
>>>
>>> Let me know how this can be resolved.
>>>
>>> thanks,
>>> Lokesh
>>>
>>>
>>> On Tuesday, July 28, 2015 at 5:41:12 PM UTC+5:30, Daniel LaLiberte wrote:
>>>
 *Introducing Frozen Google Charts*

 When we push out new releases of Google Charts, some of the changes are
 big, like entirely new chart types, but other changes are small, like
 enhancements to the appearance or behavior of existing charts.

 Many Google Chart creators fine-tune the look and feel of their charts
 until it's exactly what they want. Some of those users might feel more
 comfortable knowing that their charts will never change, regardless of what
 improvements we make in the future.  For those users, we're proud to
 announce Frozen Google Charts.

 To load a frozen version, you must make some small changes in how you
 load the Google Charts packages.  For example, here is the usual way
 of loading the stable version and drawing a chart:

 >>>
 src="https://www.google.com/jsapi";>

 

google.load('visualization', '1', {packages: ['corechart']});

google.setOnLoadCallback(drawChart);

 

 You'll need to change your code to be like this (changes highlighted
 in bold):

 >>>
 src="*https://www.gstatic.com/charts/loader.js*
 <https://www.gstatic.com/charts/loader.js>">

 

*google.charts.load(**'41'**,* {packages: ['corechart']});

*google.charts.setOnLoadCallback*(drawChart);
 


 Note that when you call google.charts.load(), you should not include
 the ‘visualization’ parameter, and the version number is a string.
 Only version ‘41’ is supported at this time, which corresponds to the
 current stable release, and additional frozen versions will be
 announced as we push out each new stable release.  More details about
 using the frozen version loader will be available here
 
 .


 When you use a frozen version of Google Charts, all charts and
 features should work the same as for the stable version it was created
 from.  But there are two minor, though important, limitations with
 loading frozen versions, which we expect to resolve in the near future.

1. You can only call google.charts.load() one time.  You can
instead list all the packages that you'll need in one call, so there is
usually no need to make separate calls.
2. If you are using a ChartWrapper, you must explicitly load all
the packages you'll need rather than relying on the ChartWrapper to
automatically load them for you.

 We expect that frozen versions will remain available indefinitely,
 though we may retire frozen versions that have security concerns.  We will
 typically not provide support for frozen versions, except to suggest
 upgrading to newer versions.

 Even if you don't plan to use the frozen version 41, it would help us
 if you could try it now with your charts and please let us know if you
 experience any problems.

 --
 Daniel LaLiberte
   - 978-394-1058
 dlali...@google.com   5CC, Cambridge MA
 daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA

>>> --
>>> 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+unsubscr...@googlegroups.com.
>>> To post to thi

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Lokesh Setia]

Thanks Daniel, you rock!

On Tue, Aug 18, 2015 at 6:52 PM, 'Daniel LaLiberte' via Google
Visualization API  wrote:

> Thanks for your report, Lokesh.  We should have a fix for this in about an
> hour.
>
> On Tue, Aug 18, 2015 at 7:43 AM, Lokesh Setia 
> wrote:
>
>> Hi Daniel,
>>
>> I see the following error on loading frozen charts over https:
>>
>> Mixed Content: The page at  was loaded over HTTPS, but requested an
>> insecure stylesheet 'http://www.gstatic.com/charts/41/css/util/util.css'.
>> This request has been blocked; the content must be served over HTTPS.
>>
>> Seems like loader.js is linking to the http version of this file
>> directly: http://www.gstatic.com/charts/41/css/util/util.css
>>
>> Let me know how this can be resolved.
>>
>> thanks,
>> Lokesh
>>
>>
>> On Tuesday, July 28, 2015 at 5:41:12 PM UTC+5:30, Daniel LaLiberte wrote:
>>
>>> *Introducing Frozen Google Charts*
>>>
>>> When we push out new releases of Google Charts, some of the changes are
>>> big, like entirely new chart types, but other changes are small, like
>>> enhancements to the appearance or behavior of existing charts.
>>>
>>> Many Google Chart creators fine-tune the look and feel of their charts
>>> until it's exactly what they want. Some of those users might feel more
>>> comfortable knowing that their charts will never change, regardless of what
>>> improvements we make in the future.  For those users, we're proud to
>>> announce Frozen Google Charts.
>>>
>>> To load a frozen version, you must make some small changes in how you
>>> load the Google Charts packages.  For example, here is the usual way of
>>> loading the stable version and drawing a chart:
>>>
>>> >>
>>> src="https://www.google.com/jsapi";>
>>>
>>> 
>>>
>>>google.load('visualization', '1', {packages: ['corechart']});
>>>
>>>google.setOnLoadCallback(drawChart);
>>>
>>> 
>>>
>>> You'll need to change your code to be like this (changes highlighted in
>>> bold):
>>>
>>> >>
>>> src="*https://www.gstatic.com/charts/loader.js*
>>> <https://www.gstatic.com/charts/loader.js>">
>>>
>>> 
>>>
>>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>>
>>>*google.charts.setOnLoadCallback*(drawChart);
>>> 
>>>
>>>
>>> Note that when you call google.charts.load(), you should not include
>>> the ‘visualization’ parameter, and the version number is a string.
>>> Only version ‘41’ is supported at this time, which corresponds to the
>>> current stable release, and additional frozen versions will be
>>> announced as we push out each new stable release.  More details about
>>> using the frozen version loader will be available here
>>> 
>>> .
>>>
>>>
>>> When you use a frozen version of Google Charts, all charts and features
>>> should work the same as for the stable version it was created from.  But 
>>> there
>>> are two minor, though important, limitations with loading frozen versions,
>>> which we expect to resolve in the near future.
>>>
>>>1. You can only call google.charts.load() one time.  You can instead
>>>list all the packages that you'll need in one call, so there is usually 
>>> no
>>>need to make separate calls.
>>>2. If you are using a ChartWrapper, you must explicitly load all the
>>>packages you'll need rather than relying on the ChartWrapper to
>>>automatically load them for you.
>>>
>>> We expect that frozen versions will remain available indefinitely,
>>> though we may retire frozen versions that have security concerns.  We will
>>> typically not provide support for frozen versions, except to suggest
>>> upgrading to newer versions.
>>>
>>> Even if you don't plan to use the frozen version 41, it would help us
>>> if you could try it now with your charts and please let us know if you
>>> experience any problems.
>>>
>>> --
>>> Daniel LaLiberte 
>>>   - 978-394-1058
>>> dlali...@google.com   5CC, Cambridge MA
>>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To post to this group, send email to
>> google-visualization-api@googlegroups.com.
>> Visit this group at
>> http://groups.google.com/group/google-visualization-api.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-visualization-api/9a18b293-6519-4363-b8d2-bb69474f88d5%40googlegroups.com
>> 

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Jace Grantham]

Working great now. Thanks for the quick response and fix Daniel! Much 
appreciated.

Best,

Jace

On Tuesday, August 18, 2015 at 11:24:31 AM UTC-4, Daniel LaLiberte wrote:
>
> Jace,
>
> Try again. It might work for you now that I have fixed it and the cache of 
> the old version has timed out.
>
>
> On Tue, Aug 18, 2015 at 11:15 AM, Jace Grantham  > wrote:
>
>> Hey Daniel,
>>
>> Getting this error loading on https. Trying to use the static version of 
>> the DataTable.
>>
>> Mixed Content: The page at  was loaded over HTTPS, but requested an 
>> insecure script '
>> http://www.gstatic.com/charts/41/js/jsapi_compiled_datatable_module.js'. 
>> This request has been blocked; the content must be served over HTTPS.
>>
>> Thanks and best,
>> Jace
>>
>> On Tuesday, August 18, 2015 at 9:22:17 AM UTC-4, Daniel LaLiberte wrote:
>>>
>>> Thanks for your report, Lokesh.  We should have a fix for this in about 
>>> an hour.
>>>
>>> On Tue, Aug 18, 2015 at 7:43 AM, Lokesh Setia  
>>> wrote:
>>>
 Hi Daniel,

 I see the following error on loading frozen charts over https:

 Mixed Content: The page at  was loaded over HTTPS, but requested 
 an insecure stylesheet '
 http://www.gstatic.com/charts/41/css/util/util.css'. This request has 
 been blocked; the content must be served over HTTPS.

 Seems like loader.js is linking to the http version of this file 
 directly: http://www.gstatic.com/charts/41/css/util/util.css

 Let me know how this can be resolved.

 thanks,
 Lokesh


 On Tuesday, July 28, 2015 at 5:41:12 PM UTC+5:30, Daniel LaLiberte 
 wrote:

> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes 
> are big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of 
> what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way 
> of loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted 
> in bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include 
> the ‘visualization’ parameter, and the version number is a string.  
> Only version ‘41’ is supported at this time, which corresponds to the 
> current stable release, and additional frozen versions will be 
> announced as we push out each new stable release.  More details about 
> using the frozen version loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and 
> features should work the same as for the stable version it was created 
> from.  But there are two minor, though important, limitations with 
> loading frozen versions, which we expect to resolve in the near 
> future.
>
>1. You can only call google.charts.load() one time.  You can 
>instead list all the packages that you'll need in one call, so there 
> is 
>usually no need to make separate calls. 
>2. If you are using a ChartWrapper, you must explicitly load all 
>the packages you'll need rather than relying on the ChartWrapper to 
>automatically load them for you. 
>
> We expect that frozen versions will remain available indefinitely, 
> though we may retire frozen versions that have security concerns.  We 
> will 
> typically not provide support for frozen versions, except to suggest 
> upgrading to newer versions.
>
> Even if you don't plan to use the frozen version 41, it would help us 
> if you could try it now with your cha

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Jace,

Try again. It might work for you now that I have fixed it and the cache of
the old version has timed out.


On Tue, Aug 18, 2015 at 11:15 AM, Jace Grantham 
wrote:

> Hey Daniel,
>
> Getting this error loading on https. Trying to use the static version of
> the DataTable.
>
> Mixed Content: The page at  was loaded over HTTPS, but requested an
> insecure script '
> http://www.gstatic.com/charts/41/js/jsapi_compiled_datatable_module.js'.
> This request has been blocked; the content must be served over HTTPS.
>
> Thanks and best,
> Jace
>
> On Tuesday, August 18, 2015 at 9:22:17 AM UTC-4, Daniel LaLiberte wrote:
>>
>> Thanks for your report, Lokesh.  We should have a fix for this in about
>> an hour.
>>
>> On Tue, Aug 18, 2015 at 7:43 AM, Lokesh Setia 
>> wrote:
>>
>>> Hi Daniel,
>>>
>>> I see the following error on loading frozen charts over https:
>>>
>>> Mixed Content: The page at  was loaded over HTTPS, but requested an
>>> insecure stylesheet 'http://www.gstatic.com/charts/41/css/util/util.css'.
>>> This request has been blocked; the content must be served over HTTPS.
>>>
>>> Seems like loader.js is linking to the http version of this file
>>> directly: http://www.gstatic.com/charts/41/css/util/util.css
>>>
>>> Let me know how this can be resolved.
>>>
>>> thanks,
>>> Lokesh
>>>
>>>
>>> On Tuesday, July 28, 2015 at 5:41:12 PM UTC+5:30, Daniel LaLiberte wrote:
>>>
 *Introducing Frozen Google Charts*

 When we push out new releases of Google Charts, some of the changes are
 big, like entirely new chart types, but other changes are small, like
 enhancements to the appearance or behavior of existing charts.

 Many Google Chart creators fine-tune the look and feel of their charts
 until it's exactly what they want. Some of those users might feel more
 comfortable knowing that their charts will never change, regardless of what
 improvements we make in the future.  For those users, we're proud to
 announce Frozen Google Charts.

 To load a frozen version, you must make some small changes in how you
 load the Google Charts packages.  For example, here is the usual way
 of loading the stable version and drawing a chart:

 >>>
 src="https://www.google.com/jsapi";>

 

google.load('visualization', '1', {packages: ['corechart']});

google.setOnLoadCallback(drawChart);

 

 You'll need to change your code to be like this (changes highlighted
 in bold):

 >>>
 src="*https://www.gstatic.com/charts/loader.js*
 <https://www.gstatic.com/charts/loader.js>">

 

*google.charts.load(**'41'**,* {packages: ['corechart']});

*google.charts.setOnLoadCallback*(drawChart);
 


 Note that when you call google.charts.load(), you should not include
 the ‘visualization’ parameter, and the version number is a string.
 Only version ‘41’ is supported at this time, which corresponds to the
 current stable release, and additional frozen versions will be
 announced as we push out each new stable release.  More details about
 using the frozen version loader will be available here
 
 .


 When you use a frozen version of Google Charts, all charts and
 features should work the same as for the stable version it was created
 from.  But there are two minor, though important, limitations with
 loading frozen versions, which we expect to resolve in the near future.

1. You can only call google.charts.load() one time.  You can
instead list all the packages that you'll need in one call, so there is
usually no need to make separate calls.
2. If you are using a ChartWrapper, you must explicitly load all
the packages you'll need rather than relying on the ChartWrapper to
automatically load them for you.

 We expect that frozen versions will remain available indefinitely,
 though we may retire frozen versions that have security concerns.  We will
 typically not provide support for frozen versions, except to suggest
 upgrading to newer versions.

 Even if you don't plan to use the frozen version 41, it would help us
 if you could try it now with your charts and please let us know if you
 experience any problems.

 --
 Daniel LaLiberte
   - 978-394-1058
 dlali...@google.com   5CC, Cambridge MA
 daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Google Vis

Re: [visualization-api] Re: Introducing Frozen Google Charts

[Jace Grantham]

Hey Daniel,

Getting this error loading on https. Trying to use the static version of 
the DataTable.

Mixed Content: The page at  was loaded over HTTPS, but requested an 
insecure script 
'http://www.gstatic.com/charts/41/js/jsapi_compiled_datatable_module.js'. 
This request has been blocked; the content must be served over HTTPS.

Thanks and best,
Jace

On Tuesday, August 18, 2015 at 9:22:17 AM UTC-4, Daniel LaLiberte wrote:
>
> Thanks for your report, Lokesh.  We should have a fix for this in about an 
> hour.
>
> On Tue, Aug 18, 2015 at 7:43 AM, Lokesh Setia  > wrote:
>
>> Hi Daniel,
>>
>> I see the following error on loading frozen charts over https:
>>
>> Mixed Content: The page at  was loaded over HTTPS, but requested an 
>> insecure stylesheet 'http://www.gstatic.com/charts/41/css/util/util.css'. 
>> This request has been blocked; the content must be served over HTTPS.
>>
>> Seems like loader.js is linking to the http version of this file 
>> directly: http://www.gstatic.com/charts/41/css/util/util.css
>>
>> Let me know how this can be resolved.
>>
>> thanks,
>> Lokesh
>>
>>
>> On Tuesday, July 28, 2015 at 5:41:12 PM UTC+5:30, Daniel LaLiberte wrote:
>>
>>> *Introducing Frozen Google Charts*
>>>
>>> When we push out new releases of Google Charts, some of the changes are 
>>> big, like entirely new chart types, but other changes are small, like 
>>> enhancements to the appearance or behavior of existing charts.  
>>>
>>> Many Google Chart creators fine-tune the look and feel of their charts 
>>> until it's exactly what they want. Some of those users might feel more 
>>> comfortable knowing that their charts will never change, regardless of what 
>>> improvements we make in the future.  For those users, we're proud to 
>>> announce Frozen Google Charts.  
>>>
>>> To load a frozen version, you must make some small changes in how you 
>>> load the Google Charts packages.  For example, here is the usual way of 
>>> loading the stable version and drawing a chart:
>>>
>>> >>
>>> src="https://www.google.com/jsapi";>
>>>
>>> 
>>>
>>>google.load('visualization', '1', {packages: ['corechart']});
>>>
>>>google.setOnLoadCallback(drawChart);
>>>
>>> 
>>>
>>> You'll need to change your code to be like this (changes highlighted in 
>>> bold):
>>>
>>> >>
>>> src="*https://www.gstatic.com/charts/loader.js* 
>>> <https://www.gstatic.com/charts/loader.js>">
>>>
>>> 
>>>
>>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>>
>>>*google.charts.setOnLoadCallback*(drawChart);
>>> 
>>>
>>>
>>> Note that when you call google.charts.load(), you should not include 
>>> the ‘visualization’ parameter, and the version number is a string.  
>>> Only version ‘41’ is supported at this time, which corresponds to the 
>>> current stable release, and additional frozen versions will be 
>>> announced as we push out each new stable release.  More details about 
>>> using the frozen version loader will be available here 
>>> 
>>> .
>>>
>>>
>>> When you use a frozen version of Google Charts, all charts and features 
>>> should work the same as for the stable version it was created from.  But 
>>> there 
>>> are two minor, though important, limitations with loading frozen versions, 
>>> which we expect to resolve in the near future.
>>>
>>>1. You can only call google.charts.load() one time.  You can instead 
>>>list all the packages that you'll need in one call, so there is usually 
>>> no 
>>>need to make separate calls. 
>>>2. If you are using a ChartWrapper, you must explicitly load all the 
>>>packages you'll need rather than relying on the ChartWrapper to 
>>>automatically load them for you. 
>>>
>>> We expect that frozen versions will remain available indefinitely, 
>>> though we may retire frozen versions that have security concerns.  We will 
>>> typically not provide support for frozen versions, except to suggest 
>>> upgrading to newer versions.
>>>
>>> Even if you don't plan to use the frozen version 41, it would help us 
>>> if you could try it now with your charts and please let us know if you 
>>> experience any problems.
>>>
>>> -- 
>>> Daniel LaLiberte 
>>>   - 978-394-1058
>>> dlali...@google.com   5CC, Cambridge MA
>>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>>
>> -- 
>> 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+unsubscr...@googlegroups.com 
>> .
>> To post to this group, send email to google-visua...@googlegroups.com 
>> 

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Thanks for your report, Lokesh.  We should have a fix for this in about an
hour.

On Tue, Aug 18, 2015 at 7:43 AM, Lokesh Setia  wrote:

> Hi Daniel,
>
> I see the following error on loading frozen charts over https:
>
> Mixed Content: The page at  was loaded over HTTPS, but requested an
> insecure stylesheet 'http://www.gstatic.com/charts/41/css/util/util.css'.
> This request has been blocked; the content must be served over HTTPS.
>
> Seems like loader.js is linking to the http version of this file directly:
> http://www.gstatic.com/charts/41/css/util/util.css
>
> Let me know how this can be resolved.
>
> thanks,
> Lokesh
>
>
> On Tuesday, July 28, 2015 at 5:41:12 PM UTC+5:30, Daniel LaLiberte wrote:
>
>> *Introducing Frozen Google Charts*
>>
>> When we push out new releases of Google Charts, some of the changes are
>> big, like entirely new chart types, but other changes are small, like
>> enhancements to the appearance or behavior of existing charts.
>>
>> Many Google Chart creators fine-tune the look and feel of their charts
>> until it's exactly what they want. Some of those users might feel more
>> comfortable knowing that their charts will never change, regardless of what
>> improvements we make in the future.  For those users, we're proud to
>> announce Frozen Google Charts.
>>
>> To load a frozen version, you must make some small changes in how you
>> load the Google Charts packages.  For example, here is the usual way of
>> loading the stable version and drawing a chart:
>>
>> >
>> src="https://www.google.com/jsapi";>
>>
>> 
>>
>>google.load('visualization', '1', {packages: ['corechart']});
>>
>>google.setOnLoadCallback(drawChart);
>>
>> 
>>
>> You'll need to change your code to be like this (changes highlighted in
>> bold):
>>
>> >
>> src="*https://www.gstatic.com/charts/loader.js*
>> <https://www.gstatic.com/charts/loader.js>">
>>
>> 
>>
>>*google.charts.load(**'41'**,* {packages: ['corechart']});
>>
>>*google.charts.setOnLoadCallback*(drawChart);
>> 
>>
>>
>> Note that when you call google.charts.load(), you should not include the
>> ‘visualization’ parameter, and the version number is a string.  Only
>> version ‘41’ is supported at this time, which corresponds to the current
>> stable release, and additional frozen versions will be announced as we
>> push out each new stable release.  More details about using the frozen 
>> version
>> loader will be available here
>> 
>> .
>>
>>
>> When you use a frozen version of Google Charts, all charts and features
>> should work the same as for the stable version it was created from.  But 
>> there
>> are two minor, though important, limitations with loading frozen versions,
>> which we expect to resolve in the near future.
>>
>>1. You can only call google.charts.load() one time.  You can instead
>>list all the packages that you'll need in one call, so there is usually no
>>need to make separate calls.
>>2. If you are using a ChartWrapper, you must explicitly load all the
>>packages you'll need rather than relying on the ChartWrapper to
>>automatically load them for you.
>>
>> We expect that frozen versions will remain available indefinitely, though
>> we may retire frozen versions that have security concerns.  We will
>> typically not provide support for frozen versions, except to suggest
>> upgrading to newer versions.
>>
>> Even if you don't plan to use the frozen version 41, it would help us if
>> you could try it now with your charts and please let us know if you
>> experience any problems.
>>
>> --
>> Daniel LaLiberte 
>>  - 978-394-1058
>> dlali...@google.com   5CC, Cambridge MA
>> daniel.l...@gmail.com 9 Juniper Ridge Road, Acton MA
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/9a18b293-6519-4363-b8d2-bb69474f88d5%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Ca

Re: [visualization-api] Re: Introducing Frozen Google Charts

['Daniel LaLiberte' via Google Visualization API]

Changing "1" to "1.0" will only be a "fix" until we push 1.1 to 1.0 this
coming Monday.  This is what we have always done when a candidate release
becomes the next production release.

I see a couple of your messages are being held up as potential spam.  Not
sure why that would be.  I'll approve.

On Tue, Aug 18, 2015 at 8:10 AM, Daniel Buttery <
hasanyoneseenmysp...@googlemail.com> wrote:

> Hi Daniel.
>
> I've seen a number of posters both here and in GitHub experiencing issues
> this morning related to version '1' being referenced. Changing this to
> '1.0' has been a fix.
>
> However I've had both a reply to your previous thread and a new thread
> aimed at helping with this issues deleted. Could you at least please post a
> sticky regarding '1' v '1.0'? As it stands if people follow the sample code
> on the Google Charts site, they will reference v1 and have issues.
>
> Cheers,
>
> Dan
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-visualization-api@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/google-visualization-api.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-visualization-api/96c80aae-8974-4365-a03a-14af71016eb1%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Daniel LaLiberte   -
978-394-1058
dlalibe...@google.com5CC, Cambridge MA
daniel.lalibe...@gmail.com  9 Juniper Ridge
Road, Acton MA

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/CAOtcSJMNNYKQCc%3DLsY_XHTk_m3Et%3D8P_HTYGpOwQKTbAV716WQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[visualization-api] Re: Introducing Frozen Google Charts

[Daniel Buttery]

Hi Daniel.

I've seen a number of posters both here and in GitHub experiencing issues 
this morning related to version '1' being referenced. Changing this to 
'1.0' has been a fix.

However I've had both a reply to your previous thread and a new thread 
aimed at helping with this issues deleted. Could you at least please post a 
sticky regarding '1' v '1.0'? As it stands if people follow the sample code 
on the Google Charts site, they will reference v1 and have issues.

Cheers,

Dan

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/96c80aae-8974-4365-a03a-14af71016eb1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[visualization-api] Re: Introducing Frozen Google Charts

[Lokesh Setia]

Hi Daniel,

I see the following error on loading frozen charts over https:

Mixed Content: The page at  was loaded over HTTPS, but requested an 
insecure stylesheet 'http://www.gstatic.com/charts/41/css/util/util.css'. 
This request has been blocked; the content must be served over HTTPS.

Seems like loader.js is linking to the http version of this file directly: 
http://www.gstatic.com/charts/41/css/util/util.css

Let me know how this can be resolved.

thanks,
Lokesh


On Tuesday, July 28, 2015 at 5:41:12 PM UTC+5:30, Daniel LaLiberte wrote:
>
> *Introducing Frozen Google Charts*
>
> When we push out new releases of Google Charts, some of the changes are 
> big, like entirely new chart types, but other changes are small, like 
> enhancements to the appearance or behavior of existing charts.  
>
> Many Google Chart creators fine-tune the look and feel of their charts 
> until it's exactly what they want. Some of those users might feel more 
> comfortable knowing that their charts will never change, regardless of what 
> improvements we make in the future.  For those users, we're proud to 
> announce Frozen Google Charts.  
>
> To load a frozen version, you must make some small changes in how you 
> load the Google Charts packages.  For example, here is the usual way of 
> loading the stable version and drawing a chart:
>
> 
> src="https://www.google.com/jsapi";>
>
> 
>
>google.load('visualization', '1', {packages: ['corechart']});
>
>google.setOnLoadCallback(drawChart);
>
> 
>
> You'll need to change your code to be like this (changes highlighted in 
> bold):
>
> 
> src="*https://www.gstatic.com/charts/loader.js* 
> <https://www.gstatic.com/charts/loader.js>">
>
> 
>
>*google.charts.load(**'41'**,* {packages: ['corechart']});
>
>*google.charts.setOnLoadCallback*(drawChart);
> 
>
>
> Note that when you call google.charts.load(), you should not include the 
> ‘visualization’ parameter, and the version number is a string.  Only 
> version ‘41’ is supported at this time, which corresponds to the current 
> stable release, and additional frozen versions will be announced as we 
> push out each new stable release.  More details about using the frozen 
> version 
> loader will be available here 
> 
> .
>
>
> When you use a frozen version of Google Charts, all charts and features 
> should work the same as for the stable version it was created from.  But 
> there 
> are two minor, though important, limitations with loading frozen versions, 
> which we expect to resolve in the near future.
>
>1. You can only call google.charts.load() one time.  You can instead 
>list all the packages that you'll need in one call, so there is usually no 
>need to make separate calls. 
>2. If you are using a ChartWrapper, you must explicitly load all the 
>packages you'll need rather than relying on the ChartWrapper to 
>automatically load them for you. 
>
> We expect that frozen versions will remain available indefinitely, though 
> we may retire frozen versions that have security concerns.  We will 
> typically not provide support for frozen versions, except to suggest 
> upgrading to newer versions.
>
> Even if you don't plan to use the frozen version 41, it would help us if 
> you could try it now with your charts and please let us know if you 
> experience any problems.
>
> -- 
> Daniel LaLiberte  
>  - 978-394-1058
> dlali...@google.com5CC, Cambridge MA
> daniel.l...@gmail.com  9 Juniper Ridge Road, Acton MA
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-visualization-api@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-visualization-api/9a18b293-6519-4363-b8d2-bb69474f88d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.