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

Re: [Pharo-project] Bug in NetNameResolver on PharoCore 10508?

by Hernan Wilkinson

The changed you suggested worked on my machine, mac os X and also on a Debian. Hernan. 2010/1/28 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > El jue, 28-01-2010 a las 07:57 -0500, Schwab,Wilhelm K escribiÃ³: > > I think you are correct about that being a bad change, but there is more > wrong than just that. There are IPv6-specific calls that are not protected > by subsequent tests on #useOldNetwork. Further, the IPv6 code does not work > correctly, so many of us appear to need to override #useOldNetwork to always > return true. I make that change in #useOldNetwork rather than #initialize. > > > > Bill > > > Yes, I know that the code is very difficult to understand, mainly > because of the primitives. They brake the understanding you have so far > when you have to switch to c code with a lot of pointers/structs/string > buffers. > > The problem here is that, now it is impossible to change the networks > subsystem of Pharo (or squeak). As Mariano said, we *need* to release > 1.0 and this bug can be a show stopper. > > Also, with due respect to the original coders of the network subsystem, > the code is really convoluted (I know that networking isn't simple), at > least to understand the fully implication of a "simple" change like > this. It is not a well factored code. It mixes GUI prompts, IPv4, IPv6, > primitives and smalltalk code. So I think that is difficult to have > someone with the enough knowledge to change the code so that it works > for now. But that is how things are now. Maybe our own ignorance of the > code is what negates us a fix, but we need to left that apart and work a > solution for the *particular* problem in hand. For 1.1 we can discuss > new implementation if that is required. > > As Adrian said, there are users that need useOldNetwork true and some > others that need useOldNetwork to false. The problem is that we don't > fully understand the consequences of both changes. > > So, people, we need your help. Those who are most familiar with the > network code, please, please, take a look and suggest a solution for the > 1.0 release. *No* full rewrites, no throw code, no blaming, just a > working workaround for this. > > Regards > > Miguel Coba > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 29, 2010

[Pharo-project] started to finish to clean PopUpMenu and friend

by StÃ©phane Ducasse

Issue 1889: clarifying PopUpMenu vs. MenuMorph inbox/Slice-1889-CleaningPopUpAndFriend-StephaneDucasse.1 Stef

Jan. 29, 2010

Re: [Pharo-project] about: Slice-CleaningAndFixingImageSegmentPart2-MarianoMartinezPeck.9

by StÃ©phane Ducasse

ok excellent I will integrate it probably tomorrow morning :) Stef On Jan 29, 2010, at 9:37 PM, Mariano Martinez Peck wrote: > > > On Fri, Jan 29, 2010 at 9:33 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > hi M > > > that's TOO lazy :) > > should I integrate that? > > > Yes. It was the last merge we reviewed together at Douai. Do you remeber ? That you discovered a little problem I was introducing :) and then I fixed it. > > > 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

Jan. 29, 2010

[Pharo-project] peek and friends

by stephane ducasse

hi Igor finally should I integrate http://bugs.squeak.org/view.php?id=7446 ? I was waiting because you said you were confused Stef

Jan. 29, 2010

[Pharo-project] Pharo web documentation viewer

by laurent laffont

Hi, now that seasidehosting can run Pharo, I've uploaded rc2 image with SimpleWebDoc. All packages documentation browsable here: http://magaloma.seasidehosting.st Laurent

Jan. 29, 2010

Re: [Pharo-project] about: Slice-CleaningAndFixingImageSegmentPart2-MarianoMartinezPeck.9

by Mariano Martinez Peck

On Fri, Jan 29, 2010 at 9:33 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > hi M > > that's TOO lazy :) > should I integrate that? > > Yes. It was the last merge we reviewed together at Douai. Do you remeber ? That you discovered a little problem I was introducing :) and then I fixed it. > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 29, 2010

[Pharo-project] about: Slice-CleaningAndFixingImageSegmentPart2-MarianoMartinezPeck.9

by StÃ©phane Ducasse

hi M should I integrate that? Stef

Jan. 29, 2010

Re: [Pharo-project] Coordination :)

by StÃ©phane Ducasse

On Jan 29, 2010, at 9:18 PM, laurent laffont wrote: > > BTW laureant with 1.1 you do not need the isKindOf: in the browser anymore :) > > OK... I will try 1.1 when 1.0 will be released :) Dont stress do not change it I wanted to say that we learned from the video and fixed the problem immediately > .... I think I should do less (different) stuff .... time .. time ... time ... I know the syndrome. Have fun this is the more important aspect. > Laurent

Jan. 29, 2010

[Pharo-project] ToolBuilder improvements....

by StÃ©phane Ducasse

Hi guys to relax I spent some time and I checked all the Toolbuilder-Kernel, ToolBuilder-Morphic changes in Squeak. Most of them looks good so I produced a slice. Slice-1895 Issue 1895: ToolBuilder squeak integration and related If one of you want to have a look go ahead and let me know. Stef

Jan. 29, 2010

[Pharo-project] [update 1.1] #11185 and 1186

by StÃ©phane Ducasse

[update 1.1] #11185 11186 ----- Issue 1880: nextChunk speedup part one and part two Thanks a lot henrik Stef PS: Miguel I did not check yet your fix because I wanted to do something relaxing to recharge my battery :)

Jan. 29, 2010