this is the class comment of Workspace :

 <<< A Workspace is a text area plus a lot of support for executable code.
It is a great place to execute top-level commands to compute something
useful, and it is a great place to develop bits of a program before those
bits get put into class methods.

To open a new workspace, execute:

Workspace open


A workspace can have its own variables, called "workspace variables", to
hold intermediate results.  For example, if you type into a workspace "x :=
5" and do-it, then later you could type in "y := x * 2" and y would become
10.

Additionally, in Morphic, a workspace can gain access to morphs that are on
the screen.  If acceptDroppedMorphss is turned on, then whenever a morph is
dropped on the workspace, a variable will be created which references that
morph.  This functionality is toggled with the window-wide menu of a
workspace.



The instance variables of this class are:

bindings  -  holds the workspace variables for this workspace

acceptDroppedMorphss - whether dropped morphs should create new variables
>>>


Call me blind but I dont see anywhere mentioning local/temporary variables
and how they work diffirently for wokspace compared to just regular
workspace variables. Because thats exactly what we discuss here.

"Once you get the hang of it, it is really cool and powerful."

Indeed it get better and better, and I can see why pharo coders feel less
need to rely on documentation compared to beginners like me and Nacho. The
one thing that really annoy me with pharo is what I call "the happy
Kangaroo" problem. That problem appears in some cases that one method
depends on another which depends on the other etc etc that ends up a nasty
spagettification .So trying to understand the code is like hunting down a
happy Kangaroo.  This is where class comments can be really helpful to help
you understand something that you wont get easily from reading method
source.

Actually I think this workspace comment is quite good, I have no issues
with it, it just does not answer the question of this thread which is ok. I
dont care about perfection.

Reply via email to