You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you looked into Signals.jl for (minimal recalculation) reactivity?
I had something like Pluto.jl in mind when I wrote Signals.jl, envisioning even debugging options
where you can enter a function
and it will be displayed like a sub Pluto notebook, with all its internal calculation laid out and amendable for changes.
And one final thought regarding reactivity:
I think notebooks like Pluto.jl should have a top-level section, for type definition and import/using statements, and a code section for statements functions etc
code section changes are handled through whatever reactivity engine you use, cheap minimal and fast, but top-level changes require a reset (new module maybe ... might leak memory ?)
The text was updated successfully, but these errors were encountered:
Very impressive work!!
Have you looked into Signals.jl for (minimal recalculation) reactivity?
I had something like Pluto.jl in mind when I wrote Signals.jl, envisioning even debugging options
where you can enter a function
and it will be displayed like a sub Pluto notebook, with all its internal calculation laid out and amendable for changes.
And one final thought regarding reactivity:
I think notebooks like Pluto.jl should have a top-level section, for type definition and import/using statements, and a code section for statements functions etc
code section changes are handled through whatever reactivity engine you use, cheap minimal and fast, but top-level changes require a reset (new module maybe ... might leak memory ?)
The text was updated successfully, but these errors were encountered: