- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

June 1, 2016

[pharo-project/pharo-core]

by GitHub

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

June 1, 2016

[pharo-project/pharo-core] 1caf97: 60053

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 1caf97d2ff45985c564d81df3daa48f59587897d https://github.com/pharo-project/pharo-core/commit/1caf97d2ff45985c564d81df… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-06-01 (Wed, 01 Jun 2016) Changed paths: R Collections-Weak.package/WeakArray.class/class/private/finalizationProcess.st R Collections-Weak.package/WeakArray.class/class/private/restartFinalizationProcess.st R Collections-Weak.package/WeakArray.class/class/system startup/startUp_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60052.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60053.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60052.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60053.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/EphemeronLayout.class/class/as yet unclassified/extending_scope_host_.st M Slot.package/ObjectLayout.class/class/accessing/layoutForType_.st A Slot.package/PointerLayout.class/instance/extending/extendEphemeron_.st A System-Finalization.package/extension/WeakArray/class/doOldFinalization.st A System-Finalization.package/extension/WeakArray/class/finalizationProcess.st A System-Finalization.package/extension/WeakArray/class/mournLoopWith_.st A System-Finalization.package/extension/WeakArray/class/primitiveFetchMourner.st A System-Finalization.package/extension/WeakArray/class/restartFinalizationProcess.st A System-Finalization.package/extension/WeakArray/class/startUp_.st A System-Support.package/SmalltalkImage.class/instance/system attributes/supportsQueueingFinalization.st A System-Support.package/SmalltalkImage.class/instance/system attributes/supportsQueueingFinalization_.st A Traits.package/TClass.class/instance/subclass creation - weak/ephemeronSubclass_instanceVariableNames_classVariableNames_package_.st A Traits.package/TClass.class/instance/subclass creation - weak/ephemeronSubclass_instanceVariableNames_classVariableNames_poolDictionaries_category_.st Log Message: ----------- 60053 17990 Spur ephemerons must be integrated https://pharo.fogbugz.com/f/cases/17990 http://files.pharo.org/image/60/60053.zip

June 1, 2016

Re: [Pharo-dev] doing stupid things (image will become unusable)

by Nicolai Hess

