February 2014 - Pharo-dev - lists.pharo.org

Handling of $+ in URLs
by Sven Van Caekenberghe Feb. 16, 2014

Feb. 16, 2014

Hi, Johan Brichau reported an issue a couple of days ago concerning the handling of $+ in ZnUrl (Pharo 3's URL class) and in Seaside's WAUrl. #bleedingEdge of Zinc HTTP Components fixes the issue, as far as I can see. I want to explain the problem and the solution. Before october 24 of last year, ZnUrl used a 'better safe than sorry' safe set when doing percent encoding of unsafe characters. However, the URL spec defines different allowed characters per URL part. This behaviour was then added to Zinc-Resource-Meta-Core, ZnUrl's package. Soon after that a discussion with Jan van de Sandt let to a first small change: since ZnUrl interprets the query part of a URL as key-value pairs, it is necessary to treat $= and $& as unsafe, even though they are not according to the URL spec (which doesn't concern itself with how the query part is interpreted). All that time, $+ kept on being interpreted as a space, independent of the safe set. As Johan reported, this conflicted with $+ being a safe character. Which eventually let to the functional problem of not being able to enter a + in an input field, in Seaside. Why only in Seaside ? Because ZnZincServerAdaptor>>#requestUrlFor: was implemented by printing the interpreted incoming ZnUrl and parsing it again. There, the escaping of $+ disappeared and it became an unintended space. This situation is now fixed by Changes to ZnPercentEncoder: - adding an #decodePlusAsSpace boolean option Changes to ZnResourceMetaUtils: - #decodePercent: no longer decodes plus as space - #decodePercentForQuery: does plus as space decoding - #queryKeyValueSafeSet no longer includes $+ - #parseQueryFrom: not uses #decodePercentForQuery: Added ZnDefaultServerDelegate>>#formTest1: to test simple form submit encoding handling Modify ZnZincServerAdaptor>>#requestUrlFor: to build a WAUrl explicitely from the interpreted parts of the incoming ZnUrl instead of going via printing and parsing Adding new unit tests - ZnUrlTests>>#testPlusHandling - ZnServerTests>>#testFormTest1 I think WAUrl should best be changed as well, but that is not my call. In code, this summarises the implemented behaviour: ZnUrlTests>>#testPlusHandling "While percent decoding, a + is translated as a space only in the context of application/x-www-form-urlencoded get/post requests: http://en.wikipedia.org/wiki/Percent-encoding#The_application.2Fx-www-form-… ZnUrl interprets its query part as key value pairs where this translation is applicable, even though strictly speaking + (and =, &) are plain unreserved characters in the query" "$+ is not special in the path part of the URL and it remains itself" self assert: 'http://localhost/foo+bar' asZnUrl firstPathSegment equals: 'foo+bar'. self assert: 'http://localhost/foo+bar' asZnUrl printString equals: 'http://localhost/foo+bar'. "$+ gets decoded to space in the interpreted query part of the URL, and becomes an encoded space if needed" self assert: ('http://localhost/test?q=foo+bar' asZnUrl queryAt: #q) equals: 'foo bar'. self assert: 'http://localhost/test?q=foo+bar' asZnUrl printString equals: 'http://localhost/test?q=foo%20bar'. "to pass $+ as $+ in a query, it has to be encoded" self assert: 'http://localhost/test?q=foo%2Bbar' asZnUrl printString equals: 'http://localhost/test?q=foo%2Bbar' I hope this is a good and correct solution. In any case, it fixes the functional problem that $+ disappeared in WAUrlEncodingFunctionalTest - which I took over in ZnDefaultServerDelegate>>#formTest1: Thanks Johan for the whole discussion ! Sven

2 1

Fwd: Request
by Guido Chari Feb. 16, 2014

Feb. 16, 2014

Hi guys, IÂ´m doing some experiments with dynamic primitives and files. Actually i am working with the socket and file plugin. (In that order of priority) Does anyone know about an open pharo app that make heavy use of sockets (mainly creating lot) that i can borrowed (install locally) for doing serious experiments? Something with heavy used of files will help too. Thanks, Best, Guido.

5 6

TextModel getSelection and "Debugger run to here"
by Nicolai Hess Feb. 15, 2014

Feb. 15, 2014

Should we tag issue 12144 for Pharo3? At the moment, this is only an isseu for the debugger, but is is related to spec. We can expect more apps/developer suffer from this in the future and I dont want to see, everyone invents its own workaround. I made to slices, with the first the textmodel only recognizes selections done by the mouse, with the second, selection by keyboard works too. But than you can only select text from left to right :(

2 2

Monticello strangeness
by Ben Coman Feb. 15, 2014

Feb. 15, 2014

Something very strange going on for me with Monticello in build 30763. The Packages I make changes in are not showing up "starred" at the top, "other" packages are. When I select one of these "other" packages and the Pharo30/main repository and click <Changes>, then it reports "No changes". Further, normally when it reports "No changes" the "star" would disappear from that package and it would sort back into its alphabetical position, but that doesn't happen. This happened in three fresh images of 30763, but I wasn't paying proper attention. Into the fresh image I just loaded a slice that I am testing and make a few minor code changes. All was good in 30753. I am trying to isolate this further. cheers -ben

2 2

[GSoC ideas] Pharo - Animation Framework for Roassal
by Alexandre Bergel Feb. 14, 2014

Feb. 14, 2014

Roassal is an visualization engine for Pharo, Visualworks and Amber. Thanks to the Viva framework, Roassal offers some flexible way to animate graphical elements. Beside having a lot of fun, the idea of this project is to have animations such as: - http://www.nytimes.com/interactive/2013/09/25/sports/americas-cup-course.ht… - http://www.jasondavies.com/wordtree/ - http://www.washingtonpost.com/wp-srv/special/politics/state-vs-federal-exch… - many more can be found on http://d3js.org Skill: Easy/Intermediate Mentor: Alexandre Bergel - alexandre.bergel(a)me.com Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

Bugfix to '/foo:bar' asUrl
by Sven Van Caekenberghe Feb. 14, 2014

Feb. 14, 2014

Hi Kris, I fixed the problem that you reported. It was a regression caused when adding support for parsing mailto: URLs which don't have a // in them. There is now a new explicit test for parsing '/foo:bar' asZnUrl. Thanks again for reporting this problem! Sven In #bleedingEdge: === Name: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.31 Author: SvenVanCaekenberghe Time: 13 February 2014, 10:41:58.821615 pm UUID: dee515f8-aff3-4930-8b90-da2b01e1ee33 Ancestors: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.30 Patch ZnUrl>>#parseFrom:defaultScheme: to parse schemes more carefully so that a colon in a path does not mess things up - see also the regression test ZnUrlTests>>#testNoSchemeColonInPath parsing /foo:bar (thanks Kris Gijbels) === Name: Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.19 Author: SvenVanCaekenberghe Time: 13 February 2014, 10:42:42.63619 pm UUID: 264c99fe-52ef-4f4a-8a25-fc870f34cfb2 Ancestors: Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.18 Patch ZnUrl>>#parseFrom:defaultScheme: to parse schemes more carefully so that a colon in a path does not mess things up - see also the regression test ZnUrlTests>>#testNoSchemeColonInPath parsing /foo:bar (thanks Kris Gijbels) ===

2 17

[pharo-project/pharo-core]
by GitHub Feb. 14, 2014

Feb. 14, 2014

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

1 0

[pharo-project/pharo-core] c0d859: 30763
by GitHub Feb. 14, 2014

Feb. 14, 2014

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: c0d859fba82ca44b444d0f920aa91781636609e6 https://github.com/pharo-project/pharo-core/commit/c0d859fba82ca44b444d0f92… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-02-14 (Fri, 14 Feb 2014) Changed paths: M FileSystem-Core.package/Path.class/class/private/absoluteWindowsPathRegex.st A GroupManager.package/DynamicGroup.class/instance/protocol/addClass_.st A Kernel.package/BlockClosure.class/instance/accessing/numLocalTemps.st M Kernel.package/BlockClosure.class/instance/accessing/numTemps.st M OpalCompiler-Core.package/extension/BlockClosure/instance/sourceNode.st A OpalCompiler-Core.package/extension/MethodContext/instance/isBlockReturn_.st A OpalCompiler-Core.package/extension/MethodContext/instance/isPushLiteralNil_.st A OpalCompiler-Core.package/extension/MethodContext/instance/isPushTemp_.st A OpalCompiler-Core.package/extension/MethodContext/instance/neighborPCWithCorrectMapping.st M OpalCompiler-Core.package/extension/MethodContext/instance/sourceNode.st A OpalCompiler-Core.package/extension/RBBlockNode/instance/enclosingMethodOrBlockNode.st A OpalCompiler-Core.package/extension/RBProgramNode/instance/enclosingMethodOrBlockNode.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script416.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30763.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30763 12508 Really strange error with Komitter on windows https://pharo.fogbugz.com/f/cases/12508 12875 Still some problems with #sourceNode https://pharo.fogbugz.com/f/cases/12875 12884 Cannot add a class to a dynamic group with drag and drop https://pharo.fogbugz.com/f/cases/12884 http://files.pharo.org/image/30/30763.zip

1 0

Adapting CMakeVMMaker to build BochsIA32Plugin
by Stefan Marr Feb. 14, 2014

Feb. 14, 2014

Hi: I am slowly getting acquainted with CMake and the CMakeVMMaker infrastructure. In order to build the BochsIA32Plugin for the Cog simulator, I need to pass a number of build flags. Would be great if someone could tell me how to realize the following things: 1. remove -std=gnu99 for only this plugin BochsIA32Plugin is written in C++ and Clang doesnât support the `-std=gnu99` switch in that case. 2. add header include paths The plugin needs the following two includes to access Bochsâ headers: -I${root}/processors/IA32/bochs/ -I${root}/processors/IA32/bochs/instrument/stubs/ 3. the final binary needs the following linker flags -lcpu -ldisasm -lfpu -L${root}/processors/IA32/macbochs/disasm/ -L${root}/processors/IA32/macbochs/cpu/ -L${root}/processors/IA32/macbochs/fpu/ In addition to that I would also need to add a script to build the bochs library before linking the binary. Any hints how to do that are very appreciate. Thanks Stefan -- Stefan Marr INRIA Lille - Nord Europe http://stefan-marr.de/research/

1 0

[Pharo3][Issue Tracker] Open issued down to 17
by Marcus Denker Feb. 14, 2014

Feb. 14, 2014

Hi, Issues tagged âmust fixâ or higher for Pharo3 is now at 17: https://pharo.fogbugz.com/f/filters/64/3-0-TODO Pls check if something is missing, or wrong. Marcus

1 1