- Pharo-dev - lists.pharo.org

[ANN] OSSubprocess first milestone
by Mariano Martinez Peck Jan. 15, 2016

Jan. 15, 2016

Dear all, I am happy to tell you I have a first prototype of the tool for executing OS processes: https://github.com/marianopeck/OSSubprocess As I said many times, the main idea was to be as much as possible FFI-based, only for executing OS commands and, from my point of view, a better end-user API. Also, as for the first step, I had to focus on Linux/OSX. I would like to thank Pharo Consortium for the sponsor of this development effort. Here is the first milestone! There are many things on my to-do but I think the code is ready for some usage, testing, code review and feedback! All classes and all methods have comments and I have quite some unit tests. All tests are green in my OSX and a CentOS box. *Important: you CANNOT have OSProcess installed in the same image as OSSubprocess. This is because I am reusing his SIGCHLD handler and for the time being both cannot coexist. * Keep in mind that the tool may be unstable and that MAY mean a VM crash. So use with care, mostly the first time. If all tests passes, then there are much less chances of something going bad. Important disclaimer: my tool (OSSubproccess from now onward) is HIGHLY influenced by a subset of the OSProcess project. There are parts which I even simply copied and adapted them (OSSPipe, OSSAttachableStream, OSSUnixProcessExitStatus). Other parts, I took them as inspiration (the idea of ThisOSProcess representing the VM process, the child watcher, and many others). In addition, I AM STILL USING (maybe as a first step?) some of the OSProcess PLUGIN (not OSProcess image side), such as the SIGCHLD handler or the creation of pipes. In github url you have all the documentation of the project, included how to install it and use it. *Finally, if you test it in a OS different than OSX and CentOS please share with me the results (about the tests).* Tomorrow the ConfigurationOf should also appear in the Catalog of Pharo 5.0. Any feedback is appreciated. Best, -- Mariano http://marianopeck.wordpress.com

5 6

spotter much slower (GTools 3.6)
by Nicolai Hess Jan. 15, 2016

Jan. 15, 2016

since pharo 50524 spotter is much slower. Most probably related to search results from classes with many subclasses Morph / Object / Error / Announcement. For example, search for Announcement and dive into the result for the Announcement class. It takes about ~ 10 seconds to build the result page (instance methods / super instance methods....) Testcase GTSpotterStepTest>>timeClassTest:aClassName [ self basicSearch:aClassName ] timeToRun logCr. "Pharo 50523" timeClassTest:'Announcement' 0:00:00:00.539 timeClassTest:'Morph' 0:00:00:01.448 "Pharo 50524" timeClassTest:'Announcement' 0:00:00:06.936 timeClassTest:'Morph' 0:00:00:49.044 Or open SUnit Testrunner and run tests for package: GT-Tests-Spotter-Scripting nicolai

3 4

(Spec/Morphic) MorphTreeNodeMorph>>setSelectedSilently: does not seem to select silently.
by Skip Lentz Jan. 15, 2016

Jan. 15, 2016

Hi, I had some problems with TreeModel>>deselectAll. It appears that when one sends #deselectAll, the selectedItemsChanged block is passed a _non-empty_ selection. While debugging I saw that #setSelectedSilently: apart from setting a #selected instance variable, also sends #selected: to its âcomplexContentsâ, which triggers an Announcement chain causing the bug in the previous paragraph. When removing this statement from #setSelectedSilently: it seems to work properly. However I donât know if this âfixâ of mine has any side effects causing it to break at other parts of UI code which is not using Spec. I opened an issue on fogbugz: https://pharo.fogbugz.com/f/cases/17391 Thanks

1 0

#sum:, #detectSum:, #sumNumbers:
by Max Leske Jan. 15, 2016

Jan. 15, 2016

Hi guys, Collection defines #sum:, #detectSum: and #sumNumbers:, all of which accomplish the same (in principal) but with subtle differences: #sum: - uses #inject:into: with #anyOne as the injected element and will thus fail for empty collections #detectSum: - uses ânextValue + sumâ instead of âsum + nextValueâ which makes it a lot slower when dealing with large numbers (primitive fails and number conversion is necessary) #sumNumbers: - same as #sum but doesnât fail for empty collections. Only good for numbers though. Benchmarks: [ 100 timesRepeat: [ (1 to: 1000000) sum: #yourself ] ] timeToRun 18062 [ 100 timesRepeat: [ (1 to: 1000000) detectSum: #yourself ] ] timeToRun 42391 [ 100 timesRepeat: [ (1 to: 1000000) sumNumbers: #yourself ] ] timeToRun 18096 Can we settle for a single implementation? Such as (modified from #sumNumbers:): newSum: aBlock ^ self inject: (self ifEmpty: [ 0 ] ifNotEmpty: [ self anyOne ]) into: [ :sum :each | sum + (aBlock value: each) ] This implementation combines the best of the three implementations I think. Benchmark: [ 100 timesRepeat: [ (1 to: 1000000) newSum: #yourself ] ] timeToRun 17955 BTW, there is also the message #sum, which suffers from the same problem as #sum: (the implementation is basically a copy). #sum could be implemented as sum ^ self sum: [ :x | x ] As for the name for the new method, I suggest #sum:. Cheers, Max

21 96

Question about attribution under the MIT License
by Sven Van Caekenberghe Jan. 15, 2016

Jan. 15, 2016

Hi, I have a been wondering recently about attribution under the MIT License. Code in Pharo and code contributed to Pharo is and should be licensed under the MIT License. https://en.wikipedia.org/wiki/MIT_License Contributors sign an extra agreement. http://files.pharo.org/media/PharoSoftwareDistributionAgreement.pdf Here, contributors give a license so Pharo can include their code. As I read the MIT license the original author keeps the copyright and about the only requirement is that that copyright shall be included when the code is used. The extra agreement does not transfer copyright. So, all authors should be mentioned in the general Pharo MIT license. The reason I was thinking about this is that many people on the list seems to be under the impression that MIT licensed code means that you can freely copy it, like most recently in the discussions about Dophin Smalltalk. I think copying MIT licensed code requires proper attribution. If people copy (my, someone else's) code from Pharo to somewhere else, I want them to at least acknowledge that fact, preferably include a general Pharo (contributors) copyright, but ideally (my, their) copyright. But that would also mean that Pharo has to do the same. I think we should list and update the official contributor list, including the historical list of original authors going back. Am I right or wrong ? How do other people feel about this ? Sven

4 4

[pharo-project/pharo-core] 0d016b: 50527
by GitHub Jan. 14, 2016

Jan. 14, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 0d016b26ee0e42f8c1960fefefde84d9f1444739 https://github.com/pharo-project/pharo-core/commit/0d016b26ee0e42f8c1960fef… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-14 (Thu, 14 Jan 2016) Changed paths: M ConfigurationOfFastTable.package/ConfigurationOfFastTable.class/instance/symbolic versions/stable_.st A ConfigurationOfFastTable.package/ConfigurationOfFastTable.class/instance/versions/version083_.st M Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/drawing/drawOn_.st R Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/drawing/toSelectionRow_primary_.st M Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/updating/updateExposedRows.st A Morphic-Widgets-FastTable.package/FTTableMorph.class/instance/accessing colors/colorForSelection_.st M Morphic-Widgets-FastTable.package/FTTableMorph.class/instance/private/selectRowIndex_event_.st M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/definition.st A Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/accessing/selectionColor_.st M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/event handling/mouseEnter_.st M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/event handling/mouseLeave_.st M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialization/initialize.st M Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialize/defaultColor.st A Morphic-Widgets-FastTable.package/FTTableRowMorph.class/instance/initialize/selectionColor.st R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/README.md R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/class/instance creation/new.st R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/class/instance creation/table_row_primary_.st R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/definition.st R Morphic-Widgets-FastTable.package/FTTableSelectionMorph.class/instance/initialization/initializeTable_row_primary_.st M Nautilus.package/AbstractNautilusUI.class/instance/private/runTestsOfClass_notifying_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50526.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50527.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50526.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50527.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50527 17379 FastTable mouse over on highlighted item https://pharo.fogbugz.com/f/cases/17379 17386 Nautilus test notification should show test results https://pharo.fogbugz.com/f/cases/17386 http://files.pharo.org/image/50/50527.zip

2 1

[pharo-project/pharo-core]
by GitHub Jan. 14, 2016

Jan. 14, 2016

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

1 0

Launcher 0.2.9 opens Spur images
by Damien Cassou Jan. 14, 2016

Jan. 14, 2016

Hi list, thanks to the awesome work of Vincent Blondeau, Stephan Eggermont and Cyril Ferlicot, Pharo Launcher 0.2.9 can be configured to open both spur and pre-spur Pharo images. You can download this version from http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher. You can safely replace your existing Launcher installation with the new one. Your images won't be affected and you will still be able to launch them. The VM coming with these builds is a pre-spur VM because Launcher is based on Pharo 4. If you want to launch Pharo 5 spur images, you need to separately download a Pharo 5 Spur VM from http://get.pharo.org/vm50 and configure the location of this VM in the Launcher settings (icon at the bottom left of the Launcher window). What I like about this release is that I didn't do anything but changing the version number in https://ci.inria.fr/pharo/view/all/job/Launcher :-). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

1 0

Bug in protocol and method selection
by stepharo Jan. 14, 2016

Jan. 14, 2016

Hi There is a problem in latest Pharo. I cannot select (and keep the selection selected) of a method and method protocol. To me it looks like QA is interferring but I do not know. This is the kind of glitches that can kill our effort doing videos. We have a strong deadline for producing such videos. beginning of march but we want to get done before any help is welcome. Stef

3 6

About LayoutFrame>>fractions:offsets:
by stepharo Jan. 14, 2016

Jan. 14, 2016

Here is the new class comments I'm trying to write. I hope that it will help people to understand the circumstances under which they should use fractions:offset: creation API. I define a transformation frame relative to some rectangle. I'm basic data structure used for graphics. I represent two groups of distances: - The fractional distance (between 0 and 1) to place the morph in its owner's bounds - Fixed pixel offset to apply after fractional positioning (e.g., "10 pixel right of the center of the owner") !! API usage It is important to understand that it is better to use the fine grained API using elementary distances (bottomFraction:, bottomOffset:, leftFraction: ....) than the ones (historical) using points and rectangles (fractions:offsets:) The reason is that the old API (fractions:offsets:) is only interesting if you already have a rectangle and points at hand. If you need to create new ones, then they are created for nothing because they will be destructured to extract their information to be feed into the layoutFrame. So please do not blindly copy and paste code! Example: Favor (LayoutFrame identity leftFraction: 0; yourself); (LayoutFrame identity leftFraction: 0.5; rightFraction: 0.95; (LayoutFrame identity topOffset: topHeight; bottomFraction: 0; bottomOffset: self buttonsBarHeight; leftOffset: -1; rightOffset: 1) over (LayoutFrame fractions: (0 @ 0 corner: 1 @ 1)) because you are creating for nothing a new rectangle and some points. !! Implementation Instance variables: The fractional distance (between 0 and 1) to place the morph in its owner's bounds is represented by the following instance variables: leftFraction topFraction rightFraction bottomFraction <Float> Fixed pixel offset to apply after fractional positioning (e.g., "10 pixel right of the center of the owner") is represented by the following instance variables: leftOffset topOffset rightOffset bottomOffset <Integer>

4 8