2015-12-14 16:30 GMT+01:00 Richard Sargent < richard.sargent(a)gemtalksystems.com>: > Nicolai Hess-3 wrote > > Object := nil > > > > you can evaluate that piece of code, but afterwards .... > > > > Opal checks for assignments to read only variables (method arguments for > > example) > > and signals an error if you try to modify those vars. > > But it does not check globals. > > > > Should all Globals (OCLiteralVariable with isGlobalVar == true) be read > > only ? > > or can we distinguish global vars and class bindings? > > I hope you will distinguish between class bindings and variable bindings > (to > classes). > > e.g. *StringClass :=String.* and *StringClass := Unicode.* should continue > to be usable. > (Assuming that classes named #String and #Unicode do exist, of course.) > > > Created a fobgubz entry: 18376 <https://pharo.fogbugz.com/f/cases/18376/Do-not-allow-assignments-to-global-…> Do not allow assignments to global vars > > > > -- > View this message in context: > http://forum.world.st/doing-stupid-things-image-will-become-unusable-tp4866… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

June 1, 2016

[pharo-project/pharo-core]

by GitHub

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

May 31, 2016

[pharo-project/pharo-core] 7be217: 60052

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 7be217b0f3f9c5939076ea20839600adfc8b94dd https://github.com/pharo-project/pharo-core/commit/7be217b0f3f9c5939076ea20… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-31 (Tue, 31 May 2016) Changed paths: M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version415_.st M Glamour-Morphic-Brick.package/GLMPhlowPharoMethodBrick.class/instance/accessing/textBrick_.st M Glamour-Tests-Core.package/GLMCompositePresentationTest.class/instance/tests/testAddRaisesAnnouncement.st M Glamour-Tests-Core.package/GLMFinderTest.class/instance/tests/testPaneAddedAnnouncement.st M Glamour-Tests-Core.package/GLMFinderTest.class/instance/tests/testPaneRemovedAnnouncement.st M Glamour-Tests-Core.package/GLMFinderTest.class/instance/tests/testPaneReplacedAnnouncement.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60051.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60052.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60051.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60052.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60052 18370 GlamourCore 4.15 https://pharo.fogbugz.com/f/cases/18370 http://files.pharo.org/image/60/60052.zip

May 31, 2016

Re: [Pharo-dev] [UFFI] Call a function where argument type is char ** (argv)

by Blondeau Vincent

TL;DR: How to pass as argument an array of Strings (char **) with Unified-FFI? Vincent De : Blondeau Vincent EnvoyÃ© : mercredi 25 mai 2016 13:58 Ã : Pharo Development List Objet : [UFFI] Call a function where argument type is char ** (argv) Hello, I have written a R bridge in Pharo and I would like to migrate it from NativeBoost to UFFI. Most of the changes are easy to do but I am stuck to a double pointer problem. I have to call the function: int Rf_initEmbeddedR(int argc, char ** argv). I know how to give the int but the char ** is a problem. It is an array of Strings. With NB, I managed to have this (working) code: "This is 32bit... too bad..." strings := OrderedCollection new. par := NativeBoost allocate: 4 * params size. params keysAndValuesDo: [ :i :each | | str | str := each asNBExternalString. strings add: str. par nbUInt32AtOffset: (i - 1) * 4 put: str value ]. self prim_initEmbeddedRargc: params size argv: par ] ensure: [ "Free the memory we allocated" par ifNotNil: [ par free ]. strings ifNotNil: [ strings do: [ :each | each free ] ] ] With a primitive call: Self nbCall: #(int Rf_initEmbeddedR(int argc, char *argv)) Do I still need to create my own array of strings or FFI creates it for me? How? Thanks in advance for your answers, Vincent !!!************************************************************************************* "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.!!!"

May 31, 2016

Re: [Pharo-dev] Smalltalk ui icons vs iconNamed: vs @

by stepharo

Yes we were thinking about it too. Stef Le 30/5/16 Ã 15:47, Henrik Nergaard a Ã©crit : > What about > > Symbol >>#asIcon > > ^ Smalltalk ui icons iconNamed: self > > Then one can do: "#add asIcon" ? > > Best regards, > Henrik > > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Peter Uhnak > Sent: Monday, May 30, 2016 4:34 PM > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: [Pharo-dev] Smalltalk ui icons vs iconNamed: vs @ > > Hi, > > My understanding is that now instead of > > Smalltalk ui icons smallConfigurationIcon > > I should do > > Smalltalk ui iconNamed: #smallConfigurationIcon > > This is however really unpractical, because it changes the operator priority, so I have to wrap it in parentheses every single time. > > Button new > icon: (... iconNamed: ...) > > How about we add '@' or another binary selector so we can avoid the parentheses? > > Peter > > >

May 31, 2016

Re: [Pharo-dev] [Moose-dev] How to run Mondrian code

by Sven Van Caekenberghe

