- First eval with "@interact" creates a "interact cell"
Drag of Slider creates update of the "interact cell", here is the data for ``cell id6``
id 6 input %__sage_interact__ sage.server.notebook.interact.recompute(6) newcell 0
How can @interact be made to have as little dependence as possible on the underlining engine?
- Use an iframe (could be made into a Widget): Loads and interacts with - How to decide if we are part of a Notebook or just a single Widget? It's really about the output cell
- Should @interact be its own django app - even with separate db tables? Help decouple or not?
- keep table layout
- add spinning 'working' img.