Hi, On Tue, Dec 16, 2014 at 1:41 PM, Thierry Goubier <thierry.goub...@gmail.com> wrote: > > > > 2014-12-16 13:23 GMT+01:00 Tudor Girba <tu...@tudorgirba.com>: >> >> Just a clarification: >> Playground is saving after each change, not only after a Go. To some >> extent, it is some sort of duplication with the DoIt actions, but the >> Playground saves the entire code, not just the executed one. >> > > It doesn't make the distinction between a go on a selection or on the full > code? I'd wonder about the correctness of the save, then. >
I do not understand what you mean. Playground saves all contents after each edit operation. So, you can open a Playground, type 42, close it without executing anything, and you will have a page with '42' contents. We used to have the saving triggered only on Go, but that was too brittle as sometimes you might close a Playground by mistake before executing anything. Does that make sense now? It saves the contents in a play-cache folder by default, but you can >> configure it to be in a central folder shared by multiple images. >> > > Ok. > > If we have a better log format than the changes, could all this (changes > and those scripts) be unified/integrated? > Indeed, that would be interesting. Cheers, Doru >> The idea is exactly to try to find a mechanism that is transparent and >> let's you play without worrying about save/load. We still have to refine >> the mechanism a bit though. >> >> Please also note that GTSpotter searches through past Playground pages >> which means that discovery is now easier than before. >> > > I expected that feature :) > > Thanks, > > Thierry > > >> >> Cheers, >> Doru >> >> On Tue, Dec 16, 2014 at 1:17 PM, Thierry Goubier < >> thierry.goub...@gmail.com> wrote: >>> >>> >>> >>> 2014-12-16 13:00 GMT+01:00 Sven Van Caekenberghe <s...@stfx.eu>: >>>> >>>> >>>> > On 16 Dec 2014, at 12:54, Thierry Goubier <thierry.goub...@gmail.com> >>>> wrote: >>>> > >>>> > >>>> > >>>> > 2014-12-16 12:44 GMT+01:00 Sven Van Caekenberghe <s...@stfx.eu>: >>>> > >>>> > >>>> > === >>>> > >>>> > We need something very low friction, like automatic >>>> saving/remembering. >>>> > >>>> > >>>> > Why not searching among the doit(s) stored in the changes? >>>> > >>>> > Thierry >>>> >>>> Yes, that combined with Workspace's 'Previous contents' and the new >>>> automatic saving of Playground after Go. >>>> >>> >>> Isn't the Playground saving after go a duplication of the Changes >>> recording of the associated doit? >>> >>> >>>> >>>> It just needs to become a really safe and dependable - so that you just >>>> know you can safely close a workspace/playground with an important script >>>> and always can get it back. >>>> >>> >>> I rebuilt my images regularly, so it could be nice to have that linked >>> to a repository. And yes, simple and dependable. Like in: there is no need >>> to explain how it works... Or that the how is obvious. >>> >>> Saving states of the workspaces / playground in a kind of log and doits >>> as actions on those? Visible in searches? Stored in the package cache? >>> Robust to multiple images use on it? >>> >>> Thierry >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > -- www.tudorgirba.com "Every thing has its own flow"
