- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] NetGen - OSM Roassal Demo

by Onil Goubier

Thank you for having reminded me for the license. It's MIT license. Onil. On Thu, Nov 20, 2014 at 5:00 AM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Hi - This looks good & useful. What is the license? > > > Thanks > > Paul > > > Onil Goubier wrote > > Hi all, > > > > We are pleased to announce a wireless sensor network animation demo in > > Pharo, Roassal and OpenStreetMap. > > > > https://github.com/OnilGoubier/Cirela > > > > The release contains 2 packages: > > 1. Cirela-OSM Package consists of the visualization of geographical > > information using roassal with OpenStreetMap as background. > > 2. Cirela-Netgen-Sim: this package allows the execution of a synchronous > > and concurrent Wireless Sensor Network (WSN) simulation program [1] from > > Pharo. Outputs of the simulation are then animated on a map visualizing > > the > > locations of the simulated sensors. > > > > A video of the animated wireless sensor network simulation: > > > > https://www.youtube.com/watch?v=sMB7DG-lbiU > > > > Another video showing Cirela-OSM: > > > > https://youtu.be/6zoGIsQaGUo > > > > A word about CIRELA > > > > CIRELA (Communication and Information technology for REsiLience to > > disAsters) is a non profit NGO aiming at providing open source solutions > > to > > monitor and prevent natural and environmental disasters. Currently we are > > focusing on wireless sensor network monitoring and warning systems. > > > > [1] This program is generated in Occam by NetGen, from B. Pottier et al. > > (UBO) > > > > > > Regards, > > Onil > > > > -- > > Onil Goubier > > Engineer > > CIRELA Association > > Communication and Information technology for REsiLience to disAsters and > > climate change > > 25, rue Paulhan > > 78140 VÃ©lizy-Villacoublay, France > > Ph. +33 6 67 77 49 93 > > > > > > -- > View this message in context: > http://forum.world.st/ANN-NetGen-OSM-Roassal-Demo-tp4791158p4791184.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- Onil Goubier Engineer CIRELA Association Communication and Information technology for REsiLience to disAsters and climate change 25, rue Paulhan 78140 VÃ©lizy-Villacoublay, France Ph. +33 6 67 77 49 93

Nov. 20, 2014

Re: [Pharo-dev] Link between PetitParser and Roassal and Glamour

by Tudor Girba

It's not strange. You only get this dependency if you load the gui of petit parser. If you do not need the gui, you can load the core group. Doru -- www.tudorgirba.com "Every thing has its own flow" > On 20 Nov 2014, at 15:57, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > Load PetitParser (dev version) => Roassal and Glamour loaded. > > Isnât it strange? I believe there should be less dependency. > > Noury

Nov. 20, 2014

Link between PetitParser and Roassal and Glamour

by Noury Bouraqadi

Load PetitParser (dev version) => Roassal and Glamour loaded. Isnât it strange? I believe there should be less dependency. Noury

Nov. 20, 2014

Re: [Pharo-dev] Source code formatting guidelines

by Peter Uhnak

What about feeding the code to RBConfigurableFormatter before merging so it matches the target style, and then there would be no need to worry about whitespace? Also I have yet to see someone using spaces for indentation and trailing whitespace (empty lines included) is usually trimmed (but then again people do use different styles so it might not apply). Peter -----Original Message----- From: "Jan Vrany" <jan.vrany(a)fit.cvut.cz> Sent: â11/â20/â2014 2:38 PM To: "pharo-dev(a)lists.pharo.org" <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] Source code formatting guidelines Hi guys, thanks for replies. I read books mentioned by Christophe years ago, they're worth reading indeed. But as I said, I'm more interested in 'low level' details like I mentioned: - tabs/spaces? How many spaces if spaces? - encoding of the source string - trailing newlines - trailing spaces - ... The reason is I'm now working with Jan K. on some stuff and he's using Pharo while I don't. To exchange code I read his .mcz when merging his changes and generating .mcz for him when he has to merge my stuff. However, Pharo's merge tool apparently does not do a really great job when it comes to whitespace changes so the merge is difficult and error-prone. The idea is to transform the source just before spitting out the .mcz to minimize these false-diffs when one try to merge. Best, Jan On Wed, 2014-11-19 at 15:19 +0100, Nicolai Hess wrote: > 2014-11-19 14:55 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > > > On 19 Nov 2014, at 14:47, Peter UhnÃ¡k <i.uhnak(a)gmail.com> > > wrote: > > > > how Pharo source code is formatted > > One could argue that this is equivalent to the default > > settings of Pharo formatter. > > Which is not goodâ¦ e.g. it always adds too many line breaksâ¦ > > > Marcus > > > If we can agree on source code guidelines, we should change the > default settings of the Pharo formatter accordingly. >

