> On 31 Aug 2017, at 17:46, Sean P. DeNigris wrote:
>
> Pavel Krivanek-3 wrote
>> In that cases I simply make them global.
>
> It seems that a variable defined with a capitalized name in an inspector is
> still local. How do you make it global? Something like: `Smalltalk globals
> at: #MyVar pu
Pavel Krivanek-3 wrote
> In that cases I simply make them global.
It seems that a variable defined with a capitalized name in an inspector is
still local. How do you make it global? Something like: `Smalltalk globals
at: #MyVar put: expression`?
-
Cheers,
Sean
--
Sent from: http://forum.wor
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
I mentioned this a while back 2, less between different playground windows, but
more when you drill down on a value in a playground and then want to use a
value on the first pane. There was some discussion about this (Denis had some
good ideas), and it seemed like a good idea but something to pu
In that cases I simply make them global.
-- Pavel
2017-08-07 10:16 GMT+02:00 Peter Uhnak :
> 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 declar
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
