April 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Pharo 4 Playground open file menu

by Cyril Ferlicot

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 <emaringolo(a)gmail.com> a Ã©crit : > 2015-04-30 16:29 GMT-03:00 Cyril Ferlicot <cyril.ferlicot(a)gmail.com > <javascript:;>>: > > 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

April 30, 2015

Re: [Pharo-users] Pharo 4 Playground open file menu

by Esteban A. Maringolo

2015-04-30 16:29 GMT-03:00 Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: > 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.

April 30, 2015

Re: [Pharo-users] Pharo 4 Playground open file menu

by Cyril Ferlicot

Just for info: you can get back the workspace into the settings (uncheck the playground button) Le jeudi 30 avril 2015, Esteban A. Maringolo <emaringolo(a)gmail.com> a Ã©crit : > 2015-04-30 16:14 GMT-03:00 Nicolai Hess <nicolaihess(a)web.de <javascript:;> > >: > > 2015-04-30 20:36 GMT+02:00 Esteban A. Maringolo <emaringolo(a)gmail.com > <javascript:;>>: > >> > >> 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. > > -- Cheers Cyril Ferlicot

April 30, 2015

Re: [Pharo-users] [ANN] Screencast on Versionner

by Sergio Fedi

Aha! I saw that in your screencast! Thanks, now I see how Tests = Tests + Core â

April 30, 2015

Re: [Pharo-users] Pharo 4 Playground open file menu

by Esteban A. Maringolo

2015-04-30 16:14 GMT-03:00 Nicolai Hess <nicolaihess(a)web.de>: > 2015-04-30 20:36 GMT+02:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: >> >> 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.

April 30, 2015

Re: [Pharo-users] [ANN] Screencast on Versionner

by Esteban A. Maringolo

Sergio, When you configure the Test package you add the Core as its dependency. eg: spec package: 'Core-Tests' with: [ spec requires: 'Core ]. Regards! Esteban A. Maringolo 2015-04-30 16:06 GMT-03:00 Sergio Fedi <sergio.fedi(a)gmail.com>: > Great, thanks everyone for the explanation. > > Having said that, there's still something I don't get. > > If a group is a possible configuration to load packages, then it seems that > the "reasonable" possible configurations would be: > > 1 - Core > 2 - Tests + Core (explicitly stated) > 3 - Default (Tests + Core, implicit when not specified) > > but NOT > > Tests (without the Core) > Because you wouldn't want to load the tests of a package without the Core. > > So, why would you define the Tests as a possible configuration for a > Version? > >

April 30, 2015

Re: [Pharo-users] Pharo 4 Playground open file menu

by Nicolai Hess

2015-04-30 20:36 GMT+02:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > 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. > > 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.

April 30, 2015

Re: [Pharo-users] [ANN] Screencast on Versionner

by Sergio Fedi

Great, thanks everyone for the explanation. Having said that, there's still something I don't get. If a group is a possible configuration to load packages, then it seems that the "reasonable" possible configurations would be: 1 - Core 2 - Tests + Core (explicitly stated) 3 - Default (Tests + Core, implicit when not specified) but NOT Tests (without the Core) â Because you wouldn't want to load the tests of a package without the Core. So, why would you define the Tests as a possible configuration for a Version?

April 30, 2015

Re: [Pharo-users] [ANN] Screencast on Versionner

by Stephan Eggermont

On 30/04/15 18:06, Sergio Fedi wrote: > Excellent work Esteban! > > âQuestion for the list: > > What are groups? > > What do they model? > > What problem do they solve? (or why are they useful) When managing configurations, choosing the right granularity is critical to reducing the amount of work needed. Groups allow one configuration to be used to manage multiple combinations of packages. With groups it becomes easier to manage variants. Seaside can be used with any combination of adapters, rest, jQuery, Scriptaculous, Bootstrap etc. The simplest example was shown by Esteban in the screencast: in a production environment one might want to not load the test packages, so one has groups core, test and default (=core+test). Our tools currently do not support groups well enough, as we don't register which groups are loaded in the system. Stephan

April 30, 2015

Pharo 4 Playground open file menu

by Esteban A. Maringolo

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.

April 30, 2015