juliapluto / plutoplotly.jl Goto Github PK

Inspired by https://discourse.julialang.org/t/reactive-plot-in-pluto-or-jupyter/77654

PlutoPlotly could publish plot coordinates (as tuple) when clicking on a plot so that they can be bound using @bind.

Modifying existing plots from different cells and from the JS side is useful many times, especially if the plot is outputting some variable that is bound on julia using @bind.

Modifying the plot via JS does not trigger a @bind reset and so is preferable.

Main idea to do this is to add a flag to the PlutoPlot object (default to true) that enforces probably via the plot id in JS that this plot is only rendered once. This way one can pass the julia plot object to a julia function and be sure that not more than one plot exists for that specific julia object.

This issue is used to trigger TagBot; feel free to unsubscribe.

If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.

If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Plot are not correctly rendered currently inside Pluto logs:

This is caused by the IO hack that is used to keep persistence between multiple plot objects in the same cell

There is no wrapper function to save an html version of a plot object. The current workaround is as follows:

let
    open("$(homedir())/tmp/text.html"; write=true) do io
        PlotlyBase.to_html(io, p.Plot)
    end
end

As discussed last week, I think I am loading plotly as the JavaScript notebook example say one should load ES6 modules:

but the Plotly object is anyway attached to the window and can not be accessed from plotly in JS.

Tagging @fonsp as mentioned last week

Current color types from Colors.jl are going through the standard json processing but that errors when rendered inside PlutoPlots.
They should be converted to string representations during _preprocessing

I just figured out that the decision who is the x axis and who the y axis has a different behavior in
PlotlyLight and PlutoPlotly:

Further observation: transposing the zz variable zz' leads to an error in PlutoPlotly. (maybe a collect is needed).
permutedims works.

all the methods that directly modify a PlotlyBase.Plot object should be overloaded to also support the PlutoPlot object directly.
Additionally, make_subplots from PlotlyJS should also be added as seen on discourse

When backing PlutoPlotly into a custom sysimage that contains Pluto and PlutoPlotly, I get the following warning upon starting Pluto

┌ Warning: You loaded this package outside of Pluto, this is not the intended behavior and you should use either PlotlyBase or PlotlyJS directly
└ @ PlutoPlotly ~/.julia/packages/PlutoPlotly/8WjBh/src/PlutoPlotly.jl:12

Does is_inside_pluto() not work as intended in this case?

Steps to reproduce on julia 1.7.3

using Pkg
Pkg.activate(temp = true)
Pkg.develop("PrecompilePlutoCourse")
cd(joinpath(Pkg.devdir(), "PrecompilePlutoCourse", "Demo"))
Pkg.activate(".")
using Demo
Demo.create_sysimage()
Demo.start()

hey! did you consider using float32 by default for plot data? to make large plots faster 🤩

The plots resize nicely when directly rendered inside a flex div, they do not do so when wrapped around a bond with @bind or when used inside PlutoUI.ExperimentalLayout.hbox.

See #1