Please allow me a little rant here... I still find disturbing the"autosave" feature without having the option to explicitly save the contents in the filesystem as I did with Workspaces. Sometimes I don't want the contents of a file/tab updated by a criteria different than when to save the image, it is: my own when I consider appropriate.
It's not I want to disable Playground by complete which I find useful when integrated with the inlined insector, but I want to keep the behavior of saving and restoring the contents under my control. Privacywise I don't like the "history" of previous contents in the Playground, the history it can be removed but it can't be disabled. I can condense the changes file, but the Playground history remains. Regards! Esteban A. Maringolo 2017-06-29 17:12 GMT-03:00 Tim Mackinnon <tim@testit.works>: > Cool - I was missing that insight. > > Tim > > Sent from my iPhone > >> On 29 Jun 2017, at 18:04, Sven Van Caekenberghe <s...@stfx.eu> wrote: >> >> One of the more hidden Playground features are named Pages. Double-click the >> page tab title and give it a name, it will then be saved automagically in >> pharo-local/play-stash (and auto saves on changes from then on). I use that >> all the time. >> >>> On 29 Jun 2017, at 16:45, Tim Mackinnon <tim@testit.works> wrote: >>> >>> Hi - I really like the playground metaphor, it really is such a nice way to >>> experiment. >>> >>> However I've noticed that unlike older versions of Smalltalk, it seems that >>> DoIt operations in playground don't end up in the .changes file anymore >>> (which I guess is a mixed blessing when you want to recover). It seems that >>> the new metaphor is that work you do is saved as a page and you can see >>> versions of your page in the upper right menu? Well sort of - as I haven't >>> quite understood when it saves or doesn't? Often I get duplicate looking >>> pages in that menu and often I make a change and want to keep it but find >>> it doesn't save and if I accidentally close my playground my changes in a >>> page are lost? >>> >>> What are the semantics of page saving? >>> >>> An example - if you do a few gofer loads of utilities and the put a >>> comment on the first line of the page (which gives it a nice title in the >>> page dropdown), sometimes that comment will be saved other times not? >>> >>> I also think it might be nice to remove page versions to help tidy things >>> up. I'm thinking of rolling my sleeves up on this idea - but wanted to >>> understand the vision firsts >>> >>> Tim >>> >>> Sent from my iPhone >>> >>> >>> Sent from my iPhone >>> >> >> > >
