- Pharo-dev - lists.pharo.org

Hapao2>>addMethodEdges:scope:view MNU

by sheridan＠sheridan-mahoney.com

Hi, I'm trying to run Hapao2 on the String class and its subclasses, and encountered an error. I downloaded the latest image (50452) for Windows, loaded Roassal2 and S2py, and tried to run the following code: (Hapao2 runTestsForClasses: String withAllSubclasses , StringTest withAllSubclasses) visualize. This worked in previous versions. This time I got an MNU error in Hapao2 >> addMethodEdges:scope:view: It looks like RTEdgeBuilder isn't loaded. Can someone tell me if I am missing a step? Many thanks, Sheridan

Nov. 19, 2015

Re: [Pharo-dev] Preparing for the (already here) future world of multi-core PCs

by Michael J. Forster

This is no small issue, nor a single one. Be careful to distinguish concurrency from parallelism. See Rob Pike's talk/slides on this. Note that many systems can benefit from a concurrent design--even on a single core, where no parallel execution is possible--because the problem is inherently concurrent; note how effectively shared-nothing approaches with Erlang, Go, or Scala/Akka have been used in such domains. In other domains, parallelism--especially nested data parallelism--is more important than concurrency (see http://yosefk.com/blog/parallelism-and-concurrency-need-different-tools.html) The Haskell and other communities have been exploring this with shared memory approaches like STM. So, to better use the slowing but increasing number of cores in today's hardware, we need to understand the many very different use cases and approaches. The lowest-hanging fruit in the Pharo/Squeak world might be to rework the vm and process scheduler to support massive numbers of lighter weight processes similar to Erlang. Check out Andrew Blacks "Erlang in Pharo", http://www.squeaksource.com/Erlang.html. Best, Mike -- View this message in context: http://forum.world.st/Preparing-for-the-already-here-future-world-of-multi-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 18, 2015

Re: [Pharo-dev] Preparing for the (already here) future world of multi-core PCs

by Chris Muller

If you are on Linux, there is a add-on package for OSProcess called CommandShell which includes a class called RemoteTask. It lets you fork a block of code to a separate OS thread and return the result to the calling image via serialization (Fuel or other). IIUC, it takes advantage of Linux memory copy-on-write sharing, so the forking overhead should be proportional to the amount of work done (e.g., memory changes). On Wed, Nov 18, 2015 at 3:56 PM, EuanM <euanmee(a)gmail.com> wrote: > (And yes, I know it's actually here already). > > Now that clock-speed rises have stalled, basically forever, desktop > and laptop PCs are growing ever-increasing numbers of cores in their > CPU chips, > > Is there design and conceptualisations work going on to see how Pharo > will deal with providing increased access to the additional processing > power? > > > One thing I have been thinking about is a set of co-operating Pharo VMs. > > But given memory and storage are shared, this may not provide as large > a benefit as we'd like. > > Or moving Pharo into being having multiple native-threads, and taking > Pharo into a concurrency route. > > Or - whatever it is I am too ignorant to see. > > This all strikes me (like the way Smalltalk is extending its system > boundary out onto the web with Monticello, Pharo is extending that > via the Configuration Browser and Versionner) as a way Pharo could > build on Smalltalk, while becoming its own thing. (as opposed to > being a Smalltalk with a very big set of classes). > > Is there thought work going on in this area yet? > > DabbleDB had a system of running multiple VMs on a server, and > hot-swapping them in and out depending on their CPU loading. > > Did that ever get developed intop a more generally-useful facility? >

Nov. 18, 2015

Re: [Pharo-dev] Preparing for the (already here) future world of multi-core PCs

by Levente Uzonyi

Searching with the right keywords should have directed you to HydraVM[1] and RoarVM[2][3], which are two different approaches to this problem. Both projects are stalled, and would require significant effort to merge them with the current VM sources. RoarVM also requires images changes, because it brings the concurrency problems up to the Smalltalk level. There are plans for Spur to have some kind of support for multi-core machines, though that'll be different than what you described, because Smalltalk code will still be executed by one core at a time. Levente [1] http://forum.world.st/ANN-Hydra-VM-A-multi-core-capable-Croquet-VM-td106298… [2] http://stefan-marr.de/2010/11/roarvm-the-manycore-squeakvm/ [3] https://github.com/smarr/RoarVM On Wed, 18 Nov 2015, EuanM wrote: > (And yes, I know it's actually here already). > > Now that clock-speed rises have stalled, basically forever, desktop > and laptop PCs are growing ever-increasing numbers of cores in their > CPU chips, > > Is there design and conceptualisations work going on to see how Pharo > will deal with providing increased access to the additional processing > power? > > > One thing I have been thinking about is a set of co-operating Pharo VMs. > > But given memory and storage are shared, this may not provide as large > a benefit as we'd like. > > Or moving Pharo into being having multiple native-threads, and taking > Pharo into a concurrency route. > > Or - whatever it is I am too ignorant to see. > > This all strikes me (like the way Smalltalk is extending its system > boundary out onto the web with Monticello, Pharo is extending that > via the Configuration Browser and Versionner) as a way Pharo could > build on Smalltalk, while becoming its own thing. (as opposed to > being a Smalltalk with a very big set of classes). > > Is there thought work going on in this area yet? > > DabbleDB had a system of running multiple VMs on a server, and > hot-swapping them in and out depending on their CPU loading. > > Did that ever get developed intop a more generally-useful facility? > >

Nov. 18, 2015

Preparing for the (already here) future world of multi-core PCs

by EuanM

(And yes, I know it's actually here already). Now that clock-speed rises have stalled, basically forever, desktop and laptop PCs are growing ever-increasing numbers of cores in their CPU chips, Is there design and conceptualisations work going on to see how Pharo will deal with providing increased access to the additional processing power? One thing I have been thinking about is a set of co-operating Pharo VMs. But given memory and storage are shared, this may not provide as large a benefit as we'd like. Or moving Pharo into being having multiple native-threads, and taking Pharo into a concurrency route. Or - whatever it is I am too ignorant to see. This all strikes me (like the way Smalltalk is extending its system boundary out onto the web with Monticello, Pharo is extending that via the Configuration Browser and Versionner) as a way Pharo could build on Smalltalk, while becoming its own thing. (as opposed to being a Smalltalk with a very big set of classes). Is there thought work going on in this area yet? DabbleDB had a system of running multiple VMs on a server, and hot-swapping them in and out depending on their CPU loading. Did that ever get developed intop a more generally-useful facility?

Nov. 18, 2015

Re: [Pharo-dev] News about FastTable

by Thierry Goubier

Hi Cyril, Le 18/11/2015 10:53, Ferlicot D. Cyril a Ã©crit : > Hi everyone! > > I just wanted to say that I added a first version of Tree in FastTable > and I corrected some bugs. > > If someone want to try it and give some feedback you can see some > examples on the latest Pharo 5 in FTExamples class. Some feedback: On exampleTree1, * expand AJBaseReg, * select AJx87Register, * then collapse AJBaseReg... selection becomes AJCallInfo. * expand AJBaseReg selection becomes AJx87Register Listening to the FTSelectionChanged announcement when doing the sequence above shows that no events are sent during collapse/expand showing the selection change in the tree (i.e. switching from AJx87Register to AJCallInfo and back). Normal GUI behavior is that selection switch to collapsed item if selection was previously among that item children. Regards, Thierry > With Usman we also worked on the glamour version of FastTable begun by > Esteban. > You can see some examples of FastList, FastTable, FastOutlineList and > FastTree in the GLMExamplesBrowser after executing this: > > (ConfigurationOfFastTable project version: #stable) load: #glamour > > Every feedback is welcome :) >

Nov. 18, 2015

[pharo-project/pharo-core]

by GitHub

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

Nov. 18, 2015

[pharo-project/pharo-core] 076939: 50453

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 07693925e92be86f3cb83d20b5be67b3a23319e5 https://github.com/pharo-project/pharo-core/commit/07693925e92be86f3cb83d20… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-11-18 (Wed, 18 Nov 2015) Changed paths: M Morphic-Base.package/HaloMorph.class/instance/private/doGrow_with_.st R Morphic-Base.package/extension/PasteUpMorph/instance/acceptDroppingMorph_event_.st R Morphic-Base.package/extension/PasteUpMorph/instance/fitAll.st R Morphic-Base.package/extension/PasteUpMorph/instance/grabLassoFromScreen_.st R Morphic-Base.package/extension/PasteUpMorph/instance/grabRubberBandFromScreen_.st R Morphic-Base.package/extension/PasteUpMorph/instance/keystrokeInWorld_.st R Morphic-Base.package/extension/PasteUpMorph/instance/modelWakeUp.st M Morphic-Base.package/extension/WorldState/class/windowsOn_.st R Morphic-Core.package/Morph.class/instance/Morphic-Base-Pluggable Widgets/beginsWith_fromList_.st A Morphic-Core.package/Morph.class/instance/Morphic-Base-Widgets/beginsWith_fromList_.st A Morphic-Core.package/Morph.class/instance/event handling/handlesMouseOver_.st A Morphic-Core.package/Morph.class/instance/event handling/mouseWheel_.st R Morphic-Core.package/Morph.class/instance/miscellaneous/setExtentFromHalo_.st R Morphic-Core.package/Morph.class/instance/other events/menuButtonMouseEnter_.st R Morphic-Core.package/Morph.class/instance/other events/menuButtonMouseLeave_.st R Morphic-Core.package/Morph.class/instance/recategorized/handlesMouseOver_.st M Morphic-Core.package/Morph.class/instance/user interface/initialExtent.st A Morphic-Core.package/PasteUpMorph.class/instance/accessing/backgroundMorph.st A Morphic-Core.package/PasteUpMorph.class/instance/accessing/backgroundMorph_.st A Morphic-Core.package/PasteUpMorph.class/instance/event handling/acceptDroppingMorph_event_.st M Morphic-Core.package/PasteUpMorph.class/instance/halos and balloon help/wantsHaloFromClick.st R Morphic-Core.package/PasteUpMorph.class/instance/recategorized/backgroundMorph.st R Morphic-Core.package/PasteUpMorph.class/instance/world menu/delayedInvokeWorldMenu_.st R Morphic-Core.package/PasteUpMorph.class/instance/world menu/extractScreenRegion_andPutSketchInHand_.st R Morphic-Core.package/PasteUpMorph.class/instance/world menu/grabDrawingFromScreen_.st R Morphic-Core.package/PasteUpMorph.class/instance/world menu/respondToCommand_bySending_to_.st R Morphic-Core.package/PasteUpMorph.class/instance/world menu/showImage_.st R Morphic-Core.package/PasteUpMorph.class/instance/world state/checkCurrentHandForObjectToPaste.st R Morphic-Core.package/PasteUpMorph.class/instance/world state/chooseClickTarget.st M Morphic-Core.package/PasteUpMorph.class/instance/world state/deleteAllHalos.st R Morphic-Core.package/WorldMorph.class/instance/event handling/mouseUp_.st A Morphic-Widgets-Taskbar.package/extension/PasteUpMorph/instance/taskList.st R Morphic-Widgets-Taskbar.package/extension/WorldMorph/instance/taskList.st A Morphic-Widgets-Windows.package/extension/Morph/instance/isWindowActive_.st A Morphic-Widgets-Windows.package/extension/Morph/instance/openModal_.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/fitAllVisibleWindows.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/isWindowActive_.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/modalLockTo_.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/modalUnlockFrom_.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/modelWakeUp.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/navigateVisibleWindowForward.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/navigateWindowBackward.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/navigateWindowForward.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/nextVisibleWindow.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/nextWindow.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/openModal_.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/previousWindow.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/systemWindows.st A Morphic-Widgets-Windows.package/extension/PasteUpMorph/instance/visibleSystemWindows.st A Nautilus.package/AbstractNautilusUI.class/instance/styling/addIconStyle.st A Nautilus.package/AbstractNautilusUI.class/instance/styling/removeIconStyle.st A Nautilus.package/AbstractNautilusUI.class/instance/styling/resetIconStyle.st M Nautilus.package/Nautilus.class/instance/history/package_class_protocol_method_.st R Nautilus.package/Nautilus.class/instance/styling/addIconStyle.st R Polymorph-Widgets.package/extension/Morph/instance/heightToDisplayInTree_.st R Polymorph-Widgets.package/extension/Morph/instance/isWindowActive_.st R Polymorph-Widgets.package/extension/Morph/instance/mouseWheel_.st R Polymorph-Widgets.package/extension/Morph/instance/openModal_.st R Polymorph-Widgets.package/extension/Morph/instance/treeRenderOn_bounds_color_font_from_.st R Polymorph-Widgets.package/extension/Morph/instance/widthToDisplayInTree_.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/backgroundMorph_.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/isWindowActive_.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/modalLockTo_.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/modalUnlockFrom_.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/navigateVisibleWindowForward.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/navigateWindowBackward.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/navigateWindowForward.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/nextVisibleWindow.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/nextWindow.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/openModal_.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/previousWindow.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/systemWindows.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/visibleSystemWindows.st M Rubric.package/RubSmalltalkEditor.class/class/accessing/menuOn_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50452.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50453.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50452.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50453.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M SmartSuggestions.package/extension/SmalltalkEditor/instance/smartSuggestions.st A Spec-MorphicAdapters.package/extension/Morph/instance/heightToDisplayInTree_.st A Spec-MorphicAdapters.package/extension/Morph/instance/treeRenderOn_bounds_color_font_from_.st A Spec-MorphicAdapters.package/extension/Morph/instance/widthToDisplayInTree_.st M Text-Edition.package/SmalltalkEditor.class/class/menu declaration/smalltalkEditorMenuOn_.st Log Message: ----------- 50453 17049 Morphic-Core cleanup https://pharo.fogbugz.com/f/cases/17049 17048 visualization of breakpoints logic on nautilus ui + reset logic to support remove all breakpoints on a method https://pharo.fogbugz.com/f/cases/17048 17039 Broken context menu in MessageBrowsers code pane https://pharo.fogbugz.com/f/cases/17039 http://files.pharo.org/image/50/50453.zip

Nov. 18, 2015

Re: [Pharo-dev] Never ending BlockClosure>>benchFor:

by Max Leske

I went ahead and implemented a simple fix for the styler. Not sure how well it performs but in my simple experiments it seems to work fine. Please test it and let me know what you think. https://pharo.fogbugz.com/f/cases/17050/SHTextStyler-styleInBackgroundProce… Cheers, Max > On 18 Nov 2015, at 19:02, Andreas Wacknitz <A.Wacknitz(a)gmx.de> wrote: > > > > Am 18.11.15 um 11:48 schrieb Andrei Chis: >> Can you try the script below in the latest Pharo image and let me know how much does it take to execute on your machine: >> >> |duration benchmarkResult| >> 100 timesRepeat: [ >> RubScrolledTextMorph new >> model: (RubScrolledTextModel new setInitialText: '1+1'; yourself); >> beForSmalltalkScripting; >> yourself >> ] . >> >> duration := 100 milliSeconds. >> benchmarkResult := [ 100 factorial ] benchFor: duration. >> >> In my case it takes around 1 minute. The inner loop finishes immediately and then most time is spend executing the benchmark. >> >> At the end I get the following result: >> "a BenchmarkResult(2,060,386 iterations in 1 minute 7 seconds 498 milliseconds. 30,525 per second)" >> >> So the benchmark is executed for over one minute before the delay expires. >> >> >> > "a BenchmarkResult(1,263,573 iterations in 37 seconds 689 milliseconds. 33,526 per second)" > (HP Z420 with Xeon E5-1620 under OpenIndiana). > > Regards > Andreas

Nov. 18, 2015

Re: [Pharo-dev] Never ending BlockClosure>>benchFor:

by Andreas Wacknitz

Am 18.11.15 um 11:48 schrieb Andrei Chis: > Can you try the script below in the latest Pharo image and let me know > how much does it take to execute on your machine: > > |duration benchmarkResult| > 100 timesRepeat: [ > RubScrolledTextMorph new > model: (RubScrolledTextModel new setInitialText: '1+1'; yourself); > beForSmalltalkScripting; > yourself > ] . > > duration := 100 milliSeconds. > benchmarkResult := [ 100 factorial ] benchFor: duration. > > In my case it takes around 1 minute. The inner loop finishes > immediately and then most time is spend executing the benchmark. > > At the end I get the following result: > "a BenchmarkResult(2,060,386 iterations in 1 minute 7 seconds 498 > milliseconds. 30,525 per second)" > > So the benchmark is executed for over one minute before the delay expires. > > > "a BenchmarkResult(1,263,573 iterations in 37 seconds 689 milliseconds. 33,526 per second)" (HP Z420 with Xeon E5-1620 under OpenIndiana). Regards Andreas

Nov. 18, 2015