Skip to content
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

client side export: offline mode #71

Closed
dermitdemwolftanzt opened this issue Aug 16, 2016 · 5 comments
Closed

client side export: offline mode #71

dermitdemwolftanzt opened this issue Aug 16, 2016 · 5 comments

Comments

@dermitdemwolftanzt
Copy link

Is it possible to set the client side export (offline mode) with no fall back to exporting server?
if yes, how can I do this in properly?

Thank you in advance

@thombergs
Copy link
Member

If your question is "can I set the option exporting.fallbackToExportServer using wicked-charts?" then the answer is:

Yes, with the workaround of extending the Exporting option class as described here.

@dermitdemwolftanzt
Copy link
Author

Hallo Tom,
in example you referenced there are @OverRide annotations above setters/getters. What does it mean? Do I need to overwrite the ChartOptions class as well?
The other question: how could I include offline-exporting.js properly? Is it included by default? or should
I use JavaScriptResourceRegistry class? if yes, which method? Thank you in advance.

@dermitdemwolftanzt
Copy link
Author

I have used the ExportOptions and got this set:
"exporting" : {
"enabled" : true,
"fallbackToExportServer" : false
},
unfortunately it still tries to use export.highchart.com to export charts. Do you have any solutions for this? thank you in advance.

@dermitdemwolftanzt
Copy link
Author

I'm getting this works. Need to add the offline-exporting.js by adding this in my renderHead method:
...
final JavaScriptResourceReference CHART_OFFLINE_EXPORT = new JavaScriptResourceReference(MyApplication.class, "offline-exporting.js");
response.render(JavaScriptReferenceHeaderItem.forReference(CHART_OFFLINE_EXPORT));
thank you anyway !

@thombergs
Copy link
Member

thanks for sharing the solution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants