November 2014 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Nov. 20, 2014

Nov. 20, 2014

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

1 0

[pharo-project/pharo-core] be3b36: 40378
by GitHub Nov. 20, 2014

Nov. 20, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: be3b363a977670fdbe7db8858e22295e160283f8 https://github.com/pharo-project/pharo-core/commit/be3b363a977670fdbe7db885… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-20 (Thu, 20 Nov 2014) Changed paths: M Nautilus.package/ClassDefinitionAcceptor.class/instance/protocol/accept_notifying_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script378.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40378.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/ObjectLayout.class/instance/extending/extendSmallInteger.st A Slot.package/SmallIntegerLayout.class/class/instance creation/extending_scope_host_.st Log Message: ----------- 40378 14508 add class ivars to SmallInteger: subclass responsibility #extending:scope:host: https://pharo.fogbugz.com/f/cases/14508 14507 DNU when accepting a class side definition for class instance vars https://pharo.fogbugz.com/f/cases/14507 http://files.pharo.org/image/40/40378.zip

1 0

[ANN] NetGen - OSM Roassal Demo
by Onil Goubier Nov. 20, 2014

Nov. 20, 2014

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

9 11

Message>>#arguments:
by Noury Bouraqadi Nov. 20, 2014

Nov. 20, 2014

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

2 1

How to check whether the handle is always valid with NativeBoost ?
by Blondeau Vincent Nov. 20, 2014

Nov. 20, 2014

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.

4 5

[pharo-project/pharo-core]
by GitHub Nov. 20, 2014

Nov. 20, 2014

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

1 0

[pharo-project/pharo-core] 4dc141: 40377
by GitHub Nov. 20, 2014

Nov. 20, 2014

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

1 0

RTPolygon does not work ?
by Pierre CHANSON Nov. 19, 2014

Nov. 19, 2014

Hi, does anyone know how to use RTPolygon shape or is there a real problem inside ? For exemple you get an error when executing: -=-=-=-=-=-=-=-=-=-=-=-= v := RTView new. p := RTPolygon new vertices:{ 25 @ 00 . 10 @ 50 . 50 @ 20 }. v add: (p elementOn: 1). v open -=-=-=-=-=-=-=-=-=-=-=-= Apparently the instance variable "strokePaint" of TRShape class, would be Nil when used by TRPolygonShape... But this variable seemed to be initialized in color black earlier so... I don't know what's appenning. If someone have a Idea... Thank you, PIerre

2 2

Spur 64-bits. Ugh, this could be a slog...
by Eliot Miranda Nov. 19, 2014

Nov. 19, 2014

Hi All, I'm making good progress on 64-bit Spur in the Stack VM simulator. But I've just noticed an image-level issue which could be indicative of lots of 32-bit assumptions baked into the Squeal/Pharo/Newspeak systems. SmallInteger>>digitAt: n "Answer the value of an indexable field in the receiver. LargePositiveInteger uses bytes of base two number, and each is a 'digit' base 256. Fail if the argument (the index) is not an Integer or is out of bounds." n>4 ifTrue: [^ 0]. self < 0 ifTrue: [self = SmallInteger minVal ifTrue: ["Can't negate minVal -- treat specially" ^ #(0 0 0 64) at: n]. ^ ((0-self) bitShift: (1-n)*8) bitAnd: 16rFF] ifFalse: [^ (self bitShift: (1-n)*8) bitAnd: 16rFF] This assumes that SmallInteger is only ever 4 bytes, which is unacceptably wasteful for my approach to 64-bits. In 64-bit Spur, SmallIntegers are 61-bit 2's complement. I'm raising this example at this point to see if the community might find similar issues and bring them to my attention. -- best, Eliot

2 2

Re: [Pharo-dev] [Vm-dev] Re: Spur 64-bits. Ugh, this could be a slog...
by Eliot Miranda Nov. 19, 2014

Nov. 19, 2014

On Tue, Nov 18, 2014 at 10:03 PM, Ryan Macnak <rmacnak(a)gmail.com> wrote: > Ah, that's true if images have a fixed word size. I had imagined that the > VM would convert an image to the host word size at startup, just as Cog > converts Floats to the host representation. The Float change is transparent > to Smalltalk, but a word size change would be visible through the > identities of objects that are either immediate or heap depending on the > word size. And for mixed format objects like CompiledMethods, the offset > for basicAt: for the beginning of the byte data would change. > Right. And for this reason I find it better to make the change a one-off bootstrap, even if it rewrites a 32-nit image to a 64-bit image, rather thna builds a fresh system from startup (an approach others are pursuing). It doesn't make sense burdening the VM with conversion code that is rarely used. The one-off conversion results in a more performant, reliable solution IMO, much like the V3 to Spur bootstrap itself. On Tue, Nov 18, 2014 at 9:07 PM, David T. Lewis <lewis(a)mail.msen.com> wrote: > > On Tue, Nov 18, 2014 at 07:59:30PM -0800, Ryan Macnak wrote: > > > > What about bytecode pc's? These are indexed based on the physical size of > > the literals. I don't like the idea of debugging pc -> source mappings, > pc > > coverage data, etc needing invalidation after starting an image on a > > platform with a different word size. > > I may be misunderstanding your question, but I do not think that this will > be an issue. All byte addressible objects need to work properly in any > image, > including 32 and 64 bit images. If that part does not work, then the image > will not run, so no problem ;-) > > With respect to platform word size (e.g. 64 bit OS versus 32 bit OS), the > images should all run bit-identically regardless of platform word size. A > 64-bit image can (and does) run on a 32-bit host platform, given a suitably > compiled VM. And a 32-bit image will run on a 64-bit host platform, given a > suitably compiled VM (or more commonly, a 32-bit VM with 32-bit > compatibility > libraries installed on the platform). > > Dave > > > > > > > On Tue, Nov 18, 2014 at 7:12 PM, Eliot Miranda <eliot.miranda(a)gmail.com> > > wrote: > > > > > Hi All, > > > > > > I'm making good progress on 64-bit Spur in the Stack VM simulator. > > > But I've just noticed an image-level issue which could be indicative of > > > lots of 32-bit assumptions baked into the Squeal/Pharo/Newspeak > systems. > > > > > > SmallInteger>>digitAt: n > > > "Answer the value of an indexable field in the receiver. > > > LargePositiveInteger uses bytes of base two number, and each is a > 'digit' > > > base 256. Fail if the argument (the index) is not an Integer or is > out of > > > bounds." > > > n>4 ifTrue: [^ 0]. > > > self < 0 > > > ifTrue: > > > [self = SmallInteger minVal ifTrue: > > > ["Can't negate minVal -- treat specially" > > > ^ #(0 0 0 64) at: n]. > > > ^ ((0-self) bitShift: (1-n)*8) bitAnd: 16rFF] > > > ifFalse: [^ (self bitShift: (1-n)*8) bitAnd: 16rFF] > > > > > > This assumes that SmallInteger is only ever 4 bytes, which is > unacceptably > > > wasteful for my approach to 64-bits. In 64-bit Spur, SmallIntegers are > > > 61-bit 2's complement. > > > > > > I'm raising this example at this point to see if the community might > find > > > similar issues and bring them to my attention. > > > -- > > > best, > > > Eliot > > > > > -- best, Eliot

1 0