- Pharo-dev - lists.pharo.org

[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

About Pragma keyword vs Pragma selector
by stepharo May 15, 2016

May 15, 2016

Color >> gtInspectorColorIn: composite <gtInspectorPresentationOrder: 30> composite morph title: 'Color'; display: [ BorderedMorph new color: self ] pragma := (Color >> #gtInspectorColorIn:) pragmas first pragma arguments > 30 pragma keyword > #gtInspectorPresentationOrder: I wonder why pragma returns their selector using keyword and not selector? Especially since message API uses selector. Pragma >> message "Answer the message of the receiving pragma." ^ Message selector: self keyword arguments: self arguments. Stef

2 5

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

May 15, 2016

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

1 0

[pharo-project/pharo-core] 728a7d: 60003
by GitHub May 15, 2016

May 15, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 728a7d49160272b052b923aa71a6dc1bb9682998 https://github.com/pharo-project/pharo-core/commit/728a7d49160272b052b923aa… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-15 (Sun, 15 May 2016) Changed paths: M Polymorph-Widgets.package/ThemeIcons.class/instance/accessing/iconNamed_ifNone_.st M Polymorph-Widgets.package/ThemeIcons.class/instance/loading/loadIconsFromUrl.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60002.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60003.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60002.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60003.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60003 18129 ThemeIcons should store icons in an IdentityDictionarry https://pharo.fogbugz.com/f/cases/18129 http://files.pharo.org/image/60/60003.zip

1 0

[pharo-project/pharo-core] 0f6544: 60002
by GitHub May 15, 2016

May 15, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 0f65440719bf4a01991d19b392957773e4d55b5d https://github.com/pharo-project/pharo-core/commit/0f65440719bf4a01991d19b3… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-15 (Sun, 15 May 2016) Changed paths: M NECompletion.package/NECContext.class/instance/private-type-guessing/guessGlobal_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60001.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60002.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60001.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60002.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60002 18148 NEC should guess global variables https://pharo.fogbugz.com/f/cases/18148 http://files.pharo.org/image/60/60002.zip

1 0

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

May 15, 2016

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

1 0

problem with slots on proxies
by Tudor Girba May 15, 2016

May 15, 2016

Hi, I am trying to play with some proxies that inherit from ProtoObject have slots. For example, I try to do this, but I get an error: ProtoObject subclass: #BBB instanceVariableNames: 'variable' classVariableNames: '' package: 'BBB'. BBB class allSlots first read: BBB new The problem is that the slot sends messages to its parent object, such as: IndexedSlot>>read: anObject ^ anObject instVarAt: index This is a problem because a similar scenario happens also when you open a debugger on a proxy that tries to communicate with a remote image. I think that instead of sending messages to the receiver, we should make the slot work with the mirror primitives. For example, we would rewrite the read: method like: IndexedSlot>>read: anObject ^ thisContext object: anObject instVarAt: index Do you agree? Can I open an issue for this? I think this is important. Cheers, Doru -- www.tudorgirba.com www.feenk.com "If you can't say why something is relevant, it probably isn't."

3 3

Spec: Rereading Dolphin book and MVP
by stepharo May 15, 2016

May 15, 2016

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 2