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

Re: [Pharo-project] Issue 3660 in pharo: Revert incorrect Monticello branch naming support

by pharo＠googlecode.com

Updates: Status: Fixed Labels: 1.3 1.2 1.1 Comment #5 on issue 3660 by stephane...(a)gmail.com: Revert incorrect Monticello branch naming support http://code.google.com/p/pharo/issues/detail?id=3660 Thanks both of you !!!!! In 13040 Todo: in 1.2 for sure, may be in 1.1 (but I do not know).

Feb. 6, 2011

Re: [Pharo-project] Issue 3666 in pharo: Ensure that classOrTraitNamed: doesn't return globals.

by pharo＠googlecode.com

Updates: Status: closed Comment #3 on issue 3666 by stephane...(a)gmail.com: Ensure that classOrTraitNamed: doesn't return globals. http://code.google.com/p/pharo/issues/detail?id=3666 in 13040

Feb. 6, 2011

Re: [Pharo-project] Issue 3667 in pharo: ThreadSafeTranscript does not understand crtab and crtab:

by pharo＠googlecode.com

Updates: Status: Accepted Comment #1 on issue 3667 by stephane...(a)gmail.com: ThreadSafeTranscript does not understand crtab and crtab: http://code.google.com/p/pharo/issues/detail?id=3667 Thanks. Goo idea if you have the definition for these methods it will be easier to get them in.

Feb. 6, 2011

Re: [Pharo-project] Hudson build for Seaside too?

by Marcus Denker

On Feb 4, 2011, at 4:13 PM, Dale Henrichs wrote: > Marcus, > > Since I seem to be on a symbolic version kick today, may I suggest that you use symbolic versions for Hudson: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside30'; > load. > > ((Smalltalk at: #ConfigurationOfSeaside30) project version: #stable) load. > > when you get a chance ... Done. > the above expression can be used for all of your Hudson builds regardless of pharo version. use the same, but it loads then a different *stable* for each version? and > ((Smalltalk at: #ConfigurationOfSeaside30) project version: #unstable) load. would load the latest code into e.g. 1.3? Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 6, 2011

Re: [Pharo-project] [Hudson] Regression Testing

by StÃ©phane Ducasse

Yesssss I love that ;) Stef On Feb 6, 2011, at 3:31 PM, Marcus Denker wrote: > > https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3%20… > > The idea is that there are lots of things that are almost never tested because the tests would take too long. > *and* because the tests do something to the image that is not wanted for a normal build. > > Examples > > -> recompile everything, run tests again > -> decompile everything to text, compile and install > -> format everything and compile > -> condense changes > -> write new sources > -> run without sources > -> run without sources but encoded temps > -> ..... what else??? > > The idea is that this CI Server Project runs all these > after every build, but not as part of main build (so it does not lengthen the build process). > > For now, this just has one test that recompiled the image and does nothing else. > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

Feb. 6, 2011

Re: [Pharo-project] [COTDC] 3 - HTTPClient

by StÃ©phane Ducasse

Hi francisco > It would be great to ilustrate post usage as well and delete class > method #examplePostArgs open a ticket. Stef > > I'm a facade for doing simple HTTP GET/POST operations like > downloading / uploading some content. > > For example, I get HTML content for http://www.pharo-project.org web > page like this: > > HTTPClient httpGet: 'http://www.pharo-project.org'. > HTTPClient httpGetDocument: 'http://www.pharo-project.org'. > > Or, i can make a post request to http://www.pharo-project.org and send > data to the server like this: > > args := Dictionary new. > args > at: 'arg1' put: #('val1'); > at: 'arg2' put: #('val2'). > result := HTTPClient httpPostDocument: 'http://www.pharo-project.org' > args: args. > > When successful, a Stream respectively a MIMEDocument is returned, in > case of error, a String is returned. > > On Sun, Feb 6, 2011 at 5:03 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: >> >> On 06 Feb 2011, at 18:23, laurent laffont wrote: >> >>> I'm a facade for doing simple HTTP GET/POST operations like downloading / uploading some content. >>> >>> For example, I get HTML content for http://www.pharo-project.org web page like this: HTTPClient httpGet: 'http://www.pharo-project.org'. >> >> I'm a facade for doing simple HTTP GET/POST operations like downloading / uploading some content. >> >> For example, I get HTML content for http://www.pharo-project.org web page like this: >> >> HTTPClient httpGet: 'http://www.pharo-project.org'. >> HTTPClient httpGetDocument: 'http://www.pharo-project.org'. >> >> When successful, a Stream respectively a MIMEDocument is returned, in case of error, a String is returned. >> >> >

Feb. 6, 2011

Re: [Pharo-project] [COTDC] 3 - HTTPClient

by Francisco Ortiz PeÃ±aloza

It would be great to ilustrate post usage as well and delete class method #examplePostArgs I'm a facade for doing simple HTTP GET/POST operations like downloading / uploading some content. For example, I get HTML content forÂ http://www.pharo-project.orgÂ web page like this: Â Â Â Â HTTPClient httpGet: 'http://www.pharo-project.org'. Â Â Â Â HTTPClient httpGetDocument: 'http://www.pharo-project.org'. Or, i can make a post request to http://www.pharo-project.org and send data to the server like this: args := Dictionary new. args at: 'arg1' put: #('val1'); at: 'arg2' put: #('val2'). result := HTTPClient httpPostDocument: 'http://www.pharo-project.org' args: args. When successful, a Stream respectively a MIMEDocument is returned, in case of error, a String is returned. On Sun, Feb 6, 2011 at 5:03 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 06 Feb 2011, at 18:23, laurent laffont wrote: > > > I'm a facade for doing simple HTTP GET/POST operations like downloading / uploading some content. > > > > For example, I get HTML content for http://www.pharo-project.org web page like this: HTTPClient httpGet: 'http://www.pharo-project.org'. > > I'm a facade for doing simple HTTP GET/POST operations like downloading / uploading some content. > > For example, I get HTML content for http://www.pharo-project.org web page like this: > > Â Â Â Â HTTPClient httpGet: 'http://www.pharo-project.org'. > Â Â Â Â HTTPClient httpGetDocument: 'http://www.pharo-project.org'. > > When successful, a Stream respectively a MIMEDocument is returned, in case of error, a String is returned. > >

Feb. 6, 2011

Re: [Pharo-project] [COTDC] 3 - HTTPClient

by Sven Van Caekenberghe

On 06 Feb 2011, at 18:23, laurent laffont wrote: > I'm a facade for doing simple HTTP GET/POST operations like downloading / uploading some content. > > For example, I get HTML content for http://www.pharo-project.org web page like this: HTTPClient httpGet: 'http://www.pharo-project.org'. I'm a facade for doing simple HTTP GET/POST operations like downloading / uploading some content. For example, I get HTML content for http://www.pharo-project.org web page like this: HTTPClient httpGet: 'http://www.pharo-project.org'. HTTPClient httpGetDocument: 'http://www.pharo-project.org'. When successful, a Stream respectively a MIMEDocument is returned, in case of error, a String is returned.

Feb. 6, 2011

[Pharo-project] Issue 3668 in pharo: remove SmalltalkImage scopeFor:from:envtAndPathIfFound:

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com New issue 3668 by marcus.d...(a)gmail.com: remove SmalltalkImage scopeFor:from:envtAndPathIfFound: http://code.google.com/p/pharo/issues/detail?id=3668 scopeFor:from:envtAndPathIfFound: ... maybe deprecate, maybe delete. (looks like a remnant of the nested SystemDictionary namespaces)

Feb. 6, 2011

Re: [Pharo-project] Network training

by Levente Uzonyi

On Sat, 5 Feb 2011, Luc Fabresse wrote: snip > Hi Levente, > > Why I am doing Ocean with Noury is: > > 1) Network never worked fine for me (NetNameResolver ,...). The API (Image > side) is not OO (All concerns in Socket: IPV4, IPV6, TCD, UDP, ...). > We first try to write unit tests and then we planned to redesign the API. > But it implies to understand well the primitives and it is not EASY at all. > Some are said old in comments (IPV4 primitives?), some are new (IPV6?),... > So it is a too HARD to understand this code without doc or explanations > (and you are right I am also a poor newbie). There was an "old" implementation of sockets, where every socket had a single semaphore. The "new" implementation added separate read and write semaphores. I guess this change was around 2005, so you can assume that every VM has the "new" implementation. There was another change for IPv6 support.AFAIK CogVMs don't have these primitives, but SqueakVMs do. > > 2) I do not want to hear this sentence anymore: "Oh yes, you use a VM with > an old version of the socket plugin. You should recompile the VM." > NO! I CAN'T DO THAT BECAUSE (until recently) RECOMPILING THE VM REQUIRE DEEP > KNOWLEDGE AND SOME BLACK MAGIC. (Thanks to Igor, Esteban and all others to Sorry but this is simply bullshit, the result of some people spreading FUD. Recompiling the VM is easy. I could compile VMs when I was a Squeak newbie. The same applies for writing plugins. > prepare a simple process for newbies like me such as checkout and compile). > > > 3) Ocean idea: pull up the network stuff on the image side. use an FFI to > call OS libs. With this approach I am able to: load new versions of the > network without changing the VM, in the future directly call the new OS API > (Grand Central on OSX for asynchronous sockets, --yes network libs > evolve--...), write more high level code and it is a little bit easier to > debug it. The idea is nice, but I guess the performance will be a lot worse than using a custom plugin. > > Ocean is our vision, perhaps it is wrong but I can not do better. > It is not as complete as the plugin yet. > We also plan to use either Alien+OS lib or the plugin as a backend for > Ocean so the plugin will still be there at the end for those who want it. > And for this last part, we will certainly need some explanations on the > primitives in SocketPlugin code. So if you know it well, feel free to > educate me. I don't know it well, but I usually deeply explore the code if I want to know how it works (or how it should work). Googling mailing lists and the squeak wiki used to be helpful too. Levente > > #Luc snip

Feb. 6, 2011