Pharo 4 Playground open file menu

Since the workspace is hidden (*)... what's the recommended procedure
to open a smalltalk script file (.st or .ws) without having to open
the FileBrowser?(**)

Regards,

Esteban A. Maringolo

(*) I had to run "Workspace open" in a playground.
(**) Which in fact doesn't open the file, but a workspace with its contents.

2015-04-30 16:14 GMT-03:00 Nicolai Hess <[hidden email]>:
> 2015-04-30 20:36 GMT+02:00 Esteban A. Maringolo <[hidden email]>:
>>
>> Since the workspace is hidden (*)... what's the recommended procedure
>> to open a smalltalk script file (.st or .ws) without having to open
>> the FileBrowser?(**)

> you can use inspector to open the directory.
> 'directory_with_your_st_file' asFileReference inspect.
>
> in the inspector you can navigate through the directory
> or select a file and for example for a .st file the menu offers a
> "do it and open" entry, this will execute the selected code and open
> an inspector tab on the result.

So basically there is no way to "File -> Open" from the Playground. :)
(nor a a way "File -> Save" its contents either [1])

I guess I'll keep opening a Workspace and continue the old way from there.


Regards!

Esteban A. Maringolo

[1]: IMO this is taking the "no-files based" concept to the extreme. A
step back if I could add.

Just for info: you can get back the workspace into the settings (uncheck the playground button) 

Le jeudi 30 avril 2015, Esteban A. Maringolo <[hidden email]> a écrit :

2015-04-30 16:14 GMT-03:00 Nicolai Hess <<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;nicolaihess@web.de&#39;)">nicolaihess@...>:
> 2015-04-30 20:36 GMT+02:00 Esteban A. Maringolo <<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;emaringolo@gmail.com&#39;)">emaringolo@...>:
>>
>> Since the workspace is hidden (*)... what's the recommended procedure
>> to open a smalltalk script file (.st or .ws) without having to open
>> the FileBrowser?(**)

> you can use inspector to open the directory.
> 'directory_with_your_st_file' asFileReference inspect.
>
> in the inspector you can navigate through the directory
> or select a file and for example for a .st file the menu offers a
> "do it and open" entry, this will execute the selected code and open
> an inspector tab on the result.

So basically there is no way to "File -> Open" from the Playground. :)
(nor a a way "File -> Save" its contents either [1])

I guess I'll keep opening a Workspace and continue the old way from there.


Regards!

Esteban A. Maringolo

[1]: IMO this is taking the "no-files based" concept to the extreme. A
step back if I could add.

--

2015-04-30 16:29 GMT-03:00 Cyril Ferlicot <[hidden email]>:
> Just for info: you can get back the workspace into the settings (uncheck the
> playground button)

Thanks, but that is an either-or choice.

I do love Playground, but for exploratory coding and or interactions.
If it is meant to replace the Workspace I want to preserve its basic
features (open/save at least).

Regards,

Esteban.

There is a way to have both I think but I don't have my laptop now to check 

Le jeudi 30 avril 2015, Esteban A. Maringolo <[hidden email]> a écrit :

2015-04-30 16:29 GMT-03:00 Cyril Ferlicot <<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;cyril.ferlicot@gmail.com&#39;)">cyril.ferlicot@...>:
> Just for info: you can get back the workspace into the settings (uncheck the
> playground button)

Thanks, but that is an either-or choice.

I do love Playground, but for exploratory coding and or interactions.
If it is meant to replace the Workspace I want to preserve its basic
features (open/save at least).

Regards,

Esteban.

--

Oh, I didn't knew that. Is there other features like this ? 

Le jeudi 30 avril 2015, Andrei Chis <[hidden email]> a écrit :

Depending on what you want to do playground has a way to manage external files with smalltalk scripts.

If you double click in the Page tab in the playground you will be able to rename it. If you rename it to

'customScript' and hit enter a file is created in the folder play-stash from the current image directory.

Then whatever you type in the playground is saved in that file.

If you then open spotter and search for 'customScript'  you will see the file. Select the file and hit enter 

and then a playground is opened linked again with that file.

Cheers,

Andrei

On Thu, Apr 30, 2015 at 9:49 PM, Cyril Ferlicot <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;cyril.ferlicot@gmail.com&#39;);" target="_blank">cyril.ferlicot@...> wrote:

There is a way to have both I think but I don't have my laptop now to check 

Le jeudi 30 avril 2015, Esteban A. Maringolo <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;emaringolo@gmail.com&#39;);" target="_blank">emaringolo@...> a écrit :

2015-04-30 16:29 GMT-03:00 Cyril Ferlicot <[hidden email]>:
> Just for info: you can get back the workspace into the settings (uncheck the
> playground button)

Thanks, but that is an either-or choice.

I do love Playground, but for exploratory coding and or interactions.
If it is meant to replace the Workspace I want to preserve its basic
features (open/save at least).

Regards,

Esteban.

--

Cheers

Cyril Ferlicot

--

Esteban A. Maringolo wrote

Since the workspace is hidden (*)

If you just want it for your own personal use, why not just add it back to the world menu via a startup script?

2015-04-30 19:08 GMT-03:00 Sean P. DeNigris <[hidden email]>:
> Esteban A. Maringolo wrote
>> Since the workspace is hidden (*)
>
> If you just want it for your own personal use, why not just add it back to
> the world menu via a startup script?

Truth is because I don't know how.
I could look, but I know myself, and I'll type "Workspace open" a
thousand times before doing it. There are 978 to go... :P

However now it is confirmed that this omission was "by design", I
think it was a bad decision, whatever is the rationale behind it. I'll
get used to it, but I can bet really hard that newcomers won't.

Regards!

Esteban A. Maringolo

I used to think like you (same names think alike ;) )
But Doru and Andrei convinced me that this way is better:

1) you actually have a save of everything you do in your Playground in play-cache subdirectory. You can even change the place your play-cache is, then you can share scripts between your images.
You access them with the elipsis button (super cool, I never wrote an external file again after learning this).

2) you can name your playgrounds by double clicking the “Page” tab. Then they can be found with spotter easily. Some observations here:
- would be cool if this named page appears also in the elipsis list (it doesn’t)
- as I said to Doru, the fact that you can double click and change name is not obvious and I do not thing anyone has realised they can. Adding an edit icon or something that indicates the field is editable would be cool.

please, before rejecting it and came back to older ways, give this a try… I thought as you (Doru can testify how strong I was on it) and now I’m convinced this is a lot better and GTools team has a point here :)

cheers,
Esteban

Sergio Fedi wrote

As a new user of Pharo, I can say that the use of Playground is not obvious
at all (among other tools).
...
Why there's not a Workspace?

I find this intriguing. I would think that Playground would only be confusing to longtime Smalltalkers, not new users who haven't gotten used to workspaces. Where does your workspace info come from - are you coming from another Smalltalk? Or is it because the documentation is out of date?

Sergio Fedi wrote

My previous smalltalks are Express, VisualAge and Pharo 1.2 but most of all
Dolphin

Cool! From that unique perspective, how do you think we can balance prodding users to evolve without confusing users from other Smalltalks? The theory goes that if we just put Workspace back in the world menu, we will all stay happy and safe in 1980 instead of using the revolutionary GT tools. Would an explanation in the Welcome window help? Do people actually read those? If so, what would you write there to explain the situation?

Sean P. DeNigris wrote

If so, what would you write there to explain the situation?

And maybe after that snippet we can put the link to http://www.humane-assessment.com/blog/introducing-the-gtplayground/

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