October 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] TextConstants
by StÃ©phane Ducasse Oct. 5, 2010

Oct. 5, 2010

probably start step by step defining first the sharedPool class after after migrating silently (no ui feedback) Stef On Oct 5, 2010, at 3:46 PM, NicolÃ¡s Paez wrote: > Hi, I noticed that this PoolDictinary is not implemented like the others that are based on SharedPool. > I made some research in this the mailing list (and in Squeak), and the only explanation I found is that it is a risky and time consuming task to change the implementation of TextConstant. > > I would like to do a spike trying to implemented the change and see what I find. > > Has anyone tried to perform this change? > > Do you have any warning/suggestion? > > Regards, > > Saludos! > Nico. > blog: nicopaez.wordpress.com > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Re: [Pharo-project] [update 1.2] #12170
by StÃ©phane Ducasse Oct. 5, 2010

Oct. 5, 2010

On Oct 5, 2010, at 12:25 PM, Henrik Johansen wrote: > So aMethod parameter can be either CompiledMethod (method recategorization), nil (when building core), or a selector (dropping cs). > Makes total sense... :P we should really fix that this is really ugly. So we will have to fix that. > Cheers, > Henry > > On Oct 5, 2010, at 12:03 22PM, StÃ©phane Ducasse wrote: > >> aMethod is a selector. >> >> so we should change the code and like that the tests get green :). >> >> Stef >> >>> Henrik >>> >>> when I drop a cs I get a DNU. >>> No time to check now. >>> >>> Stef >>> On Oct 5, 2010, at 11:51 AM, StÃ©phane Ducasse wrote: >>> >>>>> >>>>> >>>>> From: stephane ducasse <stephane.ducasse(a)gmail.com> >>>>> Date: October 5, 2010 11:43:17 AM GMT+02:00 >>>>> To: An open mailing list to discuss any topics related to an open-source Smalltalk <Pharo-project(a)lists.gforge.inria.fr> >>>>> Subject: [update 1.2] #12170 >>>>> >>>>> >>>>> >>>>> 12170 >>>>> ----- >>>>> >>>>> - Issue 3060: Update Monticello to detect method recategorization correctly. Thanks Pavel Krivanek and Henrik Johanssen >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] Soap Webservices for pharo
by Guillermo Polito Oct. 5, 2010

Oct. 5, 2010

http://www.mars.dti.ne.jp/~umejava/smalltalk/soapOpera/soapCore.html So, we have some tasks now: - put it in squeaksource - test it in pharo - build a metacello config - document it? Any help is really appreciated, since I don't have too much time. Cheers, Guille ---------- Forwarded message ---------- From: Masashi Umezawa <umejava(a)mars.dti.ne.jp> Date: Mon, Oct 4, 2010 at 8:46 AM Subject: Re: About SoapOpera and SoapCore To: Guillermo Polito <guillermopolito(a)gmail.com> Hi Guillermo, I am happy to hear that SoapOpera and SoapCore would be useful for your projects. Please feel free to reuse my Soap stuff. Recently I do not have enough time to upgrade those packages. So I really appreciate your offer. I hope SoapOpera and SoapCore will start growing again! Best regards, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi! > > My name's Guillermo and I'm from Argentina. I'm participating in the pharo > project (www.pharo-project.org) and I would love to integrate your soap > package into our available packages :). > I was wandering if you let us put it into squeaksource ( www.squeaksource.com) > and mantain it for our use, because pharo is growing very quickly and it > needs this kind of really cool stuff :). Of course we will keep the MIT > license. > > Thank you for your time and sorry for bothering :P! > Guille --- [:masashi | ^umezawa]

2 2

[Pharo-project] Xml Parser
by Guillermo Polito Oct. 5, 2010

Oct. 5, 2010

I looked after it in squeaksource and I didn't find it... Can some one enlight me? Cheers!

3 4

Re: [Pharo-project] Ocean (was Re: Less plugins, more Smalltalk code! (was: Re: Pharo 1.1.1 OneClickCogVm))
by StÃ©phane Ducasse Oct. 5, 2010

Oct. 5, 2010

On Oct 4, 2010, at 10:23 PM, Levente Uzonyi wrote: > On Mon, 4 Oct 2010, Sven Van Caekenberghe wrote: > >> Noury, >> >> One of the other aspects that I find important is elementary efficiency. >> >> A lot of stream related code in Smalltalk is not efficient, the actual data is copied around like crazy, turning it from a stream to a collection and then back into a stream multiple times. For Zinc HTTP Components I made a lot of effort to make it possible to read data from a socket stream in true streaming fashion (instead of just returning a byte array). Now, the idea was then that for example JPEGReadWriter>>#nextImage would work transparaently on that raw stream. Sadly, the code in JPEGReadWriter and friends just reads everything into an array before it starts to work ! >> >> Doing a #nextPutAll: <some byte array> should really try never to copy the array. Similary, a #next: <count> into: <some byte array> should similary write directly into the given array. What I see in the current SocketStream is <censored/> ;-) > > This is why we implemented our own SocketStream in PostgresV3. what is the license? Stef > >> >> But OK, maybe this is easier said than done. The step from Smalltalk to system call should also not copy if that is possible, but then FFI and GC come into play. > > I wonder if there's a language, that provides socket access via FFI. > > > Levente > >> >> Anyway, good luck, I am willing to try using Ocean as soon as it becomes available. >> >> Sven >> >> On 04 Oct 2010, at 10:59, Noury Bouraqadi wrote: >> >>> >>> On 3 oct. 2010, at 16:28, Schwab,Wilhelm K wrote: >>> >>>> For Ocean to succeed, you either have to work really hard to make non-blocking calls (I'm thinking of SSL sockets), or you need the ability to call functions on OS threads. The calls need to block their calling Process and let the other Processes run as though nothing is happening. >>>> >>> You're right. >>> Another option is having a multi-threaded VM. Eliot seem to work on it. >>> So far we're working on cleaning up the design of basic functionalities before going on. >>> Then, we'll try to find a workaround for non-blocking calls. >>> All ideas are welcome :-) >>> >>> BTW, some people (you included) proposed to help for the Ocean project. >>> Luc and I want to thank you and we are happy that others are willing to help. >>> We thought about the best way to integrate others help. >>> Our conclusion is that we should first do alone (luc and me) the reference design, before integrating other developers. >>> So, we all can work on solid foudations. >>> >>> Noury >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

Re: [Pharo-project] [update 1.2] #12170
by StÃ©phane Ducasse Oct. 5, 2010

Oct. 5, 2010

aMethod is a selector. so we should change the code and like that the tests get green :). Stef > Henrik > > when I drop a cs I get a DNU. > No time to check now. > > Stef > On Oct 5, 2010, at 11:51 AM, StÃ©phane Ducasse wrote: > >>> >>> >>> From: stephane ducasse <stephane.ducasse(a)gmail.com> >>> Date: October 5, 2010 11:43:17 AM GMT+02:00 >>> To: An open mailing list to discuss any topics related to an open-source Smalltalk <Pharo-project(a)lists.gforge.inria.fr> >>> Subject: [update 1.2] #12170 >>> >>> >>> >>> 12170 >>> ----- >>> >>> - Issue 3060: Update Monticello to detect method recategorization correctly. Thanks Pavel Krivanek and Henrik Johanssen >>> >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

3 5

Re: [Pharo-project] [update 1.2] #12170
by StÃ©phane Ducasse Oct. 5, 2010

Oct. 5, 2010

Henrik when I drop a cs I get a DNU. No time to check now. Stef On Oct 5, 2010, at 11:51 AM, StÃ©phane Ducasse wrote: >> >> >> From: stephane ducasse <stephane.ducasse(a)gmail.com> >> Date: October 5, 2010 11:43:17 AM GMT+02:00 >> To: An open mailing list to discuss any topics related to an open-source Smalltalk <Pharo-project(a)lists.gforge.inria.fr> >> Subject: [update 1.2] #12170 >> >> >> >> 12170 >> ----- >> >> - Issue 3060: Update Monticello to detect method recategorization correctly. Thanks Pavel Krivanek and Henrik Johanssen >> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Oct. 5, 2010

> > > From: stephane ducasse <stephane.ducasse(a)gmail.com> > Date: October 5, 2010 11:43:17 AM GMT+02:00 > To: An open mailing list to discuss any topics related to an open-source Smalltalk <Pharo-project(a)lists.gforge.inria.fr> > Subject: [update 1.2] #12170 > > > > 12170 > ----- > > - Issue 3060: Update Monticello to detect method recategorization correctly. Thanks Pavel Krivanek and Henrik Johanssen > >

1 0

Re: [Pharo-project] Issue 3060: Update Monticello to detect method recategorization correctly
by StÃ©phane Ducasse Oct. 5, 2010

Oct. 5, 2010

Thanks guys. I will just after my presentation on seaside to IRIL http://www.irill.org/events/irill-days-2010/irill-days-2010-detailed-program Stef On Oct 5, 2010, at 10:18 AM, Pavel Krivanek wrote: > Hi, > > please integrate the fix. > > Cheers, > -- Pavel > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] Issue 3060: Update Monticello to detect method recategorization correctly
by Pavel Krivanek Oct. 5, 2010

Oct. 5, 2010

Hi, please integrate the fix. Cheers, -- Pavel

2 1