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

Pharo 4.0 Update Trigger
by Yuriy Tymchuk Sept. 11, 2014

Sept. 11, 2014

Hi FYI, Iâve added Pharo-4.0-Update-Trigger job on CI https://ci.inria.fr/pharo-contribution/job/Pharo-4.0-Update-Trigger/ so if you have a CI job for your project and it should run on Pharo4, you can re-run it after Update trigger is built to be sure that no changes broke your project. Cheers Uko

2 1

[pharo-project/pharo-core] 4fd357: 40218
by GitHub Sept. 11, 2014

Sept. 11, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 4fd35771a9b42416a5d42e5d89e85fc35fd77a2f https://github.com/pharo-project/pharo-core/commit/4fd35771a9b42416a5d42e5d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-11 (Thu, 11 Sep 2014) Changed paths: M Gofer-Core.package/Gofer.class/class/private/upgrade.st M Gofer-Core.package/GoferLoad.class/instance/private/addResolved_.st M Gofer-Core.package/GoferRevert.class/instance/private/referenceFor_.st M MonticelloGUI.package/MCSaveVersionDialog.class/instance/morphic ui/setDefaultFocus.st M OpalCompiler-Core.package/OCUndeclaredVariableWarning.class/instance/correcting/declareTempAndPaste_.st R Polymorph-Widgets.package/TextEditorDialogWindow.class/class/accessing/autoAccept.st R Polymorph-Widgets.package/TextEditorDialogWindow.class/class/accessing/autoAccept_.st R Polymorph-Widgets.package/TextEditorDialogWindow.class/class/settings/settingsOn_.st R Polymorph-Widgets.package/TextEditorDialogWindow.class/instance/accessing/autoAccept.st M Polymorph-Widgets.package/TextEditorDialogWindow.class/instance/accessing/entryText_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script218.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40218.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40218 13205 Temporary variable declaration in blocks https://pharo.fogbugz.com/f/cases/13205 13989 Temporary variables not read and writen in Gofer-Core https://pharo.fogbugz.com/f/cases/13989 13837 remove TextEditorDialogWindow autoaccept preference https://pharo.fogbugz.com/f/cases/13837 13987 remove empty package Settings-Tools https://pharo.fogbugz.com/f/cases/13987 http://files.pharo.org/image/40/40218.zip

1 0

[pharo-project/pharo-core]
by GitHub Sept. 11, 2014

Sept. 11, 2014

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

1 0

Re: [Pharo-dev] Last Pharo VM on mac os x 10.6.8
by Stephan Eggermont Sept. 10, 2014

Sept. 10, 2014

Just copy the libcairo.2.dylib (in Contents/MacOS/Plugins when you do Show Package Contents on the vm app) from the 18 september 2013 vm. Stephan

1 0

Class names and special names for special things.
by phil＠highoctane.be Sept. 10, 2014

Sept. 10, 2014

I was playing around with the idea of using stuff like in jQuery, where we do have the '$' function that would do a lot of things. But one cannot create such elements as SlotClassBuilder>>validateClassName "Validate the new class name. Raise warning if invalid." name detect: [ :c | (c isAlphaNumeric or: [ c = $_ ]) not ] ifFound: [ :c | InvalidGlobalName signal: 'Invalid character: ''' , c printString , '''' for: name ]. name first canBeGlobalVarInitial ifFalse: [ InvalidGlobalName signal: 'Class name does not start with a valid Global Var Initial' for: name ] doesn't let us. Is there a reason for that (ok, we have $ for chars, and #, ... and other things but still). TIA Phil

3 7

PharoLauncher mac download not the latest version
by kilon alios Sept. 10, 2014

Sept. 10, 2014

So I re downloaded PharoLauncher using this link https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Mac-Package/lastSu… and it is not the latest version as it does not contain the latest commit which is my commit with the new progress bar. At first I thought that it was loading something else than bleedingEdge configuration but I don't see anything else in the ConfigurationOfPharoLauncher. Am I doing something wrong ?

3 6

Last Pharo VM on mac os x 10.6.8
by Serge Stinckwich Sept. 10, 2014

Sept. 10, 2014

Dear all, a guy in my lab try to use the last version of MOOSE 5.0 (last Pharo VM version) on mac os x 10.6.8. Apparently ROASSAL examples does not work (Cairo library problems). Do we have to upgrade his machine to the last mac os x version ? Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

2 1

latex exporter in Pillar
by Alexandre Bergel Sept. 10, 2014

Sept. 10, 2014

Hi! I am currently investigating whether Pillar may be used for the AgileVisualization book. I am interested in exporting to PDF and Latex. I have tried the command: ./pillar export âto=latex first.pier > first.tex But the generated .tex file is not valid since it contains a line: -=-=-=-= \newcommand{\ct}[1]} -=-=-=-= Will this be fixed ? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

5 12

Problem with Roassal examples Composite shapes
by kilon alios Sept. 10, 2014

Sept. 10, 2014

So I was browsing the examples for Roassal 2 that I installed in Pharo 3 and I took a look at Composite Shapes category I tried to view the examples and they all look like the attached image Why ? Am I missing a library or something ? â

2 2

Sept. 10, 2014

Hello guys, I was looking into the OrderedCollection protocols recently to see how well the sista optimizer perform with it methods, and I realized that this is completely broken. For example: col := #(1 2 3 4 5) asOrderedCollection. col do: [ :elem | elem trace . elem < 4 ifTrue: [ col add: col size + 1 ]]. => '12345678' However: col := #(1 2 3 4 5) asOrderedCollection. col collect: [ :elem | elem trace . elem < 4 ifTrue: [ col add: col size + 1 ]]. => '12345' This means that #do: and #reverseDo: iterate over all the elements of the collection,*including* the ones that you are adding while iterating over the collection, whereas all the other OrderedCollection protocols, such as #collect:, #select:, iterates over all the elements of the collection, *excluding* the ones you are adding while iterating over the collection. Marcus argued that one should not edit a collection while iterating over it, however this point is not valid as the World menu relies on this feature, using #do: to iterate over the elements of the OrderedCollection including the one it is adding while iterating over the collection. Changing the implementation makes the world menu display half of its items. I don't like this difference because it is inconsistent. For example, refactoring a #do: into a #collect: can simply not work because they do not iterate over the same elements if you are editing the collection while iterating over it. In VW, the protocols are consistent and iterating over a collection never iterates over the elements one is adding while iterating over it. Therefore, I believe most frameworks should expect this behavior (at least the ones cross smalltalk) which sounds the most correct. I think we should fix the world menu implementation and make the protocols consistent. Alternatively, we can let VW be a much more consistent Smalltalk environment than Pharo. What do you think ? Clement

10 17