- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub May 3, 2015

May 3, 2015

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

1 0

[pharo-project/pharo-core] d31f21: 50028
by GitHub May 3, 2015

May 3, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d31f210a4de628dd26f5a20200ea1a332bb988d6 https://github.com/pharo-project/pharo-core/commit/d31f210a4de628dd26f5a202… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-03 (Sun, 03 May 2015) Changed paths: M Collections-Abstract.package/SequenceableCollection.class/instance/private/combinationsAt_in_after_do_.st A GroupManager.package/DynamicGroup.class/instance/accessing/merge_.st R GroupManager.package/DynamicGroup.class/instance/accessing/or_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/accessing/groupsAreVisible.st M Network-Kernel.package/Socket.class/instance/initialization/initialize_.st M Network-Kernel.package/Socket.class/instance/initialize-destroy/acceptFrom_.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/accessing colors/backgroundColor.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script636.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script637.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50027.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50028.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-Base.package/AbstractTool.class/instance/group/mergeGroups_.st Log Message: ----------- 50028 15466 combinationsAt: jj in: aCollection after: nn do: aBlock bogus comment https://pharo.fogbugz.com/f/cases/15466 15464 Merging groups raised an DNU https://pharo.fogbugz.com/f/cases/15464 5465 Prevent accidental semaphore leaks when using Socket acceptFrom https://pharo.fogbugz.com/f/cases/5465 15467 better background color for Dark Theme https://pharo.fogbugz.com/f/cases/15467 http://files.pharo.org/image/50/50028.zip

1 0

TextMorph right-click?
by Stephan Eggermont May 2, 2015

May 2, 2015

How am I supposed to use TextMorph? It pops a debugger on right-click when doing a TextMorph new contents: 'Text'; openInWorld TextMorph(Object)>>doesNotUnderstand: #editView. Stephan

3 6

Re: [Pharo-dev] [Pharo-users] ZnEasy / UTF-8
by Sven Van Caekenberghe May 2, 2015

May 2, 2015

