Hi, I have been thinking in a similar problem for Grafoscopio. In that way, we could have the same persistence among playgrounds in a similar way to Jupyter's persistence among code cells. My bet would be on using the playground bindings that you get when it is executed. In Grafoscopio's case, I'm thinking in storing a them into some kind of ordered set that is available to all notebook nodes... still these are early thoughts and I don't like that the bindings only operate when you have not defined the variable between bars... see screenshot below.
So, to add to Peter's question: - There is any way to access not only variables bindings in a playground, but all variables that are declared there, once it is executed? - How can tap into the playgrounds self-completion behavior, so it can read variable names stored in a particular place? Thanks, Offray On 07/08/17 03:16, Peter Uhnak wrote: > Hi, > > is there a way to share context/variables between multiple playgrounds? > > E.g. in Playground window 1 I declare > > ``` > factor := 70. > ``` > > and in Playground window 2 I do (without declaring `factor`) > > ``` > 5 * factor. "-> 350" > ``` > > > Thanks, > Peter > >
