- Pharo-dev - lists.pharo.org

I would prefer to see the diff from Smalltalkhub than Git commits
by StÃ©phane Ducasse Aug. 18, 2013

Aug. 18, 2013

Hi could we avoid to get the github commits. I would prefer to get diff from Smalltalkhub. Stef

3 6

Re: [Pharo-dev] I would prefer to see the diff from Smalltalkhub than Git commits
by Stephan Eggermont Aug. 18, 2013

Aug. 18, 2013

Camillo wrote: >- they are auto generate, no manual intervention needed to send them So they should go to the issue tracker list >- the github repository is the place where you go to find changes, it's simply impossible to figure out when > something broke on smalltalkhub since you cannot compare multiple packages over multiple times Sounds like it's time to migrate Torch. Stephan

2 1

pharo.changes write failed
by jannik.laval Aug. 17, 2013

Aug. 17, 2013

Hi, This night, the jenkins job of Phratch failed because of an error to write the .changes file. Trying manually gives the same. For information, I do not change anything in the Phratch code source. ==== Image ----- /Users/janniklaval/Desktop/phratchDev/phratch.image Pharo2.0 Latest update: #20619 Unnamed Virtual Machine --------------- /Users/janniklaval/Desktop/phratchDev/pharo-vm/Pharo.app/Contents/MacOS/Pharo NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< VMMaker versionString git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 ====

3 4

Requested origin error on win8 ?
by Erwan Douaille Aug. 17, 2013

Aug. 17, 2013

Hi a creenshot of what happened when i opened latest 3.0 image with cogVM on win 8. Is it a known issue ?[image: Images intÃ©grÃ©es 1] Thanks :) -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

1 0

Uniformizing Pharo
by StÃ©phane Ducasse Aug. 17, 2013

Aug. 17, 2013

Hi guys I started to be fed up about protocol inconsistencies. So I will propose a set of rules (and a tool - I'm working on it) to automatically categorize methods. The first on the list was printOn: in printing and I clean many methods already with a kind of happy smile on my face. Now we discussed today with esteban for initialize* we will use 'initialization' I hope that this is ok for you because I'm fed up to have the following: {269->'initialization'. 248->'initialize-release'. 48->'as yet unclassified'. 15->'accessing'. 14->'private'. 12->'initializing'. 2->'instance creation'. 2->'testing'. 2->'initalize-release'. 2->'protocol'. 2->'display'. 1->'cleaning'. 1->'intializing'. 1->'like fullCopy'. 1->'keymapping'. 1->'ui-building'. 1->'initialize - release'. 1->'initialization-release'. 1->'intialize'. 1->'styling'. 1->'scrolling'. 1->'morphic ui'. 1->'world state'. 1->#'parts bin'} Please enjoy this gift from life, I love so much 'like fullCopy' as a category for initialize that I'm a bit sad to clean this kind of poem (minimal haiku) so we will keep it for us :) Yes there is no little steps to get a bright system, every little clean is stop. No broken window! No dirt on the floor in Pharo. Stef

7 15

Uniformizing Pharo
by Torsten Bergmann Aug. 17, 2013

Aug. 17, 2013

Instead of category 'setup' for #setUp and #tearDown I would like to see 'running' since this follows the original SUnit and tearDown has nothing to do with setting up the test case, more with cleaning up. What about binary messages like = for comparing? I would also like to see one for methods matching example... to be in examples. Beside is... for 'testing' there could also be was...., it should take into account the next Character is Uppercase. What about also taking pragmas into account? With that NB Api wrappers could be categorized into 'api' or 'primitive' (which is more general)

2 1

Why the github messages?
by Stephan Eggermont Aug. 16, 2013

Aug. 16, 2013

Why is github writing messages to this list (instead of the issue tracker list)? Stephan

2 1

[pharo-project/pharo-core]
by GitHub Aug. 16, 2013

Aug. 16, 2013

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

1 0

[pharo-project/pharo-core] 6c1085: 30332
by GitHub Aug. 16, 2013

Aug. 16, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 6c10859bcad73cba655eeb8db8ae9b54b53f5403 https://github.com/pharo-project/pharo-core/commit/6c10859bcad73cba655eeb8d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-08-16 (Fri, 16 Aug 2013) Changed paths: M KernelTests-Numbers/NumberParsingTest.cls/instance/tests - Float/testNumberReadOnlyDigit.st M KernelTests-Numbers/SqNumberParserTest.cls/instance/tests - Float/testFloatReadError.st M KernelTests-Numbers/SqNumberParserTest.cls/instance/tests - Integer/testIntegerReadFrom.st R Nautilus/extension/TClass/instance/buildAnalyzeSubMenu_.st A Nautilus/extension/TClassDescription/instance/buildAnalyzeSubMenu_.st R Nautilus/extension/Trait/instance/buildAnalyzeSubMenu_.st A Nautilus/extension/TraitDescription/instance/buildAnalyzeSubMenu_.st R NautilusRefactoring/extension/Class/instance/instVarRefactoring_.st R NautilusRefactoring/extension/Class/instance/methodRefactoring_.st R NautilusRefactoring/extension/Class/instance/refactoringMenu_.st R NautilusRefactoring/extension/Class/instance/refactoringSubmenu_.st R NautilusRefactoring/extension/Class/instance/varRefactoringSubMenu_.st A NautilusRefactoring/extension/ClassDescription/instance/instVarRefactoring_.st A NautilusRefactoring/extension/ClassDescription/instance/methodRefactoring_.st A NautilusRefactoring/extension/ClassDescription/instance/refactoringMenu_.st A NautilusRefactoring/extension/ClassDescription/instance/refactoringSubmenu_.st A NautilusRefactoring/extension/ClassDescription/instance/varRefactoringSubMenu_.st R NautilusRefactoring/extension/TClass/instance/codeRewritingClass_.st R NautilusRefactoring/extension/TClass/instance/groupRefactoring_.st R NautilusRefactoring/extension/TClass/instance/instVarRefactoring_.st R NautilusRefactoring/extension/TClass/instance/methodRefactoring_.st R NautilusRefactoring/extension/TClass/instance/packageRefactoringMenu_.st R NautilusRefactoring/extension/TClass/instance/refactoringMenu_.st R NautilusRefactoring/extension/TClass/instance/refactoringMethod_.st R NautilusRefactoring/extension/TClass/instance/refactoringSubmenu_.st R NautilusRefactoring/extension/TClass/instance/renameMethodAllItem_.st R NautilusRefactoring/extension/TClass/instance/sourceCodeRefactoringMenu_.st R NautilusRefactoring/extension/TClass/instance/sourceCodeRefactoring_.st R NautilusRefactoring/extension/TClass/instance/varRefactoringSubMenu_.st A NautilusRefactoring/extension/TClassDescription/instance/codeRewritingClass_.st A NautilusRefactoring/extension/TClassDescription/instance/groupRefactoring_.st A NautilusRefactoring/extension/TClassDescription/instance/instVarRefactoring_.st A NautilusRefactoring/extension/TClassDescription/instance/methodRefactoring_.st A NautilusRefactoring/extension/TClassDescription/instance/packageRefactoringMenu_.st A NautilusRefactoring/extension/TClassDescription/instance/refactoringMenu_.st A NautilusRefactoring/extension/TClassDescription/instance/refactoringMethod_.st A NautilusRefactoring/extension/TClassDescription/instance/refactoringSubmenu_.st A NautilusRefactoring/extension/TClassDescription/instance/renameMethodAllItem_.st A NautilusRefactoring/extension/TClassDescription/instance/sourceCodeRefactoringMenu_.st A NautilusRefactoring/extension/TClassDescription/instance/sourceCodeRefactoring_.st A NautilusRefactoring/extension/TClassDescription/instance/varRefactoringSubMenu_.st R NautilusRefactoring/extension/Trait/instance/instVarRefactoring_.st R NautilusRefactoring/extension/Trait/instance/methodRefactoring_.st R NautilusRefactoring/extension/Trait/instance/refactoringMenu_.st R NautilusRefactoring/extension/Trait/instance/refactoringSubmenu_.st R NautilusRefactoring/extension/Trait/instance/varRefactoringSubMenu_.st A NautilusRefactoring/extension/TraitDescription/instance/instVarRefactoring_.st A NautilusRefactoring/extension/TraitDescription/instance/methodRefactoring_.st A NautilusRefactoring/extension/TraitDescription/instance/refactoringMenu_.st A NautilusRefactoring/extension/TraitDescription/instance/refactoringSubmenu_.st A NautilusRefactoring/extension/TraitDescription/instance/varRefactoringSubMenu_.st A ScriptLoader30/ScriptLoader.cls/instance/pharo - scripts/script124.st A ScriptLoader30/ScriptLoader.cls/instance/pharo - updates/update30332.st M ScriptLoader30/ScriptLoader.cls/instance/public/commentForCurrentUpdate.st A Spec-Inspector/InspectorWrapper.cls/instance/initialize/initialExtent.st Log Message: ----------- 30332 - issue 11414 Fixing s1 change parsing https://pharo.fogbugz.com/default.asp?11414 - issue 11409 EyeInspector class-side slot #useAutoRefresh is missing https://pharo.fogbugz.com/default.asp?11409 - issue 11411 Cannot resize inspector window per inspector class https://pharo.fogbugz.com/default.asp?11411 - 11410 failing test (Polymorphism between classes and traits) https://pharo.fogbugz.com/default.asp?11410

1 0

[pharo-project/pharo-core]
by GitHub Aug. 16, 2013

Aug. 16, 2013

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

1 0