Le 12/12/2014 12:14, Tudor Girba a écrit :
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.
Really not much.
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:
- What kind of actions do you put in scripts?
Short, tentative, draft experiments (i.e. tentative unit tests).
- Do you rely on script files stored on the disk at all?
No.
- Where do you store your scripts (in one folder, in many folders)?
NA
- 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?
NA.
- Do you rely on the names of the scripts?
No.
- Why do you use a script file and not a class?
As soon as the code is more than a tentative draft, I move it to a class.
If I ask scripting like tasks to students, I ask them to do it in a
class, not as a set of scripts ;)
Unless you count Makefiles as scripting... In which case they happen
outside the Pharo world.
All in all, I would hate having to explain (to students or co-workers?)
intricaties of scripts files saved to disk, versionned in a different
way than the rest of the code, with different menus and code search uses.
I also very regularly erase and rebuilt my pharo repositories, so
anything not saved in a Monticello repository is lost.
Thierry
