May 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub May 16, 2016

May 16, 2016

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

1 0

[pharo-project/pharo-core] cbee24: 60006
by GitHub May 16, 2016

May 16, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: cbee242d058b3b437d58865a186ff175a111e4d1 https://github.com/pharo-project/pharo-core/commit/cbee242d058b3b437d58865a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-16 (Mon, 16 May 2016) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60005.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60006.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60005.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60006.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Tool-CriticBrowser.package/CriticBrowser.class/instance/api/defaultTitle.st M Tool-CriticBrowser.package/CriticBrowser.class/instance/api/setTitle_.st M Tool-CriticBrowser.package/CriticBrowser.class/instance/initialization/initializePresenter.st M Tool-CriticBrowser.package/CriticBrowser.class/instance/initialization/initializeWidgets.st M Tool-CriticBrowser.package/CriticBrowser.class/instance/private/applyRules.st M Tool-CriticBrowser.package/CriticBrowser.class/instance/private/reapplyAllRules.st Log Message: ----------- 60006 18230 Critic Browser window title set to nil after deselecting a rule https://pharo.fogbugz.com/f/cases/18230 http://files.pharo.org/image/60/60006.zip

1 0

call for cleaning ideas around Spec
by stepharo May 16, 2016

May 16, 2016

Hi guys this afternoon we will have a meeting with Peter and others to talk about cleaning Spec API. If you want/can join let us know else we can organise another skype. if you have ideas let us know too. Stef

8 51

Re: [Pharo-dev] Spec: Rereading Dolphin book and MVP
by Denis Kudriashov May 16, 2016

May 16, 2016

Hi. I am sure I saw model inside presenter in Spec. It was one of reason why presenter is better name. We had Model model. Now it is Presenter model. But if your wrote this there is no reference from presenter to model now? 15 Ð¼Ð°Ñ 2016 Ð³. 10:29 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "stepharo" <stepharo(a)free.fr> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: > In MVP the presenter has direct access to the Model and (of course it means that the Model API is fixed) I did not mean that Model :) I meant the relationship with View. Stef Why would that be true? You can plug the necessary behavior of how the model can be accessed, so no need to fix the Model's API. After all the actual model will vary from user the user, so the API can't be fixed. On Sat, May 14, 2016 at 8:39 PM, stepharo <stepharo(a)free.fr> wrote: > Hi > > > In MVP the presenter has direct access to the Model and (of course it > means that the Model API is fixed) but I wonder if this would not > > help us simplify Spec. > > > Model <---- presenter <----> View > > > What do you think? > > > Stef > > >

2 1

[pharo-project/pharo-core] 44051f: 60005
by GitHub May 15, 2016

May 15, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 44051f43a13b4d888974a527366b588a377ec84a https://github.com/pharo-project/pharo-core/commit/44051f43a13b4d888974a527… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-15 (Sun, 15 May 2016) Changed paths: M Refactoring-Core.package/RBNamespace.class/instance/accessing/allClassesDo_.st M Refactoring-Environment.package/RBBrowserEnvironment.class/instance/accessing-classes/allClasses.st M Refactoring-Environment.package/RBBrowserEnvironment.class/instance/accessing-classes/allMetaClasses.st M Refactoring-Environment.package/RBBrowserEnvironment.class/instance/accessing-classes/allNonMetaClasses.st M Refactoring-Environment.package/RBBrowserEnvironment.class/instance/accessing-classes/classesDo_.st M Refactoring-Environment.package/RBBrowserEnvironment.class/instance/environments/forClasses_.st M Refactoring-Environment.package/RBBrowserEnvironment.class/instance/private/allClassesDo_.st A Refactoring-Environment.package/RBBrowserEnvironment.class/instance/private/systemDictionaryClassesDo_.st M Refactoring-Environment.package/RBClassEnvironment.class/instance/accessing-classes/classesDo_.st M Refactoring-Environment.package/RBPackageEnvironment.class/instance/accessing/classesDo_.st M Refactoring-Environment.package/RBVariableEnvironment.class/instance/private/flushCachesFor_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60004.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60005.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60004.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60005.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60005 18173 fix #allClasses for RBBrowserEnvironments https://pharo.fogbugz.com/f/cases/18173 http://files.pharo.org/image/60/60005.zip

1 0

[pharo-project/pharo-core]
by GitHub May 15, 2016

May 15, 2016

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

1 0

[pharo-project/pharo-core]
by GitHub May 15, 2016

May 15, 2016

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

1 0

[pharo-project/pharo-core] f52f6b: 60004
by GitHub May 15, 2016

May 15, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f52f6b2226495c24b9c4d0e96cb55a5c7dc1d1b3 https://github.com/pharo-project/pharo-core/commit/f52f6b2226495c24b9c4d0e9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-15 (Sun, 15 May 2016) Changed paths: A Nautilus.package/ClassWidget.class/instance/private/abstractColorAdjust_.st M Nautilus.package/ClassWidget.class/instance/private/buildTabbedNameOf_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60003.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60004.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60003.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60004.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60004 17938 Show abstract classes in ClassWidget with emphasis 2 https://pharo.fogbugz.com/f/cases/17938 http://files.pharo.org/image/60/60004.zip

1 0

[ANN] Pharo 6.0 Development started
by Esteban Lorenzano May 15, 2016

May 15, 2016

Hi, So, that: We just started development of Pharo 6.0 :) And of course, now monkey fails because you guys committed fixes from Pharo 6.0 in Pharo 5.0 inbox... so if you want the check, please commit in the new inbox :) cheers! Esteban

6 7

Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5)
by Blondeau Vincent May 15, 2016

May 15, 2016

Very strange bug indeed that happens on windows machines that crashes the VM. I succeeded to reduce the problem to an evaluation of a collectionâ¦ Can someone have the same issue under Windows or Mac? To reproduce : Copy paste the contents of the attached file in the playground and print it or do it It works on pre-spur vm. BTW, there is not crash.dmp, does it works with spur? Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Marcus Denker EnvoyÃ© : vendredi 5 fÃ©vrier 2016 13:01 Ã : Pharo Development List Objet : Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5) On 05 Feb 2016, at 12:40, Marcus Denker <marcus.denker(a)inria.fr<mailto:marcus.denker@inria.fr>> wrote: I will try do integrate it nowâ¦ No, it still fails. https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/labe… The last test it executed seems to be this: running suite: Refactoring-Tests-Environment starting testcase: RBBrowserEnvironmentTest>>testAndEnvironment ... Very strange... Marcus ________________________________ Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

6 10