-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Conflict with DataFrames.jl #16
Comments
So this looks like a problem between |
Thanks, that makes sense. |
FYI... I'm pretty sure there are already issues open in both packages for On Thu, Jan 7, 2016 at 3:05 PM, datafig [email protected] wrote:
|
Given the scope of this module, I suspect a large number of users would be using I suggest for the time being we resort to saving |
I would be OK with hot loading ImageMagick within the savefig function when users ask for something besides svg or html. That would prevent this happening when you load the package and only cause the printouts when saving in a different format. |
That sounds even better. And frankly the outputs in |
Very true. That's an issue with how plotly exports png data. They use html canvas to convert the svg to base64 encoded png. The problem is that the data is fixed at either 72 or 96 dpi (I think 96, but I can't remember which) As png is lossless I should be able to use the imagemagic c api to convert to a higher quality image, but I haven't figured out the right functions to call yet. |
Implemented on master |
Another issue that I am noticing is with interoperability with DataFrames. When I just execute
using PlotlyJS
everything's fine.But if execute it after importing
DataFrames
or vice-versa. The screen get's filled with the following Warning messages.The text was updated successfully, but these errors were encountered: