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

[Pharo-project] Fwd: [Esug-list] Looking for Smalltalkers
by StÃ©phane Ducasse Aug. 19, 2010

Aug. 19, 2010

Begin forwarded message: > From: "Georg Heeg" <georg(a)heeg.de> > Date: August 19, 2010 12:33:15 PM GMT+02:00 > To: "ESUG Members" <esug-list(a)lists.esug.org> > Subject: [Esug-list] Looking for Smalltalkers > Reply-To: esug-list(a)lists.esug.org > > Dear Smalltalkers, > > We are looking to enlarge our Smalltalk team in KÃ¶then (Anhalt) or Dortmund. > > Georg Heeg > > Georg Heeg eK, Dortmund und KÃ¶then, HR Dortmund A 12812 > Tel. +49-3496-214328, Fax +49-3496-214712 > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

1 0

[Pharo-project] Wiki spam experience
by Schwab,Wilhelm K Aug. 19, 2010

Aug. 19, 2010

Hello all, Are there any tricks to running a wiki and not ending up a directory of Nigerian ecomomic scams and pornography? Is moderation the only way to do it, or can it be more automatic? Bill

3 3

[Pharo-project] CogVM binaries!!! {WAS} Re: [squeak-dev] Re: CogVM on the Mac
by Mariano Martinez Peck Aug. 19, 2010

Aug. 19, 2010

On Thu, Aug 19, 2010 at 6:23 AM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > > > On Wed, Aug 18, 2010 at 8:14 PM, Chris Cunnington < > smalltalktelevision(a)gmail.com> wrote: > >> Wow. Have I been looking in the wrong place. >> I've been downloading trunk build files from svn listed on the >> squeakvm.org/unix pages, but *sigh* I didn't see the trove of stuff you >> just pointed out. And there are specific instructions for Mac and Unix >> builds. This is what I should be looking at. Thank you for pointing there. >> > > For folks' convenience I've just put up some unofficial builds (essentially > the same builds I use for testing) under > http://www.mirandabanda.org/files/Cog/VM > > > HTH > Hi Eliot. This, this HELPS A LOT. This is awesome. Seriously. This is really cool. Now we could start to create a Pharo one click based on Cog. Having the binaries will increase people using it, reporting bugs, and submitting fixes. Two questions: 1) why "unofficial" builds? 2) Do these binaries include the fixes from henrik to avoid the crash tha happens sometime? Thanks Mariano > Eliot > > >> Chris >> >> >> >> > > > >

7 8

[Pharo-project] Senders of #haltOnce
by Lukas Renggli Aug. 19, 2010

Aug. 19, 2010

I discovered some senders of #haltOnce in Pharo 1.1 morphic code as I was using this functionality to debug my own code. I submitted a fix: http://code.google.com/p/pharo/issues/detail?id=2833 Also I discovered countless senders of #halt and friends in library code and tests. This is really bad for continuous integration and for deploying images, because they open debuggers. All these senders should be changed to throw an error or fail the test in some controllable fashion. Lukas -- Lukas Renggli www.lukas-renggli.ch

5 5

Re: [Pharo-project] SocketStream enh
by LUIS E QUIJANO Aug. 19, 2010

Aug. 19, 2010

Stef, I have been testing your SocketStream code. So far so good. I noticed that if accidentally a SmallInteger versus a CharacterOrByte parameter is used in the method SocketStream>>upTo:, the environment goes into a degraded state that persists until the original instance of SocketStream gets closed. For example, no more new Socket connects. After closing the original instance of SocketStream, the environment "seems" to be back to "normal". A simple example for reproducing the "bad parameter" situation is below. Hope this helps, Luis -=-=- Luis Quijano quijano(a)panasoft.com -=-=- | hostName portNumber hostIP ss data | hostName := '10.10.10.100'. portNumber := 10001. hostIP := NetNameResolver addressForName: hostName timeout: 20. ss := SocketStream openConnectionToHost: hostIP port: portNumber. Transcript show: '---------- Connecting ----------'; cr; show: 'hostName = ' , hostName; cr; show: 'hostIP = ' , hostIP printString; cr; show: 'portNumber = ' , portNumber printString; cr. "data := ss upTo: (Character value: 68)." "Good parameter" data := ss upTo: 68. "Bad parameter" Transcript show: 'Data received: '; show: data; cr. ss close. Transcript show: '---------- Connection Closed ----------'; cr. data inspect. ===== At 11:43 AM 8/8/2010, you wrote: >Hi lukas and others.... > >I will integrate the following SocketStream tests and before I would >love to see if this >does not impact seaside > >http://code.google.com/p/pharo/issues/detail?id=2767 > >Stef >_______________________________________________ >Pharo-project mailing list >Pharo-project(a)lists.gforge.inria.fr >http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

[Pharo-project] Questions about SRP
by Mariano Martinez Peck Aug. 19, 2010

Aug. 19, 2010

Hi folks/Paul. First, sorry for the cross-posting. Let me know if I should ask this in another place. I am interested in SRP and to understand the differences with SmartRefStream, ImageSegment, SIXX, parcels, etc. First I would like to find as much info as possible. Right now I found: http://techsupport.gemstone.com/entries/175881-srp-3-1-007-0 http://sourceforge.net/projects/srp/ http://map.squeak.org/accountbyid/94ec671f-6615-4ece-9ab0-5d4addc3be8d/pack… These seems to be dead: http://www.ccse.kfupm.edu.sa/~sohel/IMPP/references/About+State+Replication… http://www.whysmalltalk.com/Smalltalk_Solutions/sts2004/pdf/Baumann.pdf And....class side methods #documentation is there something else? Now, my questions: 1) Does SRP supports cycles in my subgraph? If true, how do you achieve that? 2) What happens with objects like nil, true, false, or any other object that has to be unique in Smalltalk. I mean, how can I make sure that when I load the subgraph in another image, I won't have duplicates of nil, true, etc ? 3) Does it provide a way to fix problems like having to rehash Set instances or things like that? 4) Does it supports class reshape? suppose I put in the file objects of a certain class and then I load the file in another image where that class has different shape (re-order of instVar, rename, new insVar, etc...). If true, how do you achieve that? 5) Do you handle BlockClosure (or BlockCOntext), MethodCoontext, CompiledMethods and things like that ? Thanks a lot for any hints you can give me. Mariano

1 0

[Pharo-project] We want your photo
by laurent laffont Aug. 19, 2010

Aug. 19, 2010

for http://pharo-project.org/community/contributors and a little description of your Pharo usage and / or contributions. Thanks, <http://pharo-project.org/community/contributors> Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

5 8

[Pharo-project] DropList/EditableDropList fixes
by Gary Chambers Aug. 19, 2010

Aug. 19, 2010

See http://code.google.com/p/pharo/issues/detail?id=2821 Regards, Gary

3 3

Aug. 19, 2010

12099 ----- - Removed possiblyChanged sent but not implemented methods in NewEditor. Issue 2827: remove all the senders of possiblyChanged - Issue 2829: Improve Watery2 theme drop list appearance. Thanks Gary Chambers. Progress is a step at a time and a lot of time. S. Ducasse the Wise

1 0

[Pharo-project] FW: FW: [Seaside] Changes file too big
by Robert Sirois Aug. 19, 2010

Aug. 19, 2010

From: watchlala(a)hotmail.com To: watchlala(a)hotmail.com Subject: RE: [Pharo-project] FW: [Seaside] Changes file too big Date: Wed, 18 Aug 2010 20:56:37 -0600 Ok... I was running "pharo1.0-10505-rc1dev10.01.2". I decided to time machine back to last night, so I only lost a couple hours of work. Somehow Gofer, maybe? added tons of lines of random code to all the methods in the packages I was trying to save out via Monticello and erased all the code I had in them. If you need more information I can pull the image out of time machine from this morning again. Thanks,RS How do I clear the changes or make the max bigger? I would think it would be easy. From: watchlala(a)hotmail.com To: pharo-project(a)lists.gforge.inria.fr Subject: RE: [Pharo-project] FW: [Seaside] Changes file too big Date: Wed, 18 Aug 2010 17:22:46 -0600 I can't say for sure until I get home but it was the something dot 505 from a little earlier this year. Thanks, RS Oh, also.. that condenseChanges messed up monticello, too. > From: stephane.ducasse(a)inria.fr > Date: Wed, 18 Aug 2010 22:58:32 +0200 > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] FW: [Seaside] Changes file too big > > Oops. > Robert can you tell us which version you are using? > > Stef > > > How do I clear my changes file? Smalltalk condenseChanges. just brings up a PositionalStream error. > > > > Thanks, RS > > _______________________________________________ > > 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