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

Re: [Pharo-project] About ExternalDropHandler initialize

by Gary Chambers

I guess the registerHandler: bits should move to registerStandardExternalDropHandlers. Even after cleanUp you'd want them, I think. Most of the users of ExternalDropHandler actually call the initialize instead of cleanUp for doing clean up... Regards, Gary ----- Original Message ----- From: "stephane ducasse" <stephane.ducasse(a)free.fr> To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, March 09, 2010 4:55 PM Subject: [Pharo-project] About ExternalDropHandler initialize > Hi guys > > registerStandardExternalDropHandlers is not invoked from the class > initialize and I was wondering if > one of you know why. > Right now we have: > > ExternalDropHandler class >> initialize > "ExternalDropHandler initialize" > > self resetRegisteredHandlers. > self > registerHandler: self defaultImageHandler; > registerHandler: self defaultGZipHandler. > > This is the same in Squeak > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 9, 2010

[Pharo-project] About ExternalDropHandler initialize

by stephane ducasse

Hi guys registerStandardExternalDropHandlers is not invoked from the class initialize and I was wondering if one of you know why. Right now we have: ExternalDropHandler class >> initialize "ExternalDropHandler initialize" self resetRegisteredHandlers. self registerHandler: self defaultImageHandler; registerHandler: self defaultGZipHandler. This is the same in Squeak

March 9, 2010

Re: [Pharo-project] networking problem (repost)

by John M McIntosh

Well Michael is dropping by for a visit. I think we'll reserve a few hours to figure out the technical side of what the proper answer is when you want to know what your IP and interface in use is. Either this is easy to do and *fixes* all the hassles, or unlikely... >From what I gather this is the key issue of the IPV6 usage ? > > Yes, please, I vote for reverting to the old working code. In 1.1 or now > with the GSoC we can propose a new infrastructure for Networking. -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

March 9, 2010

Re: [Pharo-project] Full time engineer position for Pharo looking for cool engineer :)

by Miguel Enrique CobÃ¡ Martinez

El lun, 08-03-2010 a las 21:36 +0100, StÃ©phane Ducasse escribiÃ³: > Hi guys > > Some good news :) Very good indeed. Some questions? - Is french required (A1 DELF or something like that) or English is enough? - Is just for single persons or married ones with kids are allowed? - Do you have some profile you would prefer for the position? -- Visible projects in Smalltalk -- Long time of contributing to Pharo - What kind of Visa is required? - Is some specific technical hability needed (networking experience, vm hacking experience) Cheers > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 9, 2010

[Pharo-project] Please: less license blahblah, more actual progress on the issue

by Paolo Bonzini

On Mon, Mar 8, 2010 at 18:53, stephane ducasse <stephane.ducasse(a)gmail.com> wrote: > Thanks thanks thanks thanks for a refresh on that! > Thanks! Stef, instead of thanking five times, why don't you try to do something constructive? The GPLv3 includes a system of granting Additional Permissions. This system has already been used by GCC and Autoconf. Let's develop a set of additional permissions that we believe do not "taint" the whole image. I placed a starting point at http://smalltalk.gnu.org/blog/bonzinip/towards-permissive-copyleft-license-… [To those that followed the entire thread: this is totally independent of how any GSoC code related to GNU Smalltalk will be licensed]. Paolo

March 9, 2010

Re: [Pharo-project] Full time engineer position for Pharo looking for cool engineer :)

by Igor Stasenko

I'd be willing to apply. But i'm not sure if i fit for it. On 9 March 2010 17:15, Marcus Denker <marcus.denker(a)inria.fr> wrote: > On Mon, Mar 8, 2010 at 9:36 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> This is not the official job announce but just to give some hints and that you can prepare yourself to >> Â Â Â Â - move to France (one hour from paris, 1h30 from London, 35 min from Brussels) >> Â Â Â Â - try a lot of good beers (belgium :) > > e.g. this one is just 40Km away: > > Â http://www.sintsixtus.be/eng/brouwerij.htm > > Even the local beer is good: > > Â http://beeradvocate.com/beer/profile/260/1308/ > >> we can think that 2700 Euros (before final taxes) should be a good working number > > I think it should be explained that this is the french version of > "before taxes", not the same as, > for example, german brutto. This means, health insurance, pension and > all social welfare is > already deducted. So if we take taxes into account (single person, no > kids), this means you get > 2400 EUR/Month. > > To get 2400 EUR/Month in germany, you need a "before > tax/health/social/unemployment" salary > of 4.200 EUR/Month (or 50.000 EUR for the year). > > So it's not that bad. And Lille is cheap. As a typical european city, > you don't need a car, > and for the ticket for public transport, INRIA pays half. This means > my cost of transport > is just 18.50EUR a month, plus Train for traveling to Paris or London > on the weekend... > > The health insurance system is rated as one of the best public ones in > the world by the > WHO, the local hospital is the best in the whole country. And health insurance > is *not* connected to employment. One can *never* lose health insurance. > Whatever happens. > > Â Â Â Marcus > > -- > Marcus Denker Â -- Â denker(a)acm.org > http://www.marcusdenker.de > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