> On 31 May 2016, at 15:19, Ben Coman <btc(a)openInWorld.com> wrote: > > [cross-post to pharo-dev] > > On Tue, May 31, 2016 at 9:03 PM, Serge Stinckwich > <serge.stinckwich(a)gmail.com> wrote: >> No this is not buggy, I'm using this version on mac os x also. >> This is still is still a beta version of MOOSE 6.0, but the stable >> version should be release in a couple of days normally. >> >> You have to download the missing file (PharoV50.sources) from here: >> http://files.pharo.org/sources/ > > If this will remain a well defined location, I wonder if instead of > *only* advising the file is missing, the user could be offered to > download it to either image or vm location ? Could improve first > impressions ? Well, one day we had a very cool option whereby the missing source file was downloaded automatically, but we had to disable it again because of unreliable networking for some people. A pity. > cheers -ben > > >> >> and put in the same place as your image. >> >> Regards, >> >> >> On Tue, May 31, 2016 at 1:38 PM, tien dh <tiendh11986(a)gmail.com> wrote: >>> Hi, >>> I've tried to used version 6.0 as you suggest, but it seems to be buggy on >>> Mac OS. >>> In fact, I've downloaded Pharo Virtual machine and the Image file and loaded >>> the image into the virtual machine, but the software shown the error >>> message: >>> >>> "Pharo cannot locate the sources file named >>> /Users/macbookpro/Downloads/PharoV50.sources. >>> >>> Please check that the file is named properly and is in the >>> same directory as this image. >>> Make sure the sources file is not an Alias." >>> >>> On Tue, May 31, 2016 at 2:34 PM, tien dh <tiendh11986(a)gmail.com> wrote: >>>> >>>> Xin chÃ o Serge, I'm from Vietnam and It's nice to see a greeting in >>>> Vietnamese :) >>>> Thanks for your quick reply. >>>> I'm using version 5.1 on Mac OS. Yep, I've imported a model, and I open >>>> script windows via "All model classes" > Browse > In Roassal Easel. >>>> When I copy your new code to the script windows and click the Play button, >>>> it shows the an error: >>>> MessageNotUnderstood: GLMRoassal2Easel>>correctFrom:to:with: >>>> >>>> Am I wrong in using the tool? How can I test running of Mondrian code? >>>> >>>> On Tue, May 31, 2016 at 1:31 PM, Serge Stinckwich >>>> <serge.stinckwich(a)gmail.com> wrote: >>>>> >>>>> You should read : http://agilevisualization.com/ >>>>> >>>>> On Tue, May 31, 2016 at 12:29 PM, Serge Stinckwich >>>>> <serge.stinckwich(a)gmail.com> wrote: >>>>>> On Tue, May 31, 2016 at 12:04 PM, tien dh <tiendh11986(a)gmail.com> >>>>>> wrote: >>>>>>> Hello, I'm new to Mondiran and I'm trying to run very simple piece of >>>>>>> code: >>>>>> >>>>>> >>>>>> Xin chÃ o Tien. >>>>>> Where are you located ? >>>>>> >>>>>>> | view namespaces | >>>>>>> namespaces := MooseModel root allModels first allModelNamespaces. >>>>>>> view := MOViewRenderer new. >>>>>>> view shape rectangle >>>>>>> width: #numberOfClasses; >>>>>>> height: #numberOfMethods; >>>>>>> linearFillColor: #numberOfLinesOfCode within: namespaces. >>>>>>> view nodes: namespaces. >>>>>>> view edgesToAll: #providerNamespaces. >>>>>>> view dominanceTreeLayout. >>>>>>> view open. >>>>>>> >>>>>>> >>>>>>> I tried with Roassal Easel but it doesn't compile. Where should I put >>>>>>> the >>>>>>> code and run? >>>>>> >>>>>> Apparently you are running an old version of Roassal. >>>>>> Try to use the last version of MOOSE 6.0: http://moosetechnology.org/ >>>>>> >>>>>> Are you sure you have imported a model with the MOOSE panel first ? >>>>>> >>>>>> The API change a little bit in MOOSE 6.0: >>>>>> >>>>>> | view namespaces | >>>>>> namespaces := MooseModel root allModels first allModelNamespaces. >>>>>> view := RTMondrian new. >>>>>> view shape rectangle >>>>>> width: #numberOfClasses; >>>>>> height: #numberOfMethods; >>>>>> linearFillColor: #numberOfLinesOfCode within: namespaces. >>>>>> view nodes: namespaces. >>>>>> view edges connectToAll: #providerNamespaces. >>>>>> view layout dominanceTree. >>>>>> view open. > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

May 31, 2016

Re: [Pharo-dev] [Moose-dev] Re: How to run Mondrian code

by Ben Coman

[cross-post to pharo-dev] On Tue, May 31, 2016 at 9:03 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > No this is not buggy, I'm using this version on mac os x also. > This is still is still a beta version of MOOSE 6.0, but the stable > version should be release in a couple of days normally. > > You have to download the missing file (PharoV50.sources) from here: > http://files.pharo.org/sources/ If this will remain a well defined location, I wonder if instead of *only* advising the file is missing, the user could be offered to download it to either image or vm location ? Could improve first impressions ? cheers -ben > > and put in the same place as your image. > > Regards, > > > On Tue, May 31, 2016 at 1:38 PM, tien dh <tiendh11986(a)gmail.com> wrote: >> Hi, >> I've tried to used version 6.0 as you suggest, but it seems to be buggy on >> Mac OS. >> In fact, I've downloaded Pharo Virtual machine and the Image file and loaded >> the image into the virtual machine, but the software shown the error >> message: >> >> "Pharo cannot locate the sources file named >> /Users/macbookpro/Downloads/PharoV50.sources. >> >> Please check that the file is named properly and is in the >> same directory as this image. >> Make sure the sources file is not an Alias." >> >> On Tue, May 31, 2016 at 2:34 PM, tien dh <tiendh11986(a)gmail.com> wrote: >>> >>> Xin chÃ o Serge, I'm from Vietnam and It's nice to see a greeting in >>> Vietnamese :) >>> Thanks for your quick reply. >>> I'm using version 5.1 on Mac OS. Yep, I've imported a model, and I open >>> script windows via "All model classes" > Browse > In Roassal Easel. >>> When I copy your new code to the script windows and click the Play button, >>> it shows the an error: >>> MessageNotUnderstood: GLMRoassal2Easel>>correctFrom:to:with: >>> >>> Am I wrong in using the tool? How can I test running of Mondrian code? >>> >>> On Tue, May 31, 2016 at 1:31 PM, Serge Stinckwich >>> <serge.stinckwich(a)gmail.com> wrote: >>>> >>>> You should read : http://agilevisualization.com/ >>>> >>>> On Tue, May 31, 2016 at 12:29 PM, Serge Stinckwich >>>> <serge.stinckwich(a)gmail.com> wrote: >>>> > On Tue, May 31, 2016 at 12:04 PM, tien dh <tiendh11986(a)gmail.com> >>>> > wrote: >>>> >> Hello, I'm new to Mondiran and I'm trying to run very simple piece of >>>> >> code: >>>> > >>>> > >>>> > Xin chÃ o Tien. >>>> > Where are you located ? >>>> > >>>> >> | view namespaces | >>>> >> namespaces := MooseModel root allModels first allModelNamespaces. >>>> >> view := MOViewRenderer new. >>>> >> view shape rectangle >>>> >> width: #numberOfClasses; >>>> >> height: #numberOfMethods; >>>> >> linearFillColor: #numberOfLinesOfCode within: namespaces. >>>> >> view nodes: namespaces. >>>> >> view edgesToAll: #providerNamespaces. >>>> >> view dominanceTreeLayout. >>>> >> view open. >>>> >> >>>> >> >>>> >> I tried with Roassal Easel but it doesn't compile. Where should I put >>>> >> the >>>> >> code and run? >>>> > >>>> > Apparently you are running an old version of Roassal. >>>> > Try to use the last version of MOOSE 6.0: http://moosetechnology.org/ >>>> > >>>> > Are you sure you have imported a model with the MOOSE panel first ? >>>> > >>>> > The API change a little bit in MOOSE 6.0: >>>> > >>>> > | view namespaces | >>>> > namespaces := MooseModel root allModels first allModelNamespaces. >>>> > view := RTMondrian new. >>>> > view shape rectangle >>>> > width: #numberOfClasses; >>>> > height: #numberOfMethods; >>>> > linearFillColor: #numberOfLinesOfCode within: namespaces. >>>> > view nodes: namespaces. >>>> > view edges connectToAll: #providerNamespaces. >>>> > view layout dominanceTree. >>>> > view open.

May 31, 2016