Nov. 20, 2014

Re: [Pharo-dev] Source code formatting guidelines

by Jan Vrany

Hi guys, thanks for replies. I read books mentioned by Christophe years ago, they're worth reading indeed. But as I said, I'm more interested in 'low level' details like I mentioned: - tabs/spaces? How many spaces if spaces? - encoding of the source string - trailing newlines - trailing spaces - ... The reason is I'm now working with Jan K. on some stuff and he's using Pharo while I don't. To exchange code I read his .mcz when merging his changes and generating .mcz for him when he has to merge my stuff. However, Pharo's merge tool apparently does not do a really great job when it comes to whitespace changes so the merge is difficult and error-prone. The idea is to transform the source just before spitting out the .mcz to minimize these false-diffs when one try to merge. Best, Jan On Wed, 2014-11-19 at 15:19 +0100, Nicolai Hess wrote: > 2014-11-19 14:55 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > > > On 19 Nov 2014, at 14:47, Peter UhnÃ¡k <i.uhnak(a)gmail.com> > > wrote: > > > > how Pharo source code is formatted > > One could argue that this is equivalent to the default > > settings of Pharo formatter. > > Which is not goodâ¦ e.g. it always adds too many line breaksâ¦ > > > Marcus > > > If we can agree on source code guidelines, we should change the > default settings of the Pharo formatter accordingly. >

Nov. 20, 2014

Re: [Pharo-dev] Message>>#arguments:

by Esteban Lorenzano

no ideaâ¦ but in a philosophical point of view, the fact that you have an accessor doesnât means that you should have a mutator ;) Esteban > On 20 Nov 2014, at 13:51, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > Hi, > > > Is there any reason why we donât have this method > > Message>>#arguments: anArray > args := anArray > > We already have the read accessor. There is also a write accessor for single argument messages. > > Any hint? > > Noury

Nov. 20, 2014

Message>>#arguments:

by Noury Bouraqadi

Hi, Is there any reason why we donât have this method Message>>#arguments: anArray args := anArray We already have the read accessor. There is also a write accessor for single argument messages. Any hint? Noury

Nov. 20, 2014

Re: [Pharo-dev] [Vm-dev] Re: How to check whether the handle is always valid with NativeBoost ?

by Blondeau Vincent

