December 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Web site - Hudson link

by Ben Coman

Is the link from http://www.pharo-project.org/community to the Hudson server wrong? or is the server just down?

Dec. 14, 2011

Re: [Pharo-project] Pharo 1.3 vs 1.2.1 some results for ConfigurationOfODBC - success

by Ben Coman

Dec. 14, 2011

Re: [Pharo-project] Old smalltalker is slightly lost

by Ben Coman

Depending on your needs you might like http://squeak.preeminent.org/tut2007/html/index.html KasperOsterbye wrote: > 15 years ago I did a lot in Smalltalk, and have done some recreational meta > programming along the way. However, I now wanted to do something where I was > in need of drawing a diagram with x and y axes on what I presume might be > called a Canvas. > > I lack a simple tutorial to get me started. I have looked at many, but they > seem to presume I want to draw on the world "openInWorld". I should like not > to scatter my world with line fragments and points, but keep it inside a > "normal" window with borders, a background color (i.e. not a see through > window). > I have gone dead in two approaches. > > First attempt is to use a SystemWindow, and then draw on the canvas I > presume is there somewhere. I have just not been able to figure out how to > find the canvas of that SystemWindow, nor what method presumeable does the > painting. > > Second attempt is to use a SystemWindow, and then add (addMorph:) line and > circle morphs for my diagram. But it seems something is missing in my > understanding there as well. > > While it is fun that I can open circles and other stuff in "world", it is > not what I need. > > Small hits or direct solutions more than welcome. > > -- Kasper > > -- > View this message in context: http://forum.world.st/Old-smalltalker-is-slightly-lost-tp4191137p4191137.ht… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > >

Dec. 14, 2011

Re: [Pharo-project] Startup Preferences

by Ben Coman

Steve Taylor wrote: > On 14/12/11 11:24, Sean P. DeNigris wrote: >> +1 for "imageFolder/.pharo followed by ~/.pharo (although is ~ >> meaningful on >> Windows?) > There's something like C:/Users/<current_user_name> - though I think > that might be a different location between Vista and XP and so on. > There's also the added complication that programs can be installed for > the current user or 'all users' - I don't know what the implications > of that are. > Steve From [1], for Windows I suggest: %ALLUSERSPROFILE% \pharo\startup.st - for default system wide settings %APPDATA%\pharo\startup.st - for personal settings [1] http://www.axleration.com/default-environment-variable-values-of-windows-xp…

Dec. 14, 2011

Re: [Pharo-project] Startup Preferences

by Sean P. DeNigris

Damien Cassou wrote > > This ~/.config directory is a freedesktop standard: "If > ... > But everyone seems to agree that ~/.pharo is better so I would not > push ~/.config further. > I have no preference for the extension, only the location. Since we're making this up, why not use the most standard; although I thought the objection is that there may be more than config info there? Now that I think about it. I do not understand the motivation for this file in general. Will someone give a use case? Why not just do whatever it is in the start up list? -- View this message in context: http://forum.world.st/Startup-Preferences-tp4129591p4195476.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 14, 2011

Re: [Pharo-project] Startup Preferences

by Damien Cassou

On Tue, Dec 13, 2011 at 3:26 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > I would look just on ~/.pharo (the "config" name is bad: too generic) This ~/.config directory is a freedesktop standard: "If $XDG_CONFIG_HOME is either not set or empty, a default equal to $HOME/.config should be used. " (http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html) But everyone seems to agree that ~/.pharo is better so I would not push ~/.config further. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Dec. 14, 2011

[Pharo-project] code retreat @ lille

by StÃ©phane Ducasse

Hi guys we got contacted to participate to a code retreat @ lille. I will attend it and I register to it So I imagine, that we can have fun with other people and showing them pharo and hacking. http://coderetreatlille2.eventbrite.com/ Stef

Dec. 14, 2011

Re: [Pharo-project] Latest Zinc in Pharo 1.3 with MetacelloConfiguration

