2016-08-31 18:43 GMT-03:00 Tudor Girba <[email protected]>: > Hi, > >> On Aug 31, 2016, at 11:39 PM, Esteban A. Maringolo <[email protected]> >> wrote: >> >> One use case that sometimes bites me is when I'm working in the "code" >> of the Playground (first screen), and then I start going deep with >> "Evaluate and Go", basically inspecting my objects, and then I close >> the window thinking I'm dealing with an inspector hence losing the >> code of the "workspace" in the Playground that started the inspection >> "workflow", without receiving any warning about "losing" my changes. >> I'd like an explicit "Save" in the Playground, but since I'm not >> adding it, I can't complain much. :) > > Thanks for the input. What would the Save do in this case?
It should let me decide IF and WHEN to store the code contents. Also, if you tests scripts in a workspace and evaluate them "outside" of it (e.g. from the command line) I have to copy/paste the contents back and forth from the Playground to a text editor to save/modify something that in the past I did with the Workspace. > Should the “save" save the code from the playground? Yes. > The code from the playground is actually not lost when you close the > Playground, and neither is the code you write in the Raw panes. Or is there a > different thing you have in mind? Is not lost, but sometimes I want to reset it (reload) from a previous saved state. Maybe the latest evaluation isn't what I want to recover. Also the menu isn't the best option if you have several expressions that start with the same characters and are indistinguishable from each other. I appreciate the "autosave" like feature (although I'd like to be able to disable it for security paranoid concerns), but I also like to decide when to save. But the use case I pointed wasn't about storing the contents outside of the playground but instead of getting a warning or something when closing the Playground doing inspection. Sometimes I don't want to close the playground, just want to reset everything to the original code pane as if no "Evaluate and Go" was ever ran. Regards! Esteban A. Maringolo
