2014-12-16 13:00 GMT+01:00 Sven Van Caekenberghe <sven@stfx.eu>:

> On 16 Dec 2014, at 12:54, Thierry Goubier <thierry.goubier@gmail.com> wrote:
>
>
>
> 2014-12-16 12:44 GMT+01:00 Sven Van Caekenberghe <sven@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