# HG changeset patch
# User Claus Gittinger <cg@exept.de>
# Date 1476378996 -7200
# Node ID d6c5de9d52bf54c80d559470970444674664ae97
# Parent  1db68d37c59c7d4028260aec5b429cd4f33d85c0
#DOCUMENTATION by cg
class: Workspace
comment/format in: #documentation

diff -r 1db68d37c59c -r d6c5de9d52bf Workspace.st
--- a/Workspace.st	Thu Oct 13 11:42:31 2016 +0200
+++ b/Workspace.st	Thu Oct 13 19:16:36 2016 +0200
@@ -63,22 +63,22 @@
      to call for another compiler/interpreter  ...)
 
     Special workspace- and doIt variables:
-	workspaces can be configured to automatically define undefined variables
-	as either workspace- or doIt variables. When encountering undefined variables,
-	the parser asks for an action, which is responded with #workspace or doIt if a
-	workspace is the requestor of a doIt. Both are implemented as value holders, and
-	the parser will generate code sending value/value: instead of normal assignment.
-	Workspace variables are kept in the Workspace class and will both persist between doIts
-	and also be visible across workspaces. They are perfect for scripting (and therefore anabled
-	by default when stx is started with one of the scripting options).
-	DoIt variables are only valid during a single doIt.
-	Be aware that when you ask from the outside via workspaceVariableAt:, you'll get a valueHolder.
-	This is by purbose, as it allows for easy monitoring and tracing of changes.
+        workspaces can be configured to automatically define undefined variables
+        as either workspace- or doIt variables. When encountering undefined variables,
+        the parser asks for an action, which is responded with #workspace or doIt if a
+        workspace is the requestor of a doIt. Both are implemented as value holders, and
+        the parser will generate code sending value/value: instead of normal assignment.
+        Workspace variables are kept in the Workspace class and will both persist between doIts
+        and also be visible across workspaces. They are perfect for scripting (and therefore enabled
+        by default when stx is started with one of the scripting options).
+        DoIt variables are only valid during a single doIt.
+        Be aware that when you ask from the outside via workspaceVariableAt:, you'll get a valueHolder.
+        This is by purbose, as it allows for easy monitoring and tracing of changes.
 
     Caveat:
-	in this version, Workspace does not yet support doIt in MVC setups.
-	For now, simulate this by setting the doItAction, to notify the
-	model manually about the doIt.
+        in this version, Workspace does not yet support doIt in MVC setups.
+        For now, simulate this by setting the doItAction, to notify the
+        model manually about the doIt.
 
 
     [instance variables:]
@@ -95,20 +95,20 @@
     [styleSheet values:]
 
       codeErrorSelectionForegroundColor     fg color to highlight errors
-					    (default: selection fg)
+                                            (default: selection fg)
 
       codeErrorSelectionBackgroundColor     bg color to highlight errors
-					    (default: selection bg)
+                                            (default: selection bg)
 
     [start with:]
-	Workspace open
+        Workspace open
 
     [see also:]
-	Workspace EditTextView
-	Parser ByteCodeCompiler
+        Workspace EditTextView
+        Parser ByteCodeCompiler
 
     [author:]
-	Claus Gittinger
+        Claus Gittinger
 "
 ! !