- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Looking for moderators and helpers for the Pharo Mooc

by stepharo

thanks you all :) Le 28/4/16 Ã 14:43, stepharo a Ã©crit : > Hi guys > > We are looking for moderators and people to help in the forum on the > mooc. > > Let me know if you want to help. > > Stef > > >

April 28, 2016

[pharo-project/pharo-core]

by GitHub

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

April 28, 2016

[pharo-project/pharo-core] 1b5d54: 50732

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 1b5d5454d81ce9bd26a7efd12bd1a7dc009f69d1 https://github.com/pharo-project/pharo-core/commit/1b5d5454d81ce9bd26a7efd1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-28 (Thu, 28 Apr 2016) Changed paths: M ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/symbolic versions/stable_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version211_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50731.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50732.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50731.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50732.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50732 18121 Hundreds of references to undeclared variables in Fuel https://pharo.fogbugz.com/f/cases/18121 http://files.pharo.org/image/50/50732.zip

April 28, 2016

[pharo-project/pharo-core]

by GitHub

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

April 28, 2016

[pharo-project/pharo-core] 52b37b: 50731

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 52b37b0df2ef8e07bd2aedb768d35b2e430577e3 https://github.com/pharo-project/pharo-core/commit/52b37b0df2ef8e07bd2aedb7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-28 (Thu, 28 Apr 2016) Changed paths: M ConfigurationOfGTDebugger.package/ConfigurationOfGTDebugger.class/instance/symbolic versions/stable_.st A ConfigurationOfGTDebugger.package/ConfigurationOfGTDebugger.class/instance/versions/version29_.st M ConfigurationOfGTEventRecorder.package/ConfigurationOfGTEventRecorder.class/instance/symbolic versions/stable_.st A ConfigurationOfGTEventRecorder.package/ConfigurationOfGTEventRecorder.class/instance/versions/version016_.st M ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/versions/version313_.st M ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/versions/version310_.st M ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/symbolic versions/stable_.st A ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version211_.st M ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/symbolic versions/stable_.st M ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/versions/version322_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version414_.st M GT-Inspector.package/GTProtoObjectVariablesBrowser.class/instance/private building/basicVariableValuePairsFor_.st M GT-Inspector.package/GTRawObjectVariablesBrowser.class/instance/private building/evaluatorIn_.st A Glamour-Core.package/GLMAction.class/instance/printing/gtDisplayOn_.st A Glamour-Core.package/GLMPresentation.class/instance/as yet unclassified/gtActionsIn_.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoCodeRenderer.class/instance/rendering/modelFor_.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoMethodRenderer.class/instance/rendering/modelFor_.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoScriptRenderer.class/instance/private/workspaceBindingsStrategy.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoScriptRenderer.class/instance/rendering/morph.st M Glamour-Morphic-Widgets.package/GLMRubricSmalltalkTextModel.class/instance/bindings/bindingOf_.st M Glamour-Rubric-Presentations.package/GLMPharoMethodPresentation.class/definition.st R Glamour-Rubric-Presentations.package/GLMPharoMethodPresentation.class/instance/accessing/highlightSmalltalkContext.st R Glamour-Rubric-Presentations.package/GLMPharoMethodPresentation.class/instance/accessing/smalltalkClass_.st M Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/definition.st A Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/instance/accessing/highlightSmalltalkContext.st A Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/instance/accessing/smalltalkClass_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50730.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50731.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50730.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50731.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50731 Moose http://files.pharo.org/image/50/50731.zip

April 28, 2016

[pharo-project/pharo-core] 9235f3: 50730

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 9235f306a2456e5a1a9bb0d196ad442edfc24340 https://github.com/pharo-project/pharo-core/commit/9235f306a2456e5a1a9bb0d1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-28 (Thu, 28 Apr 2016) Changed paths: M FileSystem-Disk.package/FilePluginPrims.class/instance/path primitives/lookupDirectory_filename_.st M Nautilus.package/ClassDefinitionAcceptor.class/instance/private/isClassDefinitionExpression_.st M Nautilus.package/ClassOrMethodDefinitionAcceptor.class/instance/protocol/acceptInstanceSide_notifying_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50729.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50730.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50729.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50730.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50730 18081 Added a comment in File primitives so the user can know what the primitive does. https://pharo.fogbugz.com/f/cases/18081 18124 can not add instance variables in nautilus class definition pane https://pharo.fogbugz.com/f/cases/18124 http://files.pharo.org/image/50/50730.zip

April 28, 2016

[pharo-project/pharo-core]

by GitHub

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

April 28, 2016

Re: [Pharo-dev] Logging API discussion

by Denis Kudriashov

2016-04-28 14:51 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > It is not the most elegant solution, but it is very malleable and good > enough for debugging purposes. If we would have instance-based filtering > for announcements, we could filter based on that without any extra effort. > Also, if we would have a composition mechanism in place, we could build > these objects with a more elegant API. > > Regarding your statement of logging domain objects, you will have to store > these objects with the additional information somewhere, and that will be a > wrapper class. I do not see the difference with the Signal. > Difference with Beacon is that users will not depends on objects from logging library. Nobody needs to subclass core components like Signal. Instead domain objects will be added to logs inside general LogEntry instances which will be hidden from user and only available inside logs. And LogEntry will allow include additional information to itself by appropriate logging API. Question is: does it better? And this is what problem I see around Beacon: Beacon proposes to design log entries as events, as subclasses of BeaconSignal. If nothing else exists it is good. We will see in logs collection of such events. But what to do with existing domain events which has no relation to logs? How to log them if we decide to do it? They can be added to log inside WrapperSignal. But then we will see in logs mix of normal events which created specially for logs and WrapperSignal's containing original application events. But both type of events belong to same application. We definitely want to see them and to work with them in same way everywhere (especially inside logs) Tudor what do you think about this problem? Maybe I misunderstood Beacon.

April 28, 2016

Re: [Pharo-dev] Looking for moderators and helpers for the Pharo Mooc

by Andrei Chis

I can help a bit if you need non French speakers. On Thu, Apr 28, 2016 at 3:15 PM, Blondeau Vincent < vincent.blondeau(a)worldline.com> wrote: > Me too. > > Vincent > > > -----Message d'origine----- > > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de > Serge > > Stinckwich > > EnvoyÃ© : jeudi 28 avril 2016 14:45 > > Ã : Pharo Development List > > Objet : Re: [Pharo-dev] Looking for moderators and helpers for the Pharo > Mooc > > > > I can help. > > > > > > On Thu, Apr 28, 2016 at 8:43 PM, stepharo <stepharo(a)free.fr> wrote: > > > Hi guys > > > > > > We are looking for moderators and people to help in the forum on the > mooc. > > > > > > Let me know if you want to help. > > > > > > Stef > > > > > > > > > > > > > > -- > > Serge Stinckwich > > UCBN & UMI UMMISCO 209 (IRD/UPMC) > > Every DSL ends up being Smalltalk > > http://www.doesnotunderstand.org/ > > > > !!!************************************************************************************* > "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.!!!" >

April 28, 2016

zeroconf will not support anymore get.pharo.org/vm

by Esteban Lorenzano

this is a legacy script they will not work anymore, since vms are not compatibleâ¦ is announced since last year we will remove itâ¦ this is the moment :) Esteban

April 28, 2016