I completely agree. I did the same and I never use a workspace because 
I can edit code
anywhere anyway. Even at the end I just invoke Opener install which 
call all the scripts so I can have multiple
installations processes.

> Trygve,
> in the last years, I have always used script classes instead of
> workspaces, and I believe that has considerable advantages.
> So instead of writing code into workspaces, I put them as methods
> in a class (e.g. WolfgangsScripts). I use just one script class
> with a lot of methods, but you can use more, or use method
> categories.
>
> I came to use this approach because I believe that these scripts
> are a valuable part of the source code, which should be shared as
> well.
> Also, when I was using Envy for source code management, the scripts
> always were in sync with the code, which is good.
> And, I find browing the scripts code more convenient than using
> the plain text editor. (e.g. browse senders will search your scripts,
> too)