- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Monticello connecting to ftp repo on non-standard port

by Michael Rueger

Adrian Lienhard wrote: > Thanks, Mike, > > is http://code.google.com/p/pharo/issues/detail?id=794 a duplicate? no, that's a different issue. Need to fire up my virtualbox Ubuntu now :-) Michael

June 16, 2009

Re: [Pharo-project] Monticello connecting to ftp repo on non-standard port

by Adrian Lienhard

Thanks, Mike, is http://code.google.com/p/pharo/issues/detail?id=794 a duplicate? Adrian On Jun 16, 2009, at 11:40 , Michael Rueger wrote: > Pat Maddox wrote: >> Okay per http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg08133.ht… >> all I had to do was change NetNameResolver class >> useOldNetwork to >> > > A real fix is attached here: > http://code.google.com/p/pharo/issues/detail?id=892 > >>> above (in the caller/message-sender) where #port: is sent, insert a >>> asSocketAddress (or something like that) > > This actually doesn't work as I found out. > >>> Also, at least a few weeks back, I was still needing to return >>> "true" >>> in net-name-resolver method #useOldSockets (? or Address?) > > That is causing it to work as it circumvents the problematic code > altogether. > > Michael > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 16, 2009

[Pharo-project] Problems loading Squeak Map

by Frank Church

Hi, I am trying to fix the SqueakMap loader in Seaside-2.8.4.app image. Squeak Map Loader shows a blank list with (0/0) The about dialog give this information Pharo0.1 latest update #10318 Trying 'Configuration->update from server rresults in a message not understood error. In the meantime I am using System->software update in the hope that it does the same thing The image is also displaying some bugs or what looks like unimplemented menu options. Are there commands I can execute to fix Squeak Map to get it to run properly? BTW it is because want to add the Universes to setup Gemstone Tools Client, but I don't mind learning other things along the way. Frank

June 16, 2009

Re: [Pharo-project] Monticello connecting to ftp repo on non-standard port

by Michael Rueger

Pat Maddox wrote: > Okay per http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg08133.ht… > all I had to do was change NetNameResolver class >> useOldNetwork to > A real fix is attached here: http://code.google.com/p/pharo/issues/detail?id=892 >> above (in the caller/message-sender) where #port: is sent, insert a >> asSocketAddress (or something like that) This actually doesn't work as I found out. >> Also, at least a few weeks back, I was still needing to return "true" >> in net-name-resolver method #useOldSockets (? or Address?) That is causing it to work as it circumvents the problematic code altogether. Michael

June 16, 2009

[Pharo-project] a test

by StÃ©phane Ducasse

June 16, 2009

Re: [Pharo-project] [ANN] MouseOverHandler refactoring

by Hernan Wilkinson

You are right, it is very difficult to get to the bottom of the original problem and a lot of morph experience is needed. As I suggested before, that error could happen because: 1) There are multiple processes modifying morph state 2) The same morph is visited more than once to handle the mouse over event (I don't know if this is possible). Hernan. 2009/6/15 Gary Chambers <gazzaguru2(a)btinternet.com> > Which, of course, doesn't get to the bottom of the original problem. > That being, why there would be multiple processes (rather than just UI > process) modifying any Morph state... > > Regards, Gary > > ----- Original Message ----- > *From:* Hernan Wilkinson <hernan.wilkinson(a)gmail.com> > *To:* Pharo-project(a)lists.gforge.inria.fr > *Sent:* Monday, June 15, 2009 6:51 PM > *Subject:* Re: [Pharo-project] [ANN] MouseOverHandler refactoring > > Done, issue 889 > > On Sat, Jun 13, 2009 at 5:48 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > >> >> On Jun 13, 2009, at 01:59 , Hernan Wilkinson wrote: >> >> > ups! you are write!! sorry about that, I realize I did not put the >> > name of >> > the file :-)The file name is: Morphic-HernanWilkinson.327.mcz >> > >> > About the issue tracker, the error that Stef point me to is >> > http://code.google.com/p/pharo/issues/detail?id=86 in his mail >> > >> http://lists.gforge.inria.fr/pipermail/pharo-project/2009-June/009517.html >> > but >> > the description does not macth with the error I also fix. >> > Do you think I should open a new defect? >> >> Yes, I think that would be best. >> >> Cheers, >> Adrian >> >> > >> > On Fri, Jun 12, 2009 at 5:37 PM, Adrian Lienhard <adi(a)netstyle.ch> >> > wrote: >> > >> >> Hi Hernan, >> >> >> >> On Jun 12, 2009, at 21:55 , Hernan Wilkinson wrote: >> >> >> >>> I uploaded to the pharo inbox repository... is that right? >> >> >> >> Yes. But additionally it would be good to note which file(s) you >> >> uploaded in the issue tracker. Like this we can track changes. If no >> >> report exists yet, just create a new one. >> >> >> >> Thanks, >> >> Adrian >> >> >> >>> The only way to >> >>> test it that I found of is just to install it and play with the >> >>> mouse... if >> >>> you do not have a debugger, it means it is working :-) >> >>> >> >>> On Fri, Jun 12, 2009 at 2:47 PM, Damien Cassou < >> damien.cassou(a)gmail.com >> >>>> wrote: >> >>> >> >>>> 2009/6/12 Hernan Wilkinson <hernan.wilkinson(a)gmail.com>: >> >>>>> Hope you like it. >> >>>> >> >>>> Where can we find it? >> >>>> How to test it? >> >>>> >> >>>> >> >>>> -- >> >>>> Damien Cassou >> >>>> http://damiencassou.seasidehosting.st >> >>>> >> >>>> "Lambdas are relegated to relative obscurity until Java makes them >> >>>> popular by not having them." James Iry >> >>>> >> >>>> _______________________________________________ >> >>>> 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 >> >> >> _______________________________________________ >> 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 >

June 16, 2009

Re: [Pharo-project] Monticello connecting to ftp repo on non-standard port

by Pat Maddox

Okay per http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg08133.ht… all I had to do was change NetNameResolver class >> useOldNetwork to return true. Thanks for the pointer. I hope your surgery and recovery go well... Pat On Mon, Jun 15, 2009 at 8:03 AM, Cameron Sanders<camsanders01(a)roadrunner.com> wrote: > This defect and its fix has been documented -- see the comments I > added to the bug-log. I am using Monticello on a Mac with FTP. (I do > not specify the port.) Do a search of the defects and you'll see my > comments. > > You need to add a message... but... to be honest, I've had 3 hours of > sleep, no water in many hours, and I'm leaving for the hospital for > surgery in two minutes... so i can't look it up. > > above (in the caller/message-sender) where #port: is sent, insert a > asSocketAddress Â (or something like that) > > Also, at least a few weeks back, I was still needing to return "true" > in net-name-resolver method #useOldSockets (? or Address?) > > again, my apologies for not being more clear. > > -Cam > On Jun 15, 2009, at 9:35 AM, Pat Maddox wrote: > >> On Mon, Jun 15, 2009 at 6:25 AM, Damien >> Cassou<damien.cassou(a)gmail.com> wrote: >>> On Mon, Jun 15, 2009 at 3:22 PM, Pat Maddox<pat.maddox(a)gmail.com> >>> wrote: >>>> Image # is 10324. Â vm is squeak 4.11beta2u downloaded from the pharo >>>> site. Â I don't know how to copy and paste the log trace. Â When I >>>> click >>>> Open from MC the error window comes up. Â If I try to select text >>>> from >>>> there (which works in squeak, afaik) it brings up the debugger. >>>> From >>>> there I can see the trace but can't copy and paste it. Â What am I >>>> missing? >>> >>> you should check for a debug.log file >> >> Alright, here's the log for a few frames back. Â I think that should be >> enough, please let me know if you need more info >> >> >> MessageNotUnderstood: ByteArray>>port: >> 15 June 2009 6:29:29 am >> >> VM: Mac OS - intel - 1057 - Squeak3.8.1 of '28 Aug 2006' [latest >> update: #6747] Squeak VM 4.1.1b2 >> Image: Pharo0.1 [Latest update: #10324] >> >> SecurityManager state: >> Restricted: false >> FileAccess: true >> SocketAccess: true >> Working Dir /Users/padillac/code/dogadopt >> Trusted Dir /foobar/tooBar/forSqueak/bogus >> Untrusted Dir /Users/padillac/Library/Preferences/Squeak/Internet/My >> Squeak >> >> ByteArray(Object)>>doesNotUnderstand: #port: >> Â Â Â Receiver: #[173 45 239 88] >> Â Â Â Arguments and temporary variables: >> Â Â Â Â Â Â Â aMessage: Â Â Â port: 47682 >> Â Â Â Â Â Â Â exception: Â Â Â MessageNotUnderstood: ByteArray>>port: >> Â Â Â Â Â Â Â resumeValue: Â Â nil >> Â Â Â Receiver's instance variables: >> #[173 45 239 88] >> >> Socket>>connectTo:port: >> Â Â Â Receiver: a Socket[unconnected] >> Â Â Â Arguments and temporary variables: >> Â Â Â Â Â Â Â hostAddress: Â Â #[173 45 239 88] >> Â Â Â Â Â Â Â port: Â 47682 >> Â Â Â Receiver's instance variables: >> Â Â Â Â Â Â Â semaphore: Â Â Â a Semaphore() >> Â Â Â Â Â Â Â socketHandle: Â #[254 248 53 74 0 0 0 0 144 91 48 22] >> Â Â Â Â Â Â Â readSemaphore: Â a Semaphore() >> Â Â Â Â Â Â Â writeSemaphore: Â Â Â Â a Semaphore() >> Â Â Â Â Â Â Â primitiveOnlySupportsOneSemaphore: Â Â Â false >> >> FTPClient>>openDataSocket:port: >> Â Â Â Receiver: a FTPClient >> Â Â Â Arguments and temporary variables: >> Â Â Â Â Â Â Â remoteHostAddress: Â Â Â #[173 45 239 88] >> Â Â Â Â Â Â Â dataPort: Â Â Â 47682 >> Â Â Â Receiver's instance variables: >> Â Â Â Â Â Â Â stream: Â Â Â Â SocketStream[inbuf:4kb/outbuf:4kb] >> Â Â Â Â Â Â Â connectInfo: Â Â a >> Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix- >> metan...etc... >> Â Â Â Â Â Â Â lastResponse: Â '227 Entering Passive Mode (173,45,239,88,186,66).' >> Â Â Â Â Â Â Â pendingResponses: Â Â Â nil >> Â Â Â Â Â Â Â progressObservers: Â Â Â nil >> Â Â Â Â Â Â Â responseCode: Â 227 >> Â Â Â Â Â Â Â dataSocket: Â Â a Socket[unconnected] >> >> FTPClient>>openPassiveDataConnection >> Â Â Â Receiver: a FTPClient >> Â Â Â Arguments and temporary variables: >> Â Â Â Â Â Â Â portInfo: Â Â Â '173,45,239,88,186,66' >> Â Â Â Â Â Â Â list: Â an OrderedCollection('173' '45' '239' '88' '186' '66') >> Â Â Â Â Â Â Â dataPort: Â Â Â 47682 >> Â Â Â Â Â Â Â remoteHostAddress: Â Â Â #[173 45 239 88] >> Â Â Â Receiver's instance variables: >> Â Â Â Â Â Â Â stream: Â Â Â Â SocketStream[inbuf:4kb/outbuf:4kb] >> Â Â Â Â Â Â Â connectInfo: Â Â a >> Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix- >> metan...etc... >> Â Â Â Â Â Â Â lastResponse: Â '227 Entering Passive Mode (173,45,239,88,186,66).' >> Â Â Â Â Â Â Â pendingResponses: Â Â Â nil >> Â Â Â Â Â Â Â progressObservers: Â Â Â nil >> Â Â Â Â Â Â Â responseCode: Â 227 >> Â Â Â Â Â Â Â dataSocket: Â Â a Socket[unconnected] >> >> FTPClient>>getDirectory >> Â Â Â Receiver: a FTPClient >> Â Â Â Arguments and temporary variables: >> Â Â Â Â Â Â Â dirList: Â Â Â Â nil >> Â Â Â Receiver's instance variables: >> Â Â Â Â Â Â Â stream: Â Â Â Â SocketStream[inbuf:4kb/outbuf:4kb] >> Â Â Â Â Â Â Â connectInfo: Â Â a >> Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix- >> metan...etc... >> Â Â Â Â Â Â Â lastResponse: Â '227 Entering Passive Mode (173,45,239,88,186,66).' >> Â Â Â Â Â Â Â pendingResponses: Â Â Â nil >> Â Â Â Â Â Â Â progressObservers: Â Â Â nil >> Â Â Â Â Â Â Â responseCode: Â 227 >> Â Â Â Â Â Â Â dataSocket: Â Â a Socket[unconnected] >> >> _______________________________________________ >> 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 > -- (415) 297-8028 http://www.patmaddox.com Twitter: @patmaddox GitHub: http://github.com/pat-maddox

June 15, 2009

Re: [Pharo-project] CompiledMethod and MethodReference

by StÃ©phane Ducasse

On Jun 15, 2009, at 4:42 PM, David RÃ¶thlisberger wrote: > >>>> I was playing with compiledMethod and MethodReference and it >>>> would be >>>> great if they could be more >>>> polymorphic: >>>> >>>> MethodReference>>methodClass >>>> ^ self actualClass >>> >>> It will probably not do any harm, but why should a MethodReference >>> be >>> polymorphic with a compiled method? >> >> >> like that we have a better system with less iskindof and methodClass >> vs. actualClass >> a MethodReference is a kind of wrapper for compiled method at the >> level of the tools >> so we would all gain having a good intersection between the two. > > yes, absolutely, good idea. > > Also useful: > > MethodReference>>selector > ^self methodSymbol > > >>>> I was also thinking that it would be nice to have the package >>>> associated with the MethodReference >>>> eg: >>>> >>>> (Character>>#escapeEntities) package >>>> >>>> -> PackageInfo-Base >>>> >>>> What do you think about that? > > yes, makes sense. > But this would be CompiledMethod here, not MethodReference, IMO? yes :) but we should do both :) and may be one day we will not need MethodReference :) Stef > > David > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 15, 2009

Re: [Pharo-project] [ANN] MouseOverHandler refactoring

by Gary Chambers

Which, of course, doesn't get to the bottom of the original problem. That being, why there would be multiple processes (rather than just UI process) modifying any Morph state... Regards, Gary ----- Original Message ----- From: Hernan Wilkinson To: Pharo-project(a)lists.gforge.inria.fr Sent: Monday, June 15, 2009 6:51 PM Subject: Re: [Pharo-project] [ANN] MouseOverHandler refactoring Done, issue 889 On Sat, Jun 13, 2009 at 5:48 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: On Jun 13, 2009, at 01:59 , Hernan Wilkinson wrote: > ups! you are write!! sorry about that, I realize I did not put the > name of > the file :-)The file name is: Morphic-HernanWilkinson.327.mcz > > About the issue tracker, the error that Stef point me to is > http://code.google.com/p/pharo/issues/detail?id=86 in his mail > http://lists.gforge.inria.fr/pipermail/pharo-project/2009-June/009517.html > but > the description does not macth with the error I also fix. > Do you think I should open a new defect? Yes, I think that would be best. Cheers, Adrian > > On Fri, Jun 12, 2009 at 5:37 PM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: > >> Hi Hernan, >> >> On Jun 12, 2009, at 21:55 , Hernan Wilkinson wrote: >> >>> I uploaded to the pharo inbox repository... is that right? >> >> Yes. But additionally it would be good to note which file(s) you >> uploaded in the issue tracker. Like this we can track changes. If no >> report exists yet, just create a new one. >> >> Thanks, >> Adrian >> >>> The only way to >>> test it that I found of is just to install it and play with the >>> mouse... if >>> you do not have a debugger, it means it is working :-) >>> >>> On Fri, Jun 12, 2009 at 2:47 PM, Damien Cassou <damien.cassou(a)gmail.com >>>> wrote: >>> >>>> 2009/6/12 Hernan Wilkinson <hernan.wilkinson(a)gmail.com>: >>>>> Hope you like it. >>>> >>>> Where can we find it? >>>> How to test it? >>>> >>>> >>>> -- >>>> Damien Cassou >>>> http://damiencassou.seasidehosting.st >>>> >>>> "Lambdas are relegated to relative obscurity until Java makes them >>>> popular by not having them." James Iry >>>> >>>> _______________________________________________ >>>> 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 _______________________________________________ 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

June 15, 2009

Re: [Pharo-project] [ANN] MouseOverHandler refactoring

by Hernan Wilkinson

Done, issue 889 On Sat, Jun 13, 2009 at 5:48 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > > On Jun 13, 2009, at 01:59 , Hernan Wilkinson wrote: > > > ups! you are write!! sorry about that, I realize I did not put the > > name of > > the file :-)The file name is: Morphic-HernanWilkinson.327.mcz > > > > About the issue tracker, the error that Stef point me to is > > http://code.google.com/p/pharo/issues/detail?id=86 in his mail > > > http://lists.gforge.inria.fr/pipermail/pharo-project/2009-June/009517.html > > but > > the description does not macth with the error I also fix. > > Do you think I should open a new defect? > > Yes, I think that would be best. > > Cheers, > Adrian > > > > > On Fri, Jun 12, 2009 at 5:37 PM, Adrian Lienhard <adi(a)netstyle.ch> > > wrote: > > > >> Hi Hernan, > >> > >> On Jun 12, 2009, at 21:55 , Hernan Wilkinson wrote: > >> > >>> I uploaded to the pharo inbox repository... is that right? > >> > >> Yes. But additionally it would be good to note which file(s) you > >> uploaded in the issue tracker. Like this we can track changes. If no > >> report exists yet, just create a new one. > >> > >> Thanks, > >> Adrian > >> > >>> The only way to > >>> test it that I found of is just to install it and play with the > >>> mouse... if > >>> you do not have a debugger, it means it is working :-) > >>> > >>> On Fri, Jun 12, 2009 at 2:47 PM, Damien Cassou < > damien.cassou(a)gmail.com > >>>> wrote: > >>> > >>>> 2009/6/12 Hernan Wilkinson <hernan.wilkinson(a)gmail.com>: > >>>>> Hope you like it. > >>>> > >>>> Where can we find it? > >>>> How to test it? > >>>> > >>>> > >>>> -- > >>>> Damien Cassou > >>>> http://damiencassou.seasidehosting.st > >>>> > >>>> "Lambdas are relegated to relative obscurity until Java makes them > >>>> popular by not having them." James Iry > >>>> > >>>> _______________________________________________ > >>>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 15, 2009