De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Blondeau Vincent EnvoyÃ© : lundi 17 novembre 2014 16:41 Ã : Pharo Development List Cc : Squeak Virtual Machine Development Discussion Objet : Re: [Pharo-dev] [Vm-dev] Re: How to check whether the handle is always valid with NativeBoost ? Hi Thanks a lot for your answers ! It is very helpful. But how can I launch a script at the startup or shutdown of the image especially for Pharo ? Implement in the class side : >>initialize >> Smalltalk addToStartUpList: self. And >>startUp âsome codeâ >>shutDown âsome codeâ Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Igor Stasenko EnvoyÃ© : jeudi 13 novembre 2014 23:40 Ã : Squeak Virtual Machine Development Discussion Cc : Pharo Development List Objet : Re: [Pharo-dev] [Vm-dev] Re: How to check whether the handle is always valid with NativeBoost ? On 13 November 2014 18:37, Eliot Miranda <eliot.miranda(a)gmail.com<mailto:eliot.miranda@gmail.com>> wrote: Hi Vincent, one way, used in VisualWorks, is to ensure that only valid handles exist. So very early at startup the system does some allInstances invocations on the classes of handles and invalidates all the handles found. This doesn't fix handles stored as raw integers anywhere, but provided the system is designed to have specific objects for external handles (and I hope it is) this shouldn't happen. Since snapshot is relatively rare and start-up relatively frequent (at least in e.g. a web deployment context), one performance improvement is to do the allInstances before snapshot, and then merely enumerate the collection of handles, rather than use allInstances. Just to add: - (re)validating external resources could vary depending on library or how short/long-lived the resource is etc. As you described, one of the scenarios is to flush invalid handles at system startup. In NB i using session checking, to do it lazily, once there's an attempt to use external resource. But all that, of course, doesn't addresses the problem when external resource get invalidated, for one or another reason, during same session. Using proxy to control each and every access to external resource is, of course, an ultimate solution, but alas, quite expensive since imposes high overhead. I would call it a brute-force solution. To minimize overhead, my approach often is to place a check at key entry part of algorithm, so if check passed, then rest of algorithm can run safely without excessive checking. But that really depends on design of external library/framework, whether it possible or not. Usually, if you cleverly organize the access to services, it is possible to do it without using brute-force proxyfying. On Thu, Nov 13, 2014 at 9:05 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: Hi ! I am doing a binding to the R library with NativeBoost. So I create some external objects and apply some functions on them. If the handle to the object is not valid, either the function crashes or gives a bad result. How can I ensure to have a valid pointer at anytime ? I see two solutions: - Either check at any NativeBoost call that the handle is valid (by checking the session id) - Or do a proxy that checks the session and recreate the external object. What do you think ? Thanks in advance, Cheers, Vincent BLONDEAU ________________________________ 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. -- best, Eliot -- Best regards, Igor Stasenko. ________________________________ 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. ________________________________ 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.

Nov. 20, 2014

Re: [Pharo-dev] [ANN] NetGen - OSM Roassal Demo

by Alexandre Bergel

I watched the video, this is an excellent work! Thanks Onil and Thierry! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Nov 19, 2014, at 6:40 PM, Onil Goubier <Onil.Goubier(a)gmail.com> wrote: > > > Hi all, > > We are pleased to announce a wireless sensor network animation demo in Pharo, Roassal and OpenStreetMap. > > https://github.com/OnilGoubier/Cirela <https://github.com/OnilGoubier/Cirela> > > The release contains 2 packages: > 1. Cirela-OSM Package consists of the visualization of geographical information using roassal with OpenStreetMap as background. > 2. Cirela-Netgen-Sim: this package allows the execution of a synchronous and concurrent Wireless Sensor Network (WSN) simulation program [1] from Pharo. Outputs of the simulation are then animated on a map visualizing the locations of the simulated sensors. > > A video of the animated wireless sensor network simulation: > > https://www.youtube.com/watch?v=sMB7DG-lbiU <https://www.youtube.com/watch?v=sMB7DG-lbiU> > > Another video showing Cirela-OSM: > > https://youtu.be/6zoGIsQaGUo <https://youtu.be/6zoGIsQaGUo> > > A word about CIRELA > > CIRELA (Communication and Information technology for REsiLience to disAsters) is a non profit NGO aiming at providing open source solutions to monitor and prevent natural and environmental disasters. Currently we are focusing on wireless sensor network monitoring and warning systems. > > [1] This program is generated in Occam by NetGen, from B. Pottier et al. (UBO) > > > Regards, > Onil > > -- > Onil Goubier > Engineer > CIRELA Association > Communication and Information technology for REsiLience to disAsters and climate change > 25, rue Paulhan > 78140 VÃ©lizy-Villacoublay, France > Ph. +33 6 67 77 49 93

Nov. 20, 2014

