well… IMO those scripts also should be in a method. Probably under a class named: MyCoolProjectRunScripts or something like that… but in a class. If they are in a class you can: - save them with your project - version them - if you add <script> pragma, you can even execute them by clicking on it (Pharo 4).
so… even if you might have a case where you want the save/load… you actually have (what I consider) a better option. Esteban > On 02 May 2015, at 15:17, Esteban A. Maringolo <emaring...@gmail.com> wrote: > > Ditto here. > > I have cron tasks that fire a smalltak script, the startup script itself or a > small import script that doesn't belong to a class. All those are my cases > for the workspace. > > El may 2, 2015 4:38 AM, "p...@highoctane.be <mailto:p...@highoctane.be>" > <p...@highoctane.be <mailto:p...@highoctane.be>> escribió: > playground cache is actually not nice when scripts are to be part of a > project with a name etc. And I have a ton of files in it. I can't remember > which is which. > > I have scripts to do lots of cli things and I like the save as of the > workspace. > > But I have done extra key bindings for getting the ws or the playground. > > Phil > Le 2 mai 2015 06:49, "Sergio Fedi" <sergio.f...@gmail.com > <mailto:sergio.f...@gmail.com>> a écrit : > Oh! That link gives a GREAT explanation! Thanks. > > On the subject of how to show it better, I'm not a graphic designer (although > I'm working with one) > so I'll ask him for some insights on the matter. > > > For now, he pointed out some issues like lack of consistency on some > interfaces > and some other details. >