March 9, 2010

Re: [Pharo-project] [smalltalk-research] Re: [Esug-list] Google Summer Of Code 2010 news!!!

by Paolo Bonzini

On Tue, Mar 9, 2010 at 16:10, John O'Keefe <wembley.instantiations(a)gmail.com> wrote: > I am willing to co-mentor a Grease project and/or a portable TCPIP > implementation (we will need this for the OpenSSL project anyway). I can contribute the GNU Smalltalk TCP/IP implementation under whatever license. It's all written by me(*) so I can relicense it. (*) see http://git.savannah.gnu.org/gitweb/?p=smalltalk.git;a=blob;f=packages/socke… UnixStream.st is not anymore part of the package, and Nicolas Burrus' work is not present anymore since I introduce IPv6 support. Paolo

March 9, 2010

Re: [Pharo-project] in 11233 merging is broken?

by Gary Chambers

Rather than ScriptLoader it appears to be a Monticello bug/feature... In PharoCore-1.1-11254 merging Polymorph-Widgets-gvc.109 from SqueakSource doesn't pull in PasteUpMorph>>restoreMorphicDisplay. In fact, after merge it will say "no changes" upon attempted remerge, despite the obvious difference. Something to do with MC doing snapshots relative to (common) ancestors rather then the wroking copy it seems... Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Friday, February 26, 2010 9:36 AM Subject: Re: [Pharo-project] in 11233 merging is broken? I will have a look. Stef On Feb 25, 2010, at 10:38 PM, Marcus Denker wrote: > > On Feb 25, 2010, at 5:35 PM, GARY CHAMBERS wrote: > >> Something must be wrong with the script load somehow... >> >> Note that there are changes between working copy after load and >> Polymorph-Tools-Diff-StephaneDucasse.23.mcz. >> >> To fix for yourself at the moment, reload >> Polymorph-Tools-Diff-StephaneDucasse.23.mcz. >> > > > The Scriptloader seems to never loas from the repository? Ther is a > > Name: Polymorph-Tools-Diff-StephaneDucasse.46 > Author: StephaneDucasse > Time: 10 February 2010, 7:16:13 pm > > > Marcus > >> Not an answer to why though... >> >> Regards, Gary. >> >> From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> To: Pharo-project Development <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Thursday, 25 February, 2010 15:50:40 >> Subject: [Pharo-project] in 11233 merging is broken? >> >> Hi all >> >> I'm trying to integrate changes and apparently I cannot merge anymore >> nothing show up :). >> two questions: >> - do you get the behavior with 11233 or it is only me. >> - any idea of the potential problem >> >> - Issue 2071: subclasses and withAllSubclasses should return a >> array. >> - Issue 2076: Clean Exceptions. >> - Issue 2072: clean RealEstateAgent. >> >> >> Stef >> _______________________________________________ >> 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 > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > 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

March 9, 2010

Re: [Pharo-project] Full time engineer position for Pharo looking for cool engineer :)

by Marcus Denker