by Sven Van Caekenberghe

FranÃ§ois, On 12 Dec 2011, at 21:46, Francois Stephany wrote: > Dag Sven, > >> It would be great if you could update both to the latest versions of all packages. > > I've updated the configuration to all the latest packages except for Gemstone. > > Wehn Running the 190 tests I get one failure: > > ZnClientTests>>testIfFailNonExistingHost > > > Let me now if I did something wrong ;) Please do also copy it to the main http://www.squeaksource.com/ZincHTTPComponents repository. I know having 2 is confusing, but that is how most projects seem to do it. I don't understand why you would try to get Zinc-Patch-HTTPSocket from this other repository (they are identical BTW). The failing test puzzle me, can you maybe debug it and tell me what you see ? Maybe we should also let Paul DeBruicker know what you did, if he's not reading this. Thanks again, Sven

Dec. 14, 2011

Re: [Pharo-project] ZnUrl vs furl

by StÃ©phane Ducasse

On Dec 14, 2011, at 2:09 PM, Sven Van Caekenberghe wrote: > > On 14 Dec 2011, at 14:00, Sven Van Caekenberghe wrote: > >> Now it reads like this: > > Actually with the correct quotes (I did a ZnUrl comment Print It ;-) > BTW, I already did add the examples as unit tests, executable code is even better than dead comments. Yes I do not despair to have pragma <forDoc> in unit tests for that. Stef > > > I am ZnUrl, an implementation of an interpreted HTTP(S) URL/URI. > Contrary to other implementations, this one is specific for HTTP(S). > > I consist of the following parts: > - scheme - either #http, #https or nil > - host - hostname string or nil > - port - port integer or nil > - segments - collection of path segments, ends with #/ for directories > - query - query dictionary or nil > - fragment - fragment string or nil > > The syntax of my external representation informally looks like this > > scheme://host:port/segments?query#fragment > > I am most often created by parsing my external representation using either my #fromString: class method or by sending the #asZnUrl convenience method to a String. Using #asZnUrl helps in accepting both Strings and ZnUrls arguments. > > ZnUrl fromString: 'http://www.google.com/search?q=Smalltalk'. > > I can also be constucted programmatically. > > ZnUrl new > scheme: #https; > host: 'encrypted.google.com'; > addPathSegment: 'search'; > queryAt: 'q' put: 'Smalltalk'; > yourself. > > My components can be manipulated destructively. Here is an example: > > ('http://www.google.com/?one=1&two=2' asZnUrl) > queryAt: 'three' put: '3'; > queryRemoveKey: 'one'; > yourself. > > Some characters of parts of a URL are illegal because they would interfere with the syntax and further processing and thus have to be encoded. The methods in accessing protocols do not do any encoding, those in parsing and printing do. Here is an example: > > ('http://www.google.com' asZnUrl) > addPathSegment: 'some encoding here'; > queryAt: 'and some encoding' put: 'here, too'; > yourself > > My parser is somewhat forgiving and accepts some unencoded URLs as well, like most browsers would. > > 'http://www.example.com:8888/a path?q=a, b, c' asZnUrl. > > I can parse in the context of a default scheme, like a browser would do. > > ZnUrl fromString: 'www.example.com' defaultScheme: #http > > Given a scheme, I know its default port, try #portOrDefault. > > A path defaults to what is commonly referred to as slash, test with #isSlash. Paths are most often (but don't have to be) interpreted as filesystem paths. To support this, I have #isFile and #isDirectory tests and #file and #directory accessors. > > I have some support to handle one URL in the context of another one, this is also known as a relative URL in the context of an absolute URL. Refer to #isAbsolute, #isRelative and #inContextOf: > > '/folder/file.txt' asZnUrl inContextOf: ('http://fileserver.example.net:4400' asZnUrl). > > Sometimes, the combination of my host and port are referred to as authority, see #authority. > > URL/URI/URN (Uniform/Universal Resource Locator/Identifier/Name) are closely related and can be and are used as synonyms is many contexts. Refer to http://en.wikipedia.org/wiki/Url for more information. > > Part of Zinc HTTP Components.

Dec. 14, 2011

Re: [Pharo-project] ZnUrl vs furl

by StÃ©phane Ducasse

On Dec 14, 2011, at 2:00 PM, Sven Van Caekenberghe wrote: > > On 13 Dec 2011, at 22:42, StÃ©phane Ducasse wrote: > >> Excellent now can you open an issue and provide add these examples in the ZnUrl class comment? > > You are a slave driver ;-) Yes I like that. whipping the crack :) Stef > > ==================== Summary ==================== > > Name: Zinc-HTTP-SvenVanCaekenberghe.229 > Author: SvenVanCaekenberghe > Time: 14 December 2011, 1:45:28 pm > UUID: b239edd4-c432-4139-a71a-d27618beef91 > Ancestors: Zinc-HTTP-SvenVanCaekenberghe.228 > > expanded the ZnUrl class comment > > ================================================= > > > Now it reads like this: > > > I am ZnUrl, an implementation of an interpreted HTTP(S) URL/URI. > Contrary to other implementations, this one is specific for HTTP(S). > > I consist of the following parts: > - scheme - either #http, #https or nil > - host - hostname string or nil > - port - port integer or nil > - segments - collection of path segments, ends with #/ for directories > - query - query dictionary or nil > - fragment - fragment string or nil > > The syntax of my external representation informally looks like this > > scheme://host:port/segments?query#fragment > > I am most often created by parsing my external representation using either my #fromString: class method or by sending the #asZnUrl convenience method to a String. Using #asZnUrl helps in accepting both Strings and ZnUrls arguments. > > ZnUrl fromString: ''http://www.google.com/search?q=Smalltalk''. > > I can also be constucted programmatically. > > ZnUrl new > scheme: #https; > host: ''encrypted.google.com''; > addPathSegment: ''search''; > queryAt: ''q'' put: ''Smalltalk''; > yourself. > > My components can be manipulated destructively. Here is an example: > > (''http://www.google.com/?one=1&two=2'' asZnUrl) > queryAt: ''three'' put: ''3''; > queryRemoveKey: ''one''; > yourself. > > Some characters of parts of a URL are illegal because they would interfere with the syntax and further processing and thus have to be encoded. The methods in accessing protocols do not do any encoding, those in parsing and printing do. Here is an example: > > (''http://www.google.com'' asZnUrl) > addPathSegment: ''some encoding here''; > queryAt: ''and some encoding'' put: ''here, too''; > yourself > > My parser is somewhat forgiving and accepts some unencoded URLs as well, like most browsers would. > > ''http://www.example.com:8888/a path?q=a, b, c'' asZnUrl. > > I can parse in the context of a default scheme, like a browser would do. > > ZnUrl fromString: ''www.example.com'' defaultScheme: #http > > Given a scheme, I know its default port, try #portOrDefault. > > A path defaults to what is commonly referred to as slash, test with #isSlash. Paths are most often (but don''t have to be) interpreted as filesystem paths. To support this, I have #isFile and #isDirectory tests and #file and #directory accessors. > > I have some support to handle one URL in the context of another one, this is also known as a relative URL in the context of an absolute URL. Refer to #isAbsolute, #isRelative and #inContextOf: > > ''/folder/file.txt'' asZnUrl inContextOf: (''http://fileserver.example.net:4400'' asZnUrl). > > Sometimes, the combination of my host and port are referred to as authority, see #authority. > > URL/URI/URN (Uniform/Universal Resource Locator/Identifier/Name) are closely related and can be and are used as synonyms is many contexts. Refer to http://en.wikipedia.org/wiki/Url for more information. > > Part of Zinc HTTP Components. > >

Dec. 14, 2011