Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Signals.jl #1289

Closed
TsurHerman opened this issue Jul 6, 2021 · 0 comments
Closed

Signals.jl #1289

TsurHerman opened this issue Jul 6, 2021 · 0 comments

Comments

@TsurHerman
Copy link

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 ?)

@fonsp fonsp closed this as completed Jul 6, 2021
Repository owner locked and limited conversation to collaborators Jul 6, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants