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

Re: [Pharo-project] Fun with ProfStef

by Danny Chan

Hi! As discussed I've added a new repository ProfStefBrowser and uploaded a version which builds on top of the current ProfStef version from Laurent without touching the code in the ProfStef package. > - I found a little bug in the UI. If you double click on a lesson, a > debugger comes. Can you reproduce it ? I think I found out why this happens. Apparently, when you double click on an item, the item is deselected. The callback that is called in this case receives as the item which was clicked nil. I added a workaround, but since the callback is set using a message 'setSelectedSelector:' I personally feel that this behaviour is not intuitive and that this callback shouldn't be called at all when deselecting items. Who are the guys to talk to for this behaviour? Danny

Jan. 29, 2010

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

by Schwab,Wilhelm K

I for one never said we should throw out the new network code. But, we've been living in collective denial trying to reduce it to one defect when it is actually more complicated than that. Having cited the over-use of inheritance of the Squeak image as a source of various problems, I will add that inheritance *should* be used in NetNameResolver - specifically, we should group the ipv4 and ipv6 primitive sends into protocol-specific subclasses. Errors that are now weird-looking primitive failures will suddenly become DNU errors with an obvious cause. We should further send SocketAddress to its reward and make any required changes to use an aspect-based address that can lazily help with name resolution, and does not drag the port number into the address. The socket primitives will have to change at the same time (I think). IMHO, the only quick fix is to go back to known working network code, at which point we can plan for IPv6 in a future milestone. I urge the next attempt be based on an improved design, hopefully one that will allow OpenSSL sockets along with the usual suspects. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Michael Rueger Sent: Friday, January 29, 2010 7:23 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Bug in NetNameResolver on PharoCore 10508? On 1/29/2010 1:08 PM, Adrian Lienhard wrote: > Do I understand correctly?: ipv6 issues are a VM problem, hence not > directly related to Pharo. But #useOldNetwork does not work as > advertised in new network implementation because it still uses ipv6 > code/primitives. > > Hence, should we just roll back the network changes and use the old > code as in Squeak 3.9, which, as far as I can tell, works well? Apologies for coming in a bit late into the discussion. The new network plugin/code was orignally done by Ian and mangled by myself (with contributions by Bert and Yoshiki IIRC) to be used in etoys as OLPC is IPv6 only. So would be worthwhile checking the etoys network code. Idea behind getting the code into Pharo was to enable more than the really outdated and bare bones network access available through the old network code. That the new stuff still doesn't work is a shame, but IMHO we should fix it rather than throwing it out. Patching the current code to allow use of the old network stuff would buy us time to fix the new code. Michael _______________________________________________ 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

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

by Schwab,Wilhelm K

+10. -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Adrian Lienhard Sent: Friday, January 29, 2010 7:09 AM To: Pharo-project Development Subject: Re: [Pharo-project] Bug in NetNameResolver on PharoCore 10508? Do I understand correctly?: ipv6 issues are a VM problem, hence not directly related to Pharo. But #useOldNetwork does not work as advertised in new network implementation because it still uses ipv6 code/primitives. Hence, should we just roll back the network changes and use the old code as in Squeak 3.9, which, as far as I can tell, works well? Cheers, Adrian On Jan 28, 2010, at 22:52 , John M McIntosh wrote: > Some of this is all related to > > http://bugs.squeak.org/view.php?id=7392 > > However there is no expectations than any unix socket support code fixes will be forthcoming this year, or next? > > > On 2010-01-28, at 8:50 AM, StÃ©phane Ducasse wrote: > >> +1 >> > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. > http://www.smalltalkconsulting.com > ====================================================================== > ===== > > > > > > _______________________________________________ > 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

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

by Michael Rueger

On 1/29/2010 1:08 PM, Adrian Lienhard wrote: > Do I understand correctly?: ipv6 issues are a VM problem, hence not > directly related to Pharo. But #useOldNetwork does not work as > advertised in new network implementation because it still uses ipv6 > code/primitives. > > Hence, should we just roll back the network changes and use the old > code as in Squeak 3.9, which, as far as I can tell, works well? Apologies for coming in a bit late into the discussion. The new network plugin/code was orignally done by Ian and mangled by myself (with contributions by Bert and Yoshiki IIRC) to be used in etoys as OLPC is IPv6 only. So would be worthwhile checking the etoys network code. Idea behind getting the code into Pharo was to enable more than the really outdated and bare bones network access available through the old network code. That the new stuff still doesn't work is a shame, but IMHO we should fix it rather than throwing it out. Patching the current code to allow use of the old network stuff would buy us time to fix the new code. Michael

Jan. 29, 2010

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

by Adrian Lienhard

Do I understand correctly?: ipv6 issues are a VM problem, hence not directly related to Pharo. But #useOldNetwork does not work as advertised in new network implementation because it still uses ipv6 code/primitives. Hence, should we just roll back the network changes and use the old code as in Squeak 3.9, which, as far as I can tell, works well? Cheers, Adrian On Jan 28, 2010, at 22:52 , John M McIntosh wrote: > Some of this is all related to > > http://bugs.squeak.org/view.php?id=7392 > > However there is no expectations than any unix socket support code fixes will be forthcoming this year, or next? > > > On 2010-01-28, at 8:50 AM, StÃ©phane Ducasse wrote: > >> +1 >> > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > > _______________________________________________ > 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

Re: [Pharo-project] video in Pharo

by StÃ©phane Ducasse

yes marcus don't be negative we do pharo to think about the future. :) >> true I remember the point made by david about the effort required by the port. >> > > And what do you want with an old mpeg decoder anyway? The world moved on the last 10 years... > > > Marcus > >> Stef >> >> On Jan 28, 2010, at 10:54 PM, John M McIntosh wrote: >> >>> >>> On 2010-01-28, at 1:21 PM, StÃ©phane Ducasse wrote: >>> >>>> there was a mpeg plugin in squeak but I do not know its status. >>>> >>>> Stef >>> >>> >>> That won't be offered in the 64bit variations of squeak >>> >>> -- >>> =========================================================================== >>> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 >>> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com >>> =========================================================================== >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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

Jan. 29, 2010

Re: [Pharo-project] video in Pharo

by Marcus Denker

On Jan 29, 2010, at 9:14 AM, StÃ©phane Ducasse wrote: > true I remember the point made by david about the effort required by the port. > And what do you want with an old mpeg decoder anyway? The world moved on the last 10 years... Marcus > Stef > > On Jan 28, 2010, at 10:54 PM, John M McIntosh wrote: > >> >> On 2010-01-28, at 1:21 PM, StÃ©phane Ducasse wrote: >> >>> there was a mpeg plugin in squeak but I do not know its status. >>> >>> Stef >> >> >> That won't be offered in the 64bit variations of squeak >> >> -- >> =========================================================================== >> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 >> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com >> =========================================================================== >> >> >> >> >> >> _______________________________________________ >> 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.

Jan. 29, 2010

Re: [Pharo-project] [Seaside] [ANN] seasidehosting.st for Pharo

by stephane ducasse

Thanks a lot :) ! On Jan 29, 2010, at 8:50 AM, Adrian Lienhard wrote: > Hi all, > > I'm happy to announce that seasidehosting.st now supports Pharo! > > There are no special settings or configurations needed. Get a Pharo/Seaside image, for instance from www.seaside.st/download/pharo, install your application, and upload it to seasidehosting.st. > > Before, Pharo was not supported because the special VM used did not run closure images. Since many people asked for support of Pharo, we updated the VM now. It took some time, but as promised, we managed to finish it before the upcoming Pharo 1.0 release. > > I'd like to thank ESUG and netstyle.ch for their continuous support of Seasidehosting! > > Cheers, > Adrian > > ___________________ > http://www.adrian-lienhard.ch/ > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

Jan. 29, 2010

Re: [Pharo-project] video in Pharo

by StÃ©phane Ducasse

true I remember the point made by david about the effort required by the port. Stef On Jan 28, 2010, at 10:54 PM, John M McIntosh wrote: > > On 2010-01-28, at 1:21 PM, StÃ©phane Ducasse wrote: > >> there was a mpeg plugin in squeak but I do not know its status. >> >> Stef > > > That won't be offered in the 64bit variations of squeak > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > > _______________________________________________ > 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] [ANN] seasidehosting.st for Pharo

by Adrian Lienhard

Hi all, I'm happy to announce that seasidehosting.st now supports Pharo! There are no special settings or configurations needed. Get a Pharo/Seaside image, for instance from www.seaside.st/download/pharo, install your application, and upload it to seasidehosting.st. Before, Pharo was not supported because the special VM used did not run closure images. Since many people asked for support of Pharo, we updated the VM now. It took some time, but as promised, we managed to finish it before the upcoming Pharo 1.0 release. I'd like to thank ESUG and netstyle.ch for their continuous support of Seasidehosting! Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

Jan. 29, 2010