Hi Volkert, Thanks for the test case, it helped me figure out what the problem was. Basically, what Norbert said was 100% correct: the server code (Teapot) should have specified the charset or encoding of the mime-type it was using (so application/json;charset=utf-8 instead of just application/json). However, I thought I had changed the default to be utf-8, so I was surprised it was not picked up. It turned out utf-8 was the default for reading/writing http messages and their entities, but not so when manually constructing instances (like Teapot did). In code, json := '{''bank'':''RÃ©gion GenÃ¨ve RhÃ´ne''}'. entity := ZnEntity with: json type: 'application/json'. response := ZnResponse ok: entity. response encoder. did not return a ZnUTF8Encoder but a ZnNullEncoder. I changed that now. === Name: Zinc-HTTP-SvenVanCaekenberghe.428 Author: SvenVanCaekenberghe Time: 2 May 2015, 7:09:55.832482 pm UUID: 6376bd91-2a95-4265-bfff-e3c6626aee79 Ancestors: Zinc-HTTP-SvenVanCaekenberghe.427 Change ZnStringEntity>>#initializeEncoder to default to ZnUTF8Encoder unless ZnDefaultCharacterEncoder is set Change ZnEntityReader>>#readEntity to no longer use #withDefaultUtf8Decoder: (and remove it) Change ZnEntityWriter>>#writeEntity: to no longer use #withDefaultUtf8Encoder: (and remove it) Add ZnResponseTests>>#testDefaultUTF8Encoding === Name: Zinc-Tests-SvenVanCaekenberghe.226 Author: SvenVanCaekenberghe Time: 2 May 2015, 7:10:12.331593 pm UUID: 9010fbd6-bf9d-400e-b463-cb73920b79f6 Ancestors: Zinc-Tests-SvenVanCaekenberghe.225 Change ZnStringEntity>>#initializeEncoder to default to ZnUTF8Encoder unless ZnDefaultCharacterEncoder is set Change ZnEntityReader>>#readEntity to no longer use #withDefaultUtf8Decoder: (and remove it) Change ZnEntityWriter>>#writeEntity: to no longer use #withDefaultUtf8Encoder: (and remove it) Add ZnResponseTests>>#testDefaultUTF8Encoding === for now, in #bleedingEdge of Zinc HTTP Components. HTH, Sven > On 01 May 2015, at 15:53, volkert <volkert(a)komponentenwerkstatt.de> wrote: > > Here a stripped down example > > d := { 'bank' -> 'RÃ©gion GenÃ¨ve RhÃ´ne'. } asDictionary. > > teapot := Teapot configure: { > #defaultOutput -> #json. > #port -> 8081. > #debugMode -> true > }. > > teapot > GET: '/api/d' -> d; > exception: KeyNotFound -> (TeaResponse notFound body: 'asd'); > start. > > (ZnEasy get: 'http://localhost:8081/api/d') entity string. > > Pharo 4.0 / Teapot > > BW, > Volkert > > > > Am 01.05.2015 um 15:35 schrieb Sven Van Caekenberghe: >>> On 01 May 2015, at 15:15, volkert <volkert(a)komponentenwerkstatt.de> wrote: >>> >>> I thought UTF-8 is the default encoding in case JSON Documents, and so for the Content-Type: application/json. >>> >>> I added "setCharSetUTF8" this Teapot-Output and all works fine now. :-) >> Fine, but I still think this is strange, it should work by default too. >> But to understand what went wrong, I need an example (server+client) that I can run. >> >>> Danke, >>> Volkert >>> >>> Am 01.05.2015 um 14:20 schrieb Norbert Hartl: >>>> You need to look at the headers of the request. I would assume the sender sets an Content-Type: application/json without charset. In that moment it is uncertain what has to be done because the server needs to assume what charset it might be and this tasks seldomly works out good. >>>> In order to make it work set a content type of your entity this way >>>> >>>> ZnMimeType applicationJson setCharSetUTF8 >>>> >>>> Now you send a Content-Type of application/json;charset=utf-8 and the server knows which character decoder to use. That should be it. So please always assign a char set to your sending data to make it more reliable what happens on the other end. >>>> >>>> hope this helps, >>>> >>>> Norbert >>>>> Am 01.05.2015 um 14:13 schrieb volkert <volkert(a)komponentenwerkstatt.de>: >>>>> >>>>> I tried ZnClient new get: 'http://<removed>/api/atm/801813'; yourself and got. >>>>> >>>>> <fdchdjab.png> >>>>> >>>>> This is the Doc i see in Firefox. >>>>> >>>>> <fceagiec.png> >>>>> >>>>> The JSON is served with ZnServer / Teapot. ;-) >>>>> >>>>> Volkert >>>>> >>>>> >>>>> Am 01.05.2015 um 12:21 schrieb Sven Van Caekenberghe: >>>>>> Hi Volkert, >>>>>> >>>>>> Tip 1: use ZnClient and inspect the response in detail, more specifically to see whether the response content type specifies the encoding. >>>>>> >>>>>> ZnClient new get: ' >>>>>> http:// >>>>>> <removed>/api/atm/801813'; yourself. >>>>>> >>>>>> Tip 2: you could try to force override the default encoding using ZnDefaultCharacterEncoder (see the class comment). >>>>>> >>>>>> But recent Zn code defaults to UTF8 (see #withDefaultUTF8Decoding: and #withDefaultUTF8Encoding:). So I am curious to see the response headers. >>>>>> >>>>>> HTH, >>>>>> >>>>>> Sven >>>>>> >>>>>> >>>>>>> On 01 May 2015, at 11:54, volkert <volkert(a)komponentenwerkstatt.de> >>>>>>> wrote: >>>>>>> >>>>>>> Dear all, >>>>>>> >>>>>>> i am trying to get a JSON Document with ZnEasy. The Document is UTF-8 encoded. >>>>>>> >>>>>>> (ZnEasy get: ' >>>>>>> http:// >>>>>>> <removed>/api/atm/801813') entity string. >>>>>>> <gccacjeh.png> >>>>>>> >>>>>>> Any hints? >>>>>>> >>>>>>> Volkert >>>>>>> >>>>>>> >>>>>>> >> > >

1 0

[pharo-project/pharo-core]
by GitHub May 2, 2015

May 2, 2015

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

1 0

[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