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

Re: [Pharo-project] Issue 3417 in pharo: BehaviorTest>>#testAllLocalCallsOn fails

by pharo＠googlecode.com

Updates: Status: closed Comment #3 on issue 3417 by stephane...(a)gmail.com: BehaviorTest>>#testAllLocalCallsOn fails http://code.google.com/p/pharo/issues/detail?id=3417 A possible solution would be hash ^ super hash bitXor: self sourcePointer hash

Jan. 14, 2011

Re: [Pharo-project] Socket question (Was Re: Xtreams up to date)

by Sven Van Caekenberghe

On 14 Jan 2011, at 12:54, Schwab,Wilhelm K wrote: > I am really bothered by the timeout on the accept, so much so that I think it has no place in the tests. Of course, one needs a way to clean up after a failure, but that should be done by another thread that waits for a "long" time and then cleans up anything that is left behind after the failure. > > Servers should be started and stopped and in between, they should wait for and accept connections. Clients should try to connect until told otherwise; timeouts can be reasonable options there, but should not be forced by the sockets system. Only the calling threads should be blocked, of course. I don't understand why this would bother you: it is the 'client/user' that decides about the timeout (you could use some very large number for an 'infinite' timeout). You need of course a loop around it. Here is the code from ZnSingleThreadedServer (which started from the Blackfoot example): listenLoop "We create a listening Socket, then wait for a connection. After each connection we also check that the listening Socket is still valid - if not we just make a recursive call to this method to start over." self initializeServerSocket. [ [ serverSocket isValid ifFalse: [ "will trigger #ifCurtailed: block and destroy socket" ^ self listenLoop ]. self serveConnectionOn: serverSocket ] repeat ] ifCurtailed: [ self releaseServerSocket ] serveConnectionOn: listeningSocket "We wait up to acceptWaitTimeout seconds for an incoming connection. If we get one we wrap it in a SocketStream and #executeOneRequestResponseOn: on it" | stream socket | socket := (listeningSocket waitForAcceptFor: self acceptWaitTimeout) ifNil: [ ^ self log: 'Wait for accept timed out' ]. stream := ZnNetworkingUtils socketStreamOn: socket. [ [ [ self executeOneRequestResponseOn: stream ] ensure: [ self log: 'Closing stream'. stream close ] ] ifCurtailed: [ self log: 'Destroying socket'. socket destroy ] ] forkAt: Processor highIOPriority named: 'Zinc HTTP Server Worker' Each #acceptWaitTimeout seconds, 'Wait for accept timed out' is printed on the log and another accept/wait starts. This looping improves liveliness and responsiveness to other events. Sven

Jan. 14, 2011

Re: [Pharo-project] Issue 2818 in pharo: Eliot and friends compiler fixes

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2 Milestone-1.3 Comment #6 on issue 2818 by stephane...(a)gmail.com: Eliot and friends compiler fixes http://code.google.com/p/pharo/issues/detail?id=2818 (No comment was entered for this change.)

Jan. 14, 2011

Re: [Pharo-project] linux equivalent to monticello metacello...

by Esteban Lorenzano

wel... I made the "Gofer Project Loader" (http://smallworks.com.ar/en/community/GoferProjectLoader) to handle metacello configurations as apt-get. It's working, needs to add some fixes Adrian ask me like six months ago and I forget to do it... but there was "configurations for diferent pharo versions", very easy. Is there are still some interest, I can update it :P best, Esteban El 14/01/2011, a las 11:08a.m., laurent laffont escribiÃ³: > On Fri, Jan 14, 2011 at 2:43 PM, Geoffroy Couprie <geo.couprie(a)gmail.com> wrote: > On Fri, Jan 14, 2011 at 2:00 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > > > > > for the chapter on metacello I would like to have a table showing the equivalent between > > linux tools (if this is true) > > > > apt-get... and monticello/metacello > > > > can somebody point me to that ? > > > > I would say that the mapping is: > Monticello <-> dpkg (without the repository management) > Metacello <-> apt > > > Note that it's Debian / Ubuntu / .. equivalent. Because: > On ArchLinux / Chakra / ... > Monticello <-> pkg > Metacello <-> pacman > > On RedHat / CentOS / .... > Monticello <-> rpm > Metacello <-> yum > > and there's more :) > > Laurent

Jan. 14, 2011

Re: [Pharo-project] linux equivalent to monticello metacello...

by laurent laffont

On Fri, Jan 14, 2011 at 2:43 PM, Geoffroy Couprie <geo.couprie(a)gmail.com>wrote: > On Fri, Jan 14, 2011 at 2:00 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > > > > > for the chapter on metacello I would like to have a table showing the > equivalent between > > linux tools (if this is true) > > > > apt-get... and monticello/metacello > > > > can somebody point me to that ? > > > > I would say that the mapping is: > Monticello <-> dpkg (without the repository management) > Metacello <-> apt > > Note that it's Debian / Ubuntu / .. equivalent. Because: On ArchLinux / Chakra / ... Monticello <-> pkg Metacello <-> pacman On RedHat / CentOS / .... Monticello <-> rpm Metacello <-> yum and there's more :) Laurent

Jan. 14, 2011

Re: [Pharo-project] linux equivalent to monticello metacello...

by Norbert Hartl

On 14.01.2011, at 14:00, StÃ©phane Ducasse wrote: > > > for the chapter on metacello I would like to have a table showing the equivalent between > linux tools (if this is true) > > apt-get... and monticello/metacello > > can somebody point me to that ? > Can you elaborate a little what you are after? Norbert

Jan. 14, 2011

[Pharo-project] How to bundle an application with icons?

by Dimitry Golubovsky

Hi, Fernando Olivero wrote: > Hi Dimitry , i've did an external icon family importer and manager. > It's in squeaksource, under the name of ExternalIconFamily. > Gofer it > squeaksource: 'ExternalIconFamily'; > package: 'ExternalIconFamily'; > load. > This framework allows importing and managing any external icon family. > Once imported , the icon family is reified into the image, as a > subclass of ExternalIconFamily. > As an example it comes with a tiny subset of the Oxygen icon family imported. [skip] Thanks a lot. I am currently working on other aspects of the application, but this icon importer will be a great customization tool. I'll definitely give it a try. -- Dimitry Golubovsky Anywhere on the Web

Jan. 14, 2011

Re: [Pharo-project] linux equivalent to monticello metacello...

by Geoffroy Couprie

On Fri, Jan 14, 2011 at 2:00 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > > for the chapter on metacello I would like to have a table showing the equivalent between > linux tools (if this is true) > > Â Â Â Â apt-get... and monticello/metacello > > can somebody point me to that ? > I would say that the mapping is: Monticello <-> dpkg (without the repository management) Metacello <-> apt

Jan. 14, 2011

[Pharo-project] [update 1.2] #12304

by StÃ©phane Ducasse

12304 ----- - Theme tweaks from Igor.

Jan. 14, 2011

[Pharo-project] linux equivalent to monticello metacello...

by StÃ©phane Ducasse

for the chapter on metacello I would like to have a table showing the equivalent between linux tools (if this is true) apt-get... and monticello/metacello can somebody point me to that ? Stef

Jan. 14, 2011