- Pharo-dev - lists.pharo.org

Broken Form>>dominantColor in 3.0
by Hilaire Fernandes March 8, 2014

March 8, 2014

Hello, Problem described there, https://pharo.fogbugz.com/f/cases/13057/DominantColor-brokem It seems to be related to BitBlt, combinationRule #33 Any idea? Thanks Hilaire -- Dr. Geo http://drgeo.eu

1 0

Coral (again)
by phil＠highoctane.be March 8, 2014

March 8, 2014

I would like to know where to look to get a "valid"/"best" version of Coral to use/work on. I am going to need to work in an assignment where there are a number of scripting things to do and I'd like to give Pharo a shot. I'd like to be able to use Coral, as I liked the video about it and how it worked. I saw that Camillo has it on GitHub. TIA for the pointers. Phil

2 1

Re: [Pharo-dev] Coral (again)
by Stephan Eggermont March 7, 2014

March 7, 2014

I would be strongly interested in using Coral as a replacement for puppet/chef/salt Stephan

1 0

12911 Tests-failing-in-fresh-image-MetacelloRepositorySqueakCommonTestCase
by btc＠openinworld.com March 7, 2014

March 7, 2014

Can someone with a Mac review... https://pharo.fogbugz.com/f/cases/edit/12911/Tests-failing-in-fresh-image-M… Its low priority but also simple - just an update for three tests to deal with difference on Windows platform . cheers -ben

2 1

Re: [Pharo-dev] Support for git in Pharo
by Stephan Eggermont March 7, 2014

March 7, 2014

Max wrote >In my opinion there are other factors, like readability, maintenance etc, that are maybe more important than speed. Iâm not totally convinced. The readability from the outside is limited by having one file per method. Mainstream tooling assumes one file per class. The emails from github to this list are a good example of the usability problems that leads to. I donât want to suggest switching to a larger granularity, as that leads to another set of problems. My point was more if we could mostly avoid the source view, and directly work with the archive. Why is working with single files fastest? Stephan

12 26

Re: [Pharo-dev] What happened with petitmarkdown?
by Stephan Eggermont March 7, 2014

March 7, 2014

ClÃ©ment wrote >Camillo moved all his repo on github and deleted the ones from smalltalkhub. Hmm. I strongly prefer immutability for source code repositories. And a link to older/newer repos. Stephan

1 0

What happened with petitmarkdown?
by Stephan Eggermont March 7, 2014

March 7, 2014

Camillo, While fixing some ci builds, I noticed that at least some of your smalltalkhub repositories are empty (petitmarkdown, ast-interpreter). What happened with the code? ast-interpreter I could find back, but petitmarkdown not. Stephan

3 2

[pharo-project/pharo-core]
by GitHub March 7, 2014

March 7, 2014

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

1 0

[pharo-project/pharo-core] b3065f: 30792
by GitHub March 7, 2014

March 7, 2014

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: b3065f4660c4d171cd5b87f426cad38658f3ff64 https://github.com/pharo-project/pharo-core/commit/b3065f4660c4d171cd5b87f4… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-03-07 (Fri, 07 Mar 2014) Changed paths: A OpalCompiler-Core.package/IRInterpreter.class/instance/instructions/storeInstVar_.st M OpalCompiler-Core.package/IRMethod.class/instance/optimizing/removeEmptyStart.st A OpalCompiler-Core.package/IRPrinter.class/instance/instructions/storeInstVar_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script445.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30792.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30792 13053 Sync image with repo https://pharo.fogbugz.com/f/cases/13053 13002 StoreInstVar: is missing in IRPrinter https://pharo.fogbugz.com/f/cases/13002 13003 Opal cannot optimize twice an IRMethod https://pharo.fogbugz.com/f/cases/13003 http://files.pharo.org/image/30/30792.zip

1 0

[Fuel] Unexpected stream version 19
by roberto.minelli＠usi.ch March 7, 2014

March 7, 2014

Hi, I just run into an error while materializing an object with Fuel. Unexpected stream version 19 should be 193. Do you have any idea why? I noticed that the fuel #stable version is now 1.9.3 instead of 1.9.1 which was the version I used for export. When I loaded Fuel 1.9.1 despite getting some errors, I managed to import my objects. Do you guys have an idea why? Thanks in advance, here is the stack trace. Roby FLMaterializer>>verifyVersionFrom: FLMaterializer>>materializeFrom: FLMaterializer class>>materializationFromFileNamed: in Block: [ :aFileStream | self newDefault materializeFrom: ...etc... StandardFileStream class(FileStream class)>>detectFile:do: in Block: [ anotherBlock value: file ] BlockClosure>>ensure: StandardFileStream class(FileStream class)>>detectFile:do: StandardFileStream class(FileStream class)>>oldFileNamed:do: FLMaterializer class>>materializationFromFileNamed: FLMaterializer class>>materializeFromFileNamed: DFPharoMenu class>>importSessionFromFuelPath: DFPharoMenu class>>importAllSessionsFromFolder in Block: [ :bar | ... BlockClosure>>cull: Job>>run in Block: [ result := block cull: self ] BlockClosure>>on:do: Job>>run in Block: [ ... BlockClosure>>ensure: Job>>run MorphicUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressAt:from:to:during: DFPharoMenu class>>importAllSessionsFromFolder DFPharoMenu class>>menuCommandOn: in Block: [ self importAllSessionsFromFolder ] BlockClosure>>cull: ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: in Block: [ ... BlockClosure>>ensure: CursorWithMask(Cursor)>>showWhile: ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: ToggleMenuItemMorph(MenuItemMorph)>>mouseUp: ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp: MouseButtonEvent>>sentTo: ToggleMenuItemMorph(Morph)>>handleEvent:

3 4