- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Metacello configuration conventions
by Stephan Eggermont April 16, 2013

April 16, 2013

Frank wrote: >I'd argue that since you're declaring that a certain set of versions >of packages work together, you should _always_ use explicit versions. >The "optimistic" strategy leaves you vulnerable to third parties >making seemingly innocuous changes that break your code. (I've been >bitten by this, by making such an apparently innocuous change.) Thank you. That's a clear vulnerability of the optimistic strategy. That sounds nice, but also means getting a change rate that is the sum of that of all your dependencies. It is also not very nice when you are depending on things that have known bugs you know will be fixed soon. What does it mean that a certain set of versions work together? Implicit seems the assumption that #Pharo2x is #stable, and we don't talk about the vm version or even worse the non-smalltalk dependencies. I don't see Metacello descriptions specifying all loaded packages. Stephan

2 1

[Pharo-project] [update 3.0] #30043
by Marcus Denker April 16, 2013

April 16, 2013

30043 ----- 10302 RBparser: improve error message https://pharo.fogbugz.com/f/cases/10302 10286 Remove NaturalLanguageTranslator from image startup list https://pharo.fogbugz.com/f/cases/10286/ 10109 MNU : SmalltalkEditor>>browseItHere: https://pharo.fogbugz.com/f/cases/10109 and remove Opal repos Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/AST-Core-MarcusDenker.127

1 0

[Pharo-project] [update 3.0] #30041
by Esteban Lorenzano April 16, 2013

April 16, 2013

30041 ----- 10028 Integrate Opal https://pharo.fogbugz.com/f/cases/10028 WARNING: ======== 1) Opal is still not default compiler, it is there to allow us to improve it and put it on shape 2) Please, help on it by providing bug reports, etc. :)

4 4

[Pharo-project] [regression reporter]regression occurred
by no-reply＠ci.inria.fr April 16, 2013

April 16, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 71 regressions found. CompilerTests.ClosureCompilerTest.testBlockDoitDecompilation CompilerTests.ClosureCompilerTest.testDecompiledDoitMethodTempNames CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureBytecodeInjectInto CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureLongFormBytecodeInjectInto CompilerTests.ClosureCompilerTest.testSourceRangeAccessForInjectInto CompilerTests.CompilerExceptionsTest.testAmbiguousSelector CompilerTests.CompilerExceptionsTest.testUndeclaredVariable CompilerTests.CompilerExceptionsTest.testUndefinedVariable CompilerTests.CompilerExceptionsTest.testUnknownSelector CompilerTests.CompilerExceptionsTest.testUnusedVariable CompilerTests.CompilerNotifyingTest.testATempShadowingAnotherTemp CompilerTests.CompilerNotifyingTest.testAlltogether CompilerTests.CompilerNotifyingTest.testAssignmentOfSelf CompilerTests.CompilerNotifyingTest.testCascadeInASuperSend CompilerTests.CompilerNotifyingTest.testDigitTooLargeForARadix CompilerTests.CompilerNotifyingTest.testEmptyCaseStatement CompilerTests.CompilerNotifyingTest.testExpectedExpressionInBraceArray CompilerTests.CompilerNotifyingTest.testExtraneousStatementAfterAReturnInABlock CompilerTests.CompilerNotifyingTest.testInvalidRadix CompilerTests.CompilerNotifyingTest.testLiteralCharacterMissing ...

1 0

[Pharo-project] [regression reporter]regression occurred
by no-reply＠ci.inria.fr April 16, 2013

April 16, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 71 regressions found. CompilerTests.ClosureCompilerTest.testBlockDoitDecompilation CompilerTests.ClosureCompilerTest.testDecompiledDoitMethodTempNames CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureBytecodeInjectInto CompilerTests.ClosureCompilerTest.testSourceRangeAccessForClosureLongFormBytecodeInjectInto CompilerTests.ClosureCompilerTest.testSourceRangeAccessForInjectInto CompilerTests.CompilerExceptionsTest.testAmbiguousSelector CompilerTests.CompilerExceptionsTest.testUndeclaredVariable CompilerTests.CompilerExceptionsTest.testUndefinedVariable CompilerTests.CompilerExceptionsTest.testUnknownSelector CompilerTests.CompilerExceptionsTest.testUnusedVariable CompilerTests.CompilerNotifyingTest.testATempShadowingAnotherTemp CompilerTests.CompilerNotifyingTest.testAlltogether CompilerTests.CompilerNotifyingTest.testAssignmentOfSelf CompilerTests.CompilerNotifyingTest.testCascadeInASuperSend CompilerTests.CompilerNotifyingTest.testDigitTooLargeForARadix CompilerTests.CompilerNotifyingTest.testEmptyCaseStatement CompilerTests.CompilerNotifyingTest.testExpectedExpressionInBraceArray CompilerTests.CompilerNotifyingTest.testExtraneousStatementAfterAReturnInABlock CompilerTests.CompilerNotifyingTest.testInvalidRadix CompilerTests.CompilerNotifyingTest.testLiteralCharacterMissing ...

1 0

[Pharo-project] RFB server and 2.0
by Esteban Lorenzano April 16, 2013

April 16, 2013

Hi, Someone has tried RFB in 2.0? I installed it, but looks like it is not working :( Esteban

4 5

[Pharo-project] [update 3.0] #30040
by Marcus Denker April 16, 2013

April 16, 2013

30040 ----- 10290 Typo in selector Exit class>>#signalFaillure: http://pharo.fogbugz.com/f/cases/10290 10258 DivideByZero in SystemProgressMorph https://pharo.fogbugz.com/f/cases/10258 10272 Monticello should provide a proper UI dialog to ask for username and password https://pharo.fogbugz.com/f/cases/10272/ Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Monticello-MarcusDenker.787 http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/MonticelloGUI-MarcusDenker.2… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Kernel-MarcusDenker.1361

1 0

[Pharo-project] Spec DropLists
by Sean P. DeNigris April 16, 2013

April 16, 2013

Issue 6551: [ENH Spec]: Spec-ify DropListModel http://code.google.com/p/pharo/issues/detail?id=6551 Currently: self instantiateModels: #(dropList #DropListModel). item1 := DropListItem named: 'Red morph' do: self redMorphBlock. item2 := DropListItem named: 'Blue morph' do: self blueMorphBlock. item3 := DropListItem named: 'Green morph' do: self greenMorphBlock. dropList items: {item1. item2. item3}. I'd prefer if DropLists were uniform with the rest of Spec, namely: I'd have my domain class MyColor>>description ^ nameOfColor dropList items: {myRedColor. myBlueColor. myGreenColor}; displayBlock: [ :e | e description, ' morph' ]; whenSelectionChanged: [ :e | self showMorphFor: e ]. I'd prefer not to even know that DropListItem exists, and have the model take care of it for me. Something like: DropListModel>>items: aList "Populate the drop list with a list of objects" | items | items := aList collect: [ :e | DropListItem named: e printString do: [ ] ]. listHolder contents: items. Incidentally, #whenSelectionChanged: exists for DropListModels, but is broken. When an item is chosen from the drop list, the announcement received by this block has both new and old contents set to nil: Issue 6550: [BUG Spec]: DropListModel>>whenSelectionChanged: http://code.google.com/p/pharo/issues/detail?id=6550 Cheers, Sean -- View this message in context: http://forum.world.st/Spec-DropLists-tp4643694.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 4

[Pharo-project] FTP repo without storing username/pass in ConfigurationOf
by Mariano Martinez Peck April 16, 2013

April 16, 2013

Hi all, I have the code of an app in a FTP repo which has username/password. I am doing a ConfigurationOfMyApp now and I would need to define in the baseline something like spec repository: 'ftp.mydomainapp.com ...etc'. I know I have a similar method for also specifying the username/pass. But I don't want that because it means storing the username/pass in the ConfigurationOf code. So....how can I manage this with metacello? the only thing I found (which I am not sure if it works) is to use repositoryOverride so when I am about to load my project I do a #repositoryOverride: passing as argument a FTP with my username/password. What do you think? best, -- Mariano http://marianopeck.wordpress.com

2 1

[Pharo-project] [ANN] Pharo VM packages and PPA for Ubuntu
by Damien Cassou April 15, 2013

April 15, 2013

Dear Pharo and Ubuntu users, Nicolas Petton and I are proud to announce Ubuntu packages for the Pharo VM. Installing the pharo vm is now just a matter of: sudo add-apt-repository ppa:cassou/pharo sudo apt-get update sudo apt-get install pharo-vm With this package, you get: - the latest pharo vm as a 'pharo' binary in the PATH - all plugins and libraries (native boost, freetype, ssl, ...) - file association so you can just double-click on pharo images - pharo icons visible everywhere (on image files, on ALT+TAB...) - PharoV10.sources and PharoV20.sources Please fill bug reports on https://pharo.fogbugz.com. This package is currently only available for Ubuntu 12.10 Quantal. Fill a bug report if you want me to package it for another version of Ubuntu. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

6 11