On Mon, Mar 8, 2010 at 9:36 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > This is not the official job announce but just to give some hints and that you can prepare yourself to > Â Â Â Â - move to France (one hour from paris, 1h30 from London, 35 min from Brussels) > Â Â Â Â - try a lot of good beers (belgium :) e.g. this one is just 40Km away: http://www.sintsixtus.be/eng/brouwerij.htm Even the local beer is good: http://beeradvocate.com/beer/profile/260/1308/ > we can think that 2700 Euros (before final taxes) should be a good working number I think it should be explained that this is the french version of "before taxes", not the same as, for example, german brutto. This means, health insurance, pension and all social welfare is already deducted. So if we take taxes into account (single person, no kids), this means you get 2400 EUR/Month. To get 2400 EUR/Month in germany, you need a "before tax/health/social/unemployment" salary of 4.200 EUR/Month (or 50.000 EUR for the year). So it's not that bad. And Lille is cheap. As a typical european city, you don't need a car, and for the ticket for public transport, INRIA pays half. This means my cost of transport is just 18.50EUR a month, plus Train for traveling to Paris or London on the weekend... The health insurance system is rated as one of the best public ones in the world by the WHO, the local hospital is the best in the whole country. And health insurance is *not* connected to employment. One can *never* lose health insurance. Whatever happens. Marcus -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

March 9, 2010

Re: [Pharo-project] networking problem (repost)

by Miguel Enrique CobÃ¡ Martinez

El mar, 09-03-2010 a las 09:08 +0000, Michael Roberts escribiÃ³: > i'm not sure this email came through whilst the list was down > sunday/monday so i am reposting by request. i will add some further > content at the end > ===================================================== > I have dug around the network problem (OS X) in Pharo 1.0. I am > convinced #useOldNetwork = true does not work. Looking through old > core images, it never worked; at least with my current OS and VM > choice. > > i have been using Magma as a test case. Indeed it is broken on 10508 > rc2, however if I set > > NetNameResolver classPool at: #UseOldNetwork put: false > > and hack #initializeNetwork to make the reference false as well (since > it can change its value once set)... I can run the first 10mins of the > Magma test suite which is heavy on network use. I only can't complete > the magma test case due to unrelated issues. I've asked Chris to see > if these changes work for him. > > i propose in Pharo Core 1.0 > -set UseOldNetwork := false, and change all references that try and > set it to true > -now we are only using the new network infrastructure, > -gather fresh test cases from the community where networking fails and > fix them with a final push. > -do not try and fix the UseOldNetwork := true branches > > If we can not get this approach above to work then as a fallback I > propose to remove all the new network code and revert it all back to > the point where it was simpler where socket addresses were just byte > arrays...We then spend more time in 1.1 trying to get it to work > properly. Does anyone care at this point how the infrastructure looks > in 1.0? The fact that our rc2 network layer is totally bust is enough > to do something drastic to finish the cycle. > > I propose in Pharo 1.1 > -strip out all useOldNetwork = true branches. it does not work, and > it is a mess to have these two branches side by side, especially when > the value of useOldNetwork can change on its own (this happened a > number of times to me) I guess due to all the attempts to check and > initialize the network. somewhere it flips. > > obviously we need some focus on testing a final set of changes, but > please consider the direction I outline. > > thanks, > Mike > ==================================================== > > I spent some time after writing this above looking at the magma test > case more deeply and chatting to Chris offline. After fixing a > quoting issue with magma image launching i managed to get the magma > test suite to run for about 30 mins (until it stopped...). So in > principle the networking does work... > > Then to my astonishment i could not get it to run again at all for > another few hours, i got no where... it was like it was a dream. I > suspect the problem is the exact network interfaces that the server > and client try to connect/bind to. In the old ipv4 world it was fairly > simple. i suspect in the ipv6 world, different parts of magma are > binding to different interfaces and i find it impenetrable to work out > which. i have lots of interfaces on my machine (wifi, ethernet, > parallels virtual, etc) and when you do NetNameResolver > localHostAddress (or whatever the message is) you get back only the > first one. I think this could be the cause of issues. Adrian mentions > to me John thought they came back randomly. > > So now my conclusion is firmly we have to take a step back and > simplify. for pharo 1.0 unless we have someone with a lot of time i > do not feel we can untangle the resolver and socket code. We should > revert it back to the original #[192 168 0 10] style code when it used > to be simple. This assumes the primitives still support this. Then > what I would like to see in Pharo 1.1 or 1.2, is that we separate out > classes for ip4 and ip6 support, and make them work cleanly and > transparently together. Just because we have ip6 support i don't want > to be forced to use it. we should have a clearer interface to > enumerate all the network interfaces on the machine, and we should > really document this heavily. I think the new help system would be > great for this. I started to have to write my own scripts just to > document the change in API across images. these can go straight into a > help system... Yes, please, I vote for reverting to the old working code. In 1.1 or now with the GSoC we can propose a new infrastructure for Networking. > > cheers, > Mike > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 9, 2010