New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow offline use #277
Comments
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
What is the status of this ? |
@albertolobrano As far as I know, this is a Terms of Service issue more than a technical one. Google has requested that we download the library from their servers for use. I follow some of the other support channels for this API and I haven't seen any indication that this is likely to change, though I don't work for Google so I wouldn't have inside knowledge. |
I am building an application with polymer and firebase which they support offline mode and i was hoping the charts could do the same. Let's see if someone from google will notice this thread and come back with more information. |
+1 offline use is a must. |
I am in favor of offline use of this API |
Please google. |
+1 Detracts from the user experience in apps hosted in local networks that demand authentication for internet access. |
I Download bellow links: https://www.google.com/jsapi and use them in google charts:
|
Please up the priority for this, Google Charts is brilliant but this is a major showstopper. |
https://developers.google.com/chart/interactive/faq unfortunately states:
|
I have been using Google Charts to provide visualisations for a household electrical control system. This restriction means that the users won't be able to see their system if the internet connection goes down. At the least it would be good if it was OK to maintain a long-lived cache that could be preemptively updated so that (for example) one or two accesses per month were sufficient. |
Please at least tell us if there is a possibility for offline use in the future. Later edit: Just in case anybody might be interested, I found that D3 charts libray suited my needs better and allows offline use. It also has a GWT wrapper (which was one of my requirements). |
@mihajul This issue has actually never received a reply from a Google staffer, which probably says a lot. I've seen comments in the mailing list that they would like to provide this, but under the current Terms of Service, it is prohibited. So, if you need to make a decision, assume the status quo will continue. Further evidence is that the team continues to put effort into the loader mechanism, rather than providing a static versioned endpoint, which would be preferable for offline use. |
It was necessary to work on the loader in the recent past because the
previous way of serving the code was being deprecated. The new loader also
provided a way we could offer frozen versions, rather than always forcing
updates upon all users.
We are understandably reluctant to make long term commitments to provide
something that is not yet available, whereas it is much easier to make a
long term promise about something that is already available.
Allowing offline use is a technical possibility, though we will have to
investigate the legal and security issues. By continuing to serve the API,
we also have the ability to change it as necessary, even the frozen
versions.
We have discussed the possibility of open sourcing the Google Charts code,
and I am pretty sure that has been mentioned in years past. But making it
happen is itself a large project, and weighed against all the other
priorities, it tends to fall off the table. With every decision we make
about how the code is structured and maintained, we try to move closer to
eventually open sourcing it, but it is still a long road ahead.
…On Sun, Jun 25, 2017 at 10:52 AM, Nicholas Bering ***@***.***> wrote:
@mihajul <https://github.com/mihajul> This issue has actually never
received a reply from a Google staffer, which probably says a lot. I've
seen comments in the mailing list that they would like to provide this, but
under the current Terms of Service, it is prohibited. So, if you need to
make a decision, assume the status quo will continue.
Further evidence is that the team continues to put effort into the loader
mechanism, rather than providing a static versioned endpoint, which would
be preferable for offline use.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#277 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAizDW5kBaAso-lwH3lUg0GoviiuI_q2ks5sHnQqgaJpZM4Gdn_c>
.
--
Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2>
dlaliberte@Google.com <dlaliberte@google.com> 5CC, Cambridge MA
|
+1 The dynamic loading is also a problem for use in Chrome / Firefox / Safari extensions. It's not that you can't access the dynamically loaded code, it's that reviewers are rejecting extensions that load and execute code from an external source. I just had my extension pulled from the Mozilla site because of this (and also the use of eval in Google's code). |
Original issue reported on code.google.com by
suls%suls.org@gtempaccount.com
on 2010-05-11 10:42:04The text was updated successfully, but these errors were encountered: