May 2015 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 7554e4: 50027
by GitHub May 2, 2015

May 2, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 7554e430b71ac42468fa98995dd45df7f831237f https://github.com/pharo-project/pharo-core/commit/7554e430b71ac42468fa9899… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-02 (Sat, 02 May 2015) Changed paths: M ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/symbolic versions/stable_.st A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version1213_.st M ConfigurationOfZincHTTPComponents.package/ConfigurationOfZincHTTPComponents.class/instance/accessing/stable_.st A ConfigurationOfZincHTTPComponents.package/ConfigurationOfZincHTTPComponents.class/instance/versions/version264_.st M Rubric.package/RubShoutStylerDecorator.class/README.md M Rubric.package/RubShoutStylerDecorator.class/definition.st M Rubric.package/RubShoutStylerDecorator.class/instance/accessing/next_.st M Rubric.package/RubShoutStylerDecorator.class/instance/private/aboutToBeUnplugged.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script635.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script636.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50026.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50027.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Zinc-HTTP.package/ZnClient.class/instance/private protocol/prepareRedirect.st M Zinc-HTTP.package/ZnCookie.class/instance/initialize-release/fromString_.st M Zinc-HTTP.package/ZnCredential.class/class/accessing/findRealmFor_.st M Zinc-HTTP.package/ZnDigestAuthenticator.class/class/accessing/parseAuthRequest_.st M Zinc-HTTP.package/ZnLogEvent.class/class/convenience/stopLoggingToTranscript.st A Zinc-Resource-Meta-Core.package/ZnMaximumNumberOfDictionaryEntries.class/README.md A Zinc-Resource-Meta-Core.package/ZnMaximumNumberOfDictionaryEntries.class/definition.st M Zinc-Resource-Meta-Core.package/ZnMimeType.class/class/instance creation/main_sub_.st M Zinc-Resource-Meta-Core.package/ZnMimeType.class/class/instance creation/main_sub_parameters_.st A Zinc-Resource-Meta-Core.package/ZnMultiValueDictionary.class/class/accessing/defaultLimit.st R Zinc-Resource-Meta-Core.package/ZnMultiValueDictionary.class/instance/accessing/defaultLimit.st M Zinc-Resource-Meta-Core.package/ZnMultiValueDictionary.class/instance/initialize-release/initialize_.st M Zinc-Resource-Meta-Core.package/ZnUrl.class/instance/accessing-path/closePath.st M Zinc-Resource-Meta-Core.package/ZnUrl.class/instance/comparing/=.st M Zinc-Resource-Meta-Core.package/ZnUrl.class/instance/comparing/equals_.st A Zinc-Resource-Meta-Tests.package/ZnMultiValueDictionaryTests.class/instance/testing/testDynamicLimit.st A Zinc-Resource-Meta-Tests.package/ZnUrlTests.class/instance/testing/testQueryRemoveAll.st M Zinc-Tests.package/ZnClientTests.class/instance/testing/testLogging.st A Zinc-Tests.package/ZnClientTests.class/instance/testing/testRelativeRedirect307.st Log Message: ----------- 50027 15457 Update Zinc to handle some deprecations in Pharo 5 https://pharo.fogbugz.com/f/cases/15457 15463 Rubric turns text to transparent when styling https://pharo.fogbugz.com/f/cases/15463 http://files.pharo.org/image/50/50027.zip

1 0

Fwd: Download problem: certificate
by jannik laval May 2, 2015

May 2, 2015

Hi guys, Does someone have a solution for this problem ? Cheers, Jannik ---------- Forwarded message ---------- From: Markus Schlager <m.slg(a)gmx.de> Date: 2015-05-02 14:32 GMT+02:00 Subject: Re: Download problem: certificate To: jannik laval <jannik.laval(a)gmail.com> Dear Jannik, When visiting https://ci.inria.fr/ firefox for example is complaining (on arch linux as well as on windows 7) that the security certificate of ci.inria.fr is not valid: error code: sec_error_unknown_issuer This seems to be a problem of missing intermediate certificates on the server of ci.inria.fr. You get this hint when checking ci.inria.fr on http://www.networking4all.com/en/support/tools/site+check/ which leads to http://www.networking4all.com/en/support/tools/site+check/report/?fqdn=ci.i… Problem description also at https://support.mozilla.org/de/questions/773136 Probably you should contact the server-admins. They might want to check the installation of their TERENA-certificate (c.f. https://www.terena.org/activities/tcs/repository/) Greetings Markus -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info http://car.mines-douai.fr/

2 1

Re: [Pharo-dev] [Pharo-users] Fuel version
by Mariano Martinez Peck May 2, 2015

May 2, 2015

Johannes, The simples approach is that you materialize your object in 3.0, then load the same version as fuel from pharo 4.0 and then serialize again in 3.0. After that, you can materialize in 4.0. The other alternative is that in 4.0 you load older version of Fuel (the one in 3.0), then import, the expert, then load new fuel again. I have been doing this since Pharo 1.4 until 4.0 since my client's app also uses Fuel. And the process was always quite simple and only once per release. Migration is something we miss in Fuel..and even if we have promised to keep format unchanged, sometimes the evolution of Pharo itself (not the internal Fuel format representation) makes the format to be broken from one version to the other. So until we have a better automagic migration tool, the above trick should work. Also...see this link: http://rmod.inria.fr/web/software/Fuel/Version1.9/Documentation/FormatMigra… Btw...here is the scrip I used to migrate from 1.8 to 1.9... this is just an EXAMPLE of how you can do it..but do not copy it becuase it uses old version of the code repositories, etc... | oldVersion newVersion fileNames objectsByFileName materializerClass | oldVersion := '1.8'. newVersion := '1.9'. fileNames := #( '/Users/mariano/XXX/aaaaDB.fdb' '/Users/mariano/XXX/bbbbDB.fdb' '/Users/mariano/XXX/ccccDB.fdb' '/Users/mariano/XXX/ddddDB.fdb' '/Users/mariano/XXX/eeeeDB.fdb' '/Users/mariano/XXX/ffffDB.fdb' ). objectsByFileName := Dictionary new. materializerClass := Smalltalk at: #FLMaterializer. fileNames do: [ :fileName | objectsByFileName at: fileName put: (materializerClass materializeFromFileNamed: fileName). FileDirectory default copyFileNamed: fileName toFileNamed: fileName, '-', oldVersion asString ]. Gofer it squeaksource3: 'Fuel'; package: 'ConfigurationOfFuel'; load. (ConfigurationOfFuel project version: newVersion) load. objectsByFileName keysAndValuesDo: [ :fileName :objects | FLSerializer serialize: objects toFileNamed: fileName. FileDirectory default copyFileNamed: fileName toFileNamed: fileName, '-', newVersion asString ]. On Thu, Apr 30, 2015 at 9:19 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 30.04.2015 um 14:08 schrieb Johannes Rasche Kreuzberg < > Johannes(a)Rasche-Kreuzberg.de>: > > Hi folks, > > I'm just migrating to Pharo 4.0 > > On materialization of objects serialized under Pharo 3 > an error was raised: different versions numbers ( 194 required ). > > Where does version 194 come from ? > Monticello from Pharo 3 offers 193 > > Johannes > > You need to add the repository of Fuel, load the ConfigurationOf from > there and you can upgrade to 1.9.4 > > The repository to add is > > http://smalltalkhub.com/mc/Pharo/Fuel/main > > Norbert > > -- Mariano http://marianopeck.wordpress.com

4 4

[ANN]: Tiny Dev Tools for SimplePersistence and STON
by Sean P. DeNigris May 2, 2015

May 2, 2015

I often find myself writing the same boilerplate over and over for my basic persistence needs. My usual pattern is to serialize/materialize a class-side instance variable with accessors of the same name. Some time ago, I added the following to SimplePersistence (IIRC it gets loaded by default): aClass persist: #fieldName which adds the necessary code automatically. Since I've been playing with STON a bit, I created the same in STON-Tools and uploaded to http://smalltalkhub.com/#!/~SeanDeNigris/SeansOutbox. There is even a test ;) Enjoy... ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Tiny-Dev-Tools-for-SimplePersistence-and-STON-tp4… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 3

Are these changes good enough
by Sergio Fedi May 2, 2015

May 2, 2015

Hi, I'm new to the Pharo community and recently installed Pharo 4.0. While using it I've found that the TestRunner didn't have coverage and after investigating a little I've found that is was almost there and I made it work. Is this change something I could submit as a Fix? (as per in http://pharo.org/contribute-propose-fix)

7 20

sometimes Shout changes the selection during styling
by Andrei Chis May 2, 2015

May 2, 2015

Hi, In the glamour debugger that we use in moose we are now having the following problem: - the selection of a PluggableTextMorph is, quite randomly , changed during styling. If I revert the fix for issue 15240 <https://pharo.fogbugz.com/f/cases/15240> then it works ok. Also if I change in SHTextStyler>>#styleInBackgroundProcess: from sem waitTimeoutSeconds: 5. view ifNotNil: [ view stylerStyledInBackground: text ] to: (sem waitTimeoutSeconds: 5) ifFalse: [ view ifNotNil: [ view stylerStyledInBackground: text ] ] it works ok. In the second snippet we only do the styling if the styler completed. If I look at the senders of styleInBackgroundProcess: there is another strange issue. First PluggableTextMorph>>#setText: calls either style: or styleInBackgroundProcess:, depending in the size of the text. Then, PluggableTextMorph>>#setText: calls PluggableTextMorph>>#setTextBasic:, which calls PluggableTextMorph>>#hasUnacceptedEdits: which in turn calls again styleInBackgroundProcess:. So when you set the text if the size of the text is small Shout will try to style the text with and without a background process. If you call hasUnacceptedEdits: manually when initializing the morph then three processes will be started for doing the styling. Removing the calls to styleInBackgroundProcess: from PluggableTextMorph>>#hasUnacceptedEdits: and PluggableTextMorph>>#basicHasUnacceptedEdits:. also solves the problem with the changing selection. Cheers, Andrei

3 7

Breakpoint of variable write
by Yuriy Tymchuk May 2, 2015

May 2, 2015

Hi, is it possible to do a halt whenever some instance variable is written? Because this week Iâve spent a lot of time debugging because something was setting some strange values to variables and it was hard to track that down. Uko

5 5

can or: be redefined?
by stepharo May 1, 2015

May 1, 2015

In nautilus I get an error MNU: RBBlockNode>>method When I select several groups and select merge mergeGroups: aCollection aCollection ifNotEmpty: [:groups || group | group := groups reduce: [:a :b | a or: [b]]. ^^^^^^^^^^^^ a is a dynamicClassGroup and its superclass defines or: groups do: [:gp | gp removable ifTrue: [self groupsManager removeAGroupSilently: gp]]. ^ group]. ^ nil RBBlockNode(Object)>>doesNotUnderstand: #method RBBlockNode>>sourceNodeForPC: DynamicClassGroup(Object)>>mustBeBooleanInMagic: DynamicClassGroup(Object)>>mustBeBoolean [ :a :b | a or: [ b ] ] in [ :groups | | group | group := groups reduce: [ :a :b | a or: [ b ] ]. groups do: [ :gp | gp removable ifTrue: [ self groupsManager removeAGroupSilently: gp ] ]. ^ group ] in PackageTreeNautilusUI(AbstractTool)>>mergeGroups: in Block: [ :a :b | a or: [ b ] ] [ :index | arguments replaceFrom: 2 to: arguments size with: self startingAt: index; at: 1 put: (aBlock valueWithArguments: arguments) ] in Array(SequenceableCollection)>>reduceLeft: in Block: [ :index | ... SmallInteger(Number)>>to:by:do: Array(SequenceableCollection)>>reduceLeft: Array(SequenceableCollection)>>reduce: [ :groups | | group | group := groups reduce: [ :a :b | a or: [ b ] ]. groups do: [ :gp | gp removable ifTrue: [ self groupsManager removeAGroupSilently: gp ] ]. ^ group ] in PackageTreeNautilusUI(AbstractTool)>>mergeGroups: in Block: [ :groups | ... BlockClosure>>cull: Array(Collection)>>ifNotEmpty: PackageTreeNautilusUI(AbstractTool)>>mergeGroups: PackageTreeNautilusUI(AbstractNautilusUI)>>mergeGroups [ target mergeGroups ] in AbstractNautilusUI class>>groupsMenu: in Block: [ target mergeGroups ] BlockClosure>>cull: [ | selArgCount | "show cursor in case item opens a new MVC window" (selArgCount := selector numArgs) = 0 ifTrue: [ target perform: selector ] ifFalse: [ selArgCount = arguments size ifTrue: [ target perform: selector withArguments: arguments ] ifFalse: [ target perform: selector withArguments: (arguments copyWith: evt) ] ]. self changed ] in ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: in Block: [ ... BlockClosure>>ensure: CursorWithMask(Cursor)>>showWhile: ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: ToggleMenuItemMorph(MenuItemMorph)>>mouseUp: ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp: MouseButtonEvent>>sentTo: ToggleMenuItemMorph(Morph)>>handleEvent: MorphicEventDispatcher>>dispatchDefault:with: MorphicEventDispatcher>>handleMouseUp: MouseButtonEvent>>sentTo: [ ^ anEvent sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: in Block: [ ^ anEvent sentTo: self ] BlockClosure>>ensure: MorphicEventDispatcher>>dispatchEvent:with:

6 22

Re: [Pharo-dev] can or: be redefined?
by Marcus Denker May 1, 2015

May 1, 2015

> On 01 May 2015, at 11:49, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 01 May 2015, at 11:46, stepharo <stepharo(a)free.fr> wrote: >> >> We should at least have a rules stating "pay attentino you use an optimised selector". Im not sure what should be form of the warning but we should make progress >> > > why? > >> I see two cases >> - the dev uses a non optimized version and the warning tell him that it would be better to use the optimised >> ifNil....of whatever case >> >> - when defining a method with such selector: >> warn them because we should avoid them. > > I somehow feel that I did not manage to explain the whole thing in a way that it was understandable. Can we discuss that on the whiteboard next week? Marcus

2 1

[ANN] Screencast on Versionner (Part 2)
by Esteban Lorenzano May 1, 2015

May 1, 2015

Hi again, Now I made a small video on how to use Versionner to help you manage your releases and commits. https://youtu.be/cFRJDuWL-Q0 <https://youtu.be/cFRJDuWL-Q0> This is new stuff, so you will need latest Pharo 5 to use it, alternatively you can install latest Versionner into Pharo 4 (I donât know how it will work on Pharo 3, youâll probably need to load Glamour as well others). In Pharo 4, you can install it executing: Gofer it smalltalkhubUser: 'PharoExtras' project: 'Versionner'; configuration; loadVersion: '2.12.2'. cheers, Esteban

7 8