> On 12 Dec 2014, at 12:14, Tudor Girba <tudor@tudorgirba.com> wrote:
>
> Hi,
>
> As input for designing new features that better support scripting in Pharo, we would benefit from a bit more input around the role scripts play in your development life.
>
> To this end, I would like to invite you to share your scripting experience. Here are some questions to start from, but feel free to diverge:
Every image that I am working in for some time contains multiple open workspaces that I need and depend on, that I dare not close because they might contain important stuff.
> - What kind of actions do you put in scripts?
Starting points for coding, exploring, starting/stopping services, loading code, generally useful expressions, snippets of code that will evolve in something else later on.
> - Do you rely on script files stored on the disk at all?
Not really, but I tried (both using save/load and ScriptManager) - I think the extra step is too much, a permanent workspace in an image is so much easier.
> - Where do you store your scripts (in one folder, in many folders)?
Just next to the image, mostly. But I tried structured saving with ScriptManager.
> - Do you version your scripts?
No
> - Do you store them in separate files with dedicated names, or tend to put multiple snippets in one larger file?
Both
> - Do you rely on the names of the scripts?
If there are names, yes.
> - Why do you use a script file and not a class?
Some tools end up as class methods, if not real code.
But changing a class (code) is more serious than playing/experimenting/exploring code in a workspace.
===
One of the things that I do is mail snippets around internally, so that I and others have them in their mailbox for later reference.
===
We need something very low friction, like automatic saving/remembering.