[pharo-project/pharo-core] 4dc141: 40377

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 4dc1418ad60b5f5298f7b6835de28e46c40f0361 https://github.com/pharo-project/pharo-core/commit/4dc1418ad60b5f5298f7b683… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-20 (Thu, 20 Nov 2014) Changed paths: R MonticelloGUI.package/MCTool.class/class/window color/patchworkUIThemeColor.st R MonticelloGUI.package/MCTool.class/instance/morphic ui/patchworkUIThemeColor.st R Morphic-Base.package/EventHandler.class/README.md R Morphic-Base.package/EventHandler.class/definition.st R Morphic-Base.package/EventHandler.class/instance/access/allRecipients.st R Morphic-Base.package/EventHandler.class/instance/access/firstMouseSelector.st R Morphic-Base.package/EventHandler.class/instance/access/messageList.st R Morphic-Base.package/EventHandler.class/instance/access/methodRefList.st R Morphic-Base.package/EventHandler.class/instance/access/mouseDownSelector.st R Morphic-Base.package/EventHandler.class/instance/access/mouseStillDownRecipient.st R Morphic-Base.package/EventHandler.class/instance/access/mouseStillDownSelector.st R Morphic-Base.package/EventHandler.class/instance/access/mouseUpSelector.st R Morphic-Base.package/EventHandler.class/instance/copying/veryDeepFixupWith_.st R Morphic-Base.package/EventHandler.class/instance/events/click_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/events/doubleClickTimeout_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/events/doubleClick_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/events/keyStroke_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/events/mouseDown_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/events/mouseEnterDragging_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/events/mouseEnter_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/events/mouseLeaveDragging_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/events/mouseLeave_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/events/mouseMove_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/events/mouseStillDown_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/events/mouseUp_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/events/send_to_withEvent_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/events/startDrag_fromMorph_.st R Morphic-Base.package/EventHandler.class/instance/initialization/onGestureSend_to_.st R Morphic-Base.package/EventHandler.class/instance/initialization/on_send_to_.st R Morphic-Base.package/EventHandler.class/instance/initialization/on_send_to_withValue_.st R Morphic-Base.package/EventHandler.class/instance/printing/printOn_.st R Morphic-Base.package/EventHandler.class/instance/testing/handlesClickOrDrag_.st R Morphic-Base.package/EventHandler.class/instance/testing/handlesGestureStart_.st R Morphic-Base.package/EventHandler.class/instance/testing/handlesKeyboard_.st R Morphic-Base.package/EventHandler.class/instance/testing/handlesMouseDown_.st R Morphic-Base.package/EventHandler.class/instance/testing/handlesMouseMove_.st R Morphic-Base.package/EventHandler.class/instance/testing/handlesMouseOverDragging_.st R Morphic-Base.package/EventHandler.class/instance/testing/handlesMouseOver_.st R Morphic-Base.package/EventHandler.class/instance/testing/handlesMouseStillDown_.st R Morphic-Base.package/MorphicModel.class/class/window color/patchworkUIThemeColor.st R Morphic-Widgets-Windows.package/MouseOverEventHandler.class/README.md R Morphic-Widgets-Windows.package/MouseOverEventHandler.class/definition.st R Morphic-Widgets-Windows.package/MouseOverEventHandler.class/instance/as yet unclassified/handlesMouseOver_.st R Morphic-Widgets-Windows.package/MouseOverEventHandler.class/instance/as yet unclassified/mouseOver_fromMorph_.st R Morphic-Widgets-Windows.package/MouseOverEventHandler.class/instance/as yet unclassified/on_send_to_.st R SUnit-UI.package/TestRunner.class/class/window color/patchworkUIThemeColor.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script377.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40377.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Spec-Debugger.package/SpecDebugger.class/class/window color/patchworkUIThemeColor.st R Tool-Browser-Old.package/Browser.class/class/window color/patchworkUIThemeColor.st R Tool-Browser-Old.package/StringHolder.class/class/window color/patchworkUIThemeColor.st R Tool-Changes.package/ChangeList.class/class/window color/patchworkUIThemeColor.st R Tool-FileList.package/FileList.class/class/window color/patchworkUIThemeColor.st R Tool-FilePackageBrowser.package/FileContentsBrowser.class/class/window color/patchworkUIThemeColor.st R Tool-Transcript.package/extension/ThreadSafeTranscript/class/patchworkUIThemeColor.st Log Message: ----------- 40377 14502 remove unsent methods #patchworkUIThemeColor https://pharo.fogbugz.com/f/cases/14502 7390 EventHander and MouseOverEventHandler Cleanup https://pharo.fogbugz.com/f/cases/7390 http://files.pharo.org/image/40/40377.zip

Nov. 20, 2014