- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Pharo Sprint First half 2017

by Marcus Denker

> On 10 Jan 2017, at 15:02, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 23 Dec 2016, at 15:18, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi, >> >> As this year, there will be again âPharo Sprintsâ next year. At these dates we meet (virtual or real) >> to work on boring (or complex) issues together: >> > > â¦. > >> May 26 > > This one we have to change: The 25th is a holiday here and the 26 a âpre allocated free day from the overtime that comes > from having officially a 35h work week but working 38.5 hoursâ where our office is closed. > The idea is to move it one week: Friday, June 2. Marcus

Jan. 10, 2017

Re: [Pharo-dev] [ANN] Pharo Sprint First half 2017

by Marcus Denker

> On 23 Dec 2016, at 15:18, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > As this year, there will be again âPharo Sprintsâ next year. At these dates we meet (virtual or real) > to work on boring (or complex) issues together: > â¦. > May 26 This one we have to change: The 25th is a holiday here and the 26 a âpre allocated free day from the overtime that comes from having officially a 35h work week but working 38.5 hoursâ where our office is closed. Marcus

Jan. 10, 2017

[pharo-project/pharo-core] 10ad6c: 60342

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 10ad6c88e25fff7be020b03a14786be40cc6308f https://github.com/pharo-project/pharo-core/commit/10ad6c88e25fff7be020b03a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-01-09 (Mon, 09 Jan 2017) Changed paths: M BaselineOfIDE.package/BaselineOfIDE.class/instance/baseline/baseline_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60341.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60342.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60341.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60342.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60342 19531 Latest GTTools integration broke the bootstrap https://pharo.fogbugz.com/f/cases/19531 http://files.pharo.org/image/60/60342.zip

Jan. 9, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60342 Home: https://github.com/pharo-project/pharo-core

Jan. 9, 2017

Re: [Pharo-dev] happy and bold new year

by Tudor Girba

Hi, In my opinion, Pharo provides the strongest infrastructure for understanding a system from all technologies I have seen. So, if you say that Pharo is a bit "under featured in, then I think we are not referring to the same thing :). May I ask how you are using the inspector? For example: - do you extend the inspector? - do you construct visualizations about your system in the inspector? - do you write queries about code in the inspector? Cheers, Doru > On Jan 9, 2017, at 3:42 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > > I know this path of understanding code while it is running (inspector or > debugger), but it is still a tedious path, and I feel Pharo is a bit > under featured on that specific department, therefore my question on Moose. > > Hilaire > > > > Le 09/01/2017 Ã 15:09, Tudor Girba a Ã©crit : >> That is why my advice is to not try too long to understand Pharo code statically because this is not where the power of Pharo is. You are in a much better position to understand a system when itâs running. So, the tools that I use the most are the inspector when I need to understand structural relationships or contracts between objects, and the debugger when I need to understand some algorithmic steps. Even when I look for code structure patterns, I mostly use the inspector because it allows me to query. Then you augment these tools with custom views and you get quite far. > > -- > Dr. Geo > http://drgeo.eu > > -- www.tudorgirba.com www.feenk.com "We can create beautiful models in a vacuum. But, to get them effective we have to deal with the inconvenience of reality."

Jan. 9, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60341 Home: https://github.com/pharo-project/pharo-core

Jan. 9, 2017

[pharo-project/pharo-core] ea0552: 60341

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ea05523c2866a231ada4b126bf58392f4ed0de8f https://github.com/pharo-project/pharo-core/commit/ea05523c2866a231ada4b126… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-01-09 (Mon, 09 Jan 2017) Changed paths: A Nautilus.package/AbstractNautilusUI.class/instance/button-variables/browseVariableReferences.st A Nautilus.package/AbstractNautilusUI.class/instance/button-variables/browseVariablesButtonAction.st A Nautilus.package/AbstractNautilusUI.class/instance/button-variables/browseVariablesButtonEnabled.st A Nautilus.package/AbstractNautilusUI.class/instance/button-variables/browseVariablesButtonLabel.st A Nautilus.package/AbstractNautilusUI.class/instance/button-variables/browseVariablesButtonState.st A Nautilus.package/AbstractNautilusUI.class/instance/button-variables/buildVariableMenuFor_variablesFrom_menuItemBy_.st A Nautilus.package/AbstractNautilusUI.class/instance/button-variables/variablesMenuEntry_items_in_using_.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/browseVariableReferences.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/browseVariablesButtonAction.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/browseVariablesButtonEnabled.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/browseVariablesButtonLabel.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/browseVariablesButtonState.st R Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/buildVariableMenuFor_variablesFrom_menuItemBy_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60340.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60341.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60340.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60341.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Traits.package/TBehavior.class/instance/accessing method dictionary/localMethodNamed_ifAbsent_.st A Traits.package/TBehavior.class/instance/accessing method dictionary/localMethods.st R Traits.package/TClassDescription.class/instance/filein%2Fout/localMethods.st Log Message: ----------- 60341 19521 localMethods should be moved to TBehavior where localSelectors methods are defined https://pharo.fogbugz.com/f/cases/19521 19528 Split larger variable entries in the Variables menu into submenus https://pharo.fogbugz.com/f/cases/19528 http://files.pharo.org/image/60/60341.zip

Jan. 9, 2017

Re: [Pharo-dev] happy and bold new year

by Hilaire

I know this path of understanding code while it is running (inspector or debugger), but it is still a tedious path, and I feel Pharo is a bit under featured on that specific department, therefore my question on Moose. Hilaire Le 09/01/2017 Ã 15:09, Tudor Girba a Ã©crit : > That is why my advice is to not try too long to understand Pharo code statically because this is not where the power of Pharo is. You are in a much better position to understand a system when itâs running. So, the tools that I use the most are the inspector when I need to understand structural relationships or contracts between objects, and the debugger when I need to understand some algorithmic steps. Even when I look for code structure patterns, I mostly use the inspector because it allows me to query. Then you augment these tools with custom views and you get quite far. -- Dr. Geo http://drgeo.eu

Jan. 9, 2017

Re: [Pharo-dev] [Ann] Calypso system browser

by Bernhard Pieber

No, this is not what I meant. Although it might be a useful variant once there is go back and go forward like in web browsers. For now ClySystemBrowser beDefaultBrowser does what I want. Thanks! Cheers, Bernhard > Am 09.01.2017 um 15:10 schrieb Denis Kudriashov <dionisiydk(a)gmail.com>: > > > 2017-01-09 13:02 GMT+01:00 Bernhard Pieber <bernhard(a)pieber.com>: > I just played a bit with Calypso. I love the possibility to easily show the inherited methods. I would love to stay in a Calypso browser when I use Cmd-b to browse classes referenced in method source. > > Maybe I misunderstood you. Do you want cmd-b open selected class in same browser window?

Jan. 9, 2017

Re: [Pharo-dev] [Ann] Calypso system browser

by Denis Kudriashov

2017-01-09 13:02 GMT+01:00 Bernhard Pieber <bernhard(a)pieber.com>: > I just played a bit with Calypso. I love the possibility to easily show > the inherited methods. I would love to stay in a Calypso browser when I use > Cmd-b to browse classes referenced in method source. Maybe I misunderstood you. Do you want cmd-b open selected class in same browser window?

Jan. 9, 2017