Thank you for the defense.  It seems, though, that all of the features
of Script Manager are available in Squeak already.  Thus while Script
Manager is surely very handy in VisualWorks, we're talking about
*Squeak* here.  Squeak's main feature is the ability to make
presentations that mix code with other media forms--isn't that better
than workspaces?

If I'm ever using a non-Squeak Smalltalk, then Script Manager is
something I would look into.  But I don't see a use for it in my
personal environment, and I don't really see a use for it for Stable
Squeak.  The only defense I can think of is that authoring tools weren't
as well developed back in 2.8 as they are in 3.0.  Even in 2.8, though,
you can do some quite good stuff....  I wrote up an introduction to
network hacking for the class I asissted with in the spring; it was
filled with lots of text and lots of example do-its, and it worked just
fine in Squeak 2.8.

Lex


Joseph Pelrine <jpelrine at acm.org> wrote:
> I must say that I found it quite amusing the way so many people just judged 
> a book (or script Manager) by its cover, without even bothering to try it 
> out, or to ask questions about it. Since I wrote it, I guess I ought to 
> tell you a bit about it.
> 
> The original ScriptManager is one of the examples published in "Mastering 
> ENVY/Developer". I put it together as a way to store a lot of code snippets 
> or workspaces that I used in my work. In the ENVY version, the individual 
> scripts are stored as user fields on an ENVY User, similar to application 
> attachments (for those of you who know what I'm talking about). This allows 
> you to access them from any workstation connected to the repository. When I 
> started working on the StableSqueak project, I whipped one up for myself in 
> Squeak. I quite honestly didn't give a d*** which Morphs I used; I had (and 
> have) more important problems to solve (in any case, the UI has been redone 
> using the StSq framework, and runs both in Morphic and MVC FWIW). The code 
> happened to be in an image I sent John and Paul, and they happened to find 
> it useful.
> 
> All the ScriptManager does is let you store code snippets (or workspaces) 
> by name in folders. You can also execute the code in the script by 
> swipe-and-doIt. You can name scripts and folders any way you like - the 
> list box just sorts them alphabetically. If the screen shot of Goran's page 
> happened to have numbers in it, well that's because John named his scripts 
> and folders with numbers and characters.
> 
> The ScriptManager has some added functionality to allow me to "tear off" a 
> script into a separate workspace, "bring in" workspaces, do the same to and 
> from files, and to dump and load a whole script dictionary to a named file. 
> You can easily have multiple script managers open on multiple script 
> dictionaries.
> 
> As I said - it's a tool I wrote because I needed it. If you like it, use 
> it. If not, don't.
> 
> All my opinions are my own - but I ain't really a Squeaker, just a lil' 
> ole' Smalltalker...
> --
>   - Joseph Pelrine [ | ]
> Daedalos Consulting
> Email:  jpelrine at acm.org
> Web:    www.daedalos.com/~j_pelrine
> 
> Smalltalk - scene and not herd!