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

Re: [Pharo-project] Something I don't understand with ImageSegments

by Lukas Renggli

>> But I also fail to see why you'd get the class of one of the referenced >> objects but not Association. > > Yes, I don't understand neither. I would expect everything to be in the outPointers. All involved objects are referenced from the outside through the stack frame that is still active while creating the segment. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 9, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Matthias Berth

Hi Bill, this one works for me with the current pharo core 1.0 rc1, update upto 10505 "execute this:" Gofer new squeaksource: 'Loader'; package: 'Loader'; load. "then this" Loader new load: 'Pharo' version: '1.0-rc2.10505'. "then this" Loader new load: 'Seaside28' version: '2.8.4.2' The "Loader new load: 'Pharo' version: '1.0-rc2.10505'." loads a lot of additional pharo packages. I guess you won't need that just to get seaside working. Ask Esteban Lorenzano for details about hw this works :) Cheers Matthias 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > Two can be tired of this.Â I could just use the official Seaside images, but > I thought it might be nice to help with testing the monthly images.Â I won't > get very far with that if Seaside won't load. > > > ________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano > Martinez Peck > Sent: Saturday, January 09, 2010 4:38 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [BetaTesting] [ANN] > Pharo1.0-10505-rc1dev10.01.1 > > > > 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> >> >> Mariano, >> >> The reason I objected (and continue to do so) to clobbering the web image >> is that complete chaos of how to install things comes into play.Â Assuming >> that I know what YOU said on the subject is a stretch to say the least: try >> a search engine on the subject. >> > > I am a bit tired of this. I will answer for the last time and I hope you > understand: Do you want seaside ? > > 1) Volunteer yourself to build Web images. It is easy to ask, but what about > doing? > > 2) Take the Web Image before, analize how seaside was installed and do it by > yourself. I cannot take it more than half an hour. > > 3) Use official seaside image > > 4) Report what doesn't work with the ConfigurationOfSeaside in Metacello > mailing list so that everybody can collaborate and fix it. If you see that > mailing list, I did exactly that. Just saying "doesn't work"Â does not help. > > Cheers > > Mariano > >> >> BTW, it does not work.Â There is very little I can do until Seaside loads. >> >> Bill >> >> ________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano >> Martinez Peck >> Sent: Saturday, January 09, 2010 4:08 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] [BetaTesting] [ANN] >> Pharo1.0-10505-rc1dev10.01.1 >> >> >> >> 2010/1/9 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> >>> >>> Gofer seaside28 load >>> >> >> I didn't say that. I said: >> >> Gofer new >> Â Â Â squeaksource: 'MetacelloRepository'; >> Â Â Â package: 'ConfigurationOfSeaside28'; >> Â Â Â load. >> >> (Smalltalk at: #ConfigurationOfSeaside28) load >> >> And I also said I was not sure of this is working. >> >> Cheers >> >> Mariano >> >>> >>> does not work.Â What is the correct way to install Seaside - I can't do >>> much w/o it. >>> >>> ________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano >>> Martinez Peck >>> Sent: Saturday, January 09, 2010 3:01 PM >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Subject: Re: [Pharo-project] [BetaTesting] [ANN] >>> Pharo1.0-10505-rc1dev10.01.1 >>> >>> >>> >>> 2010/1/9 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> >>>> >>>> Hi Mariano, >>>> >>>> good job. Some feedback. >>>> >>>> The installScript has unused variables and your proxy settings exposed. >>>> Maybe this should be deleted from the final build. >>>> >>> >>> hahahahah I knew I was going to forget about that :( >>> Thanks. Some bash guru that help me to automatize this? I would like >>> something that automatically removes that from the file if it is found. >>> Can you help me Miguel ? >>> >>>> >>>> Shouldn't be this a RC 2? because there is a new build process and has >>>> nothing to do with the RC1? >>>> >>> >>> I thought about putting it RC2, actually, I was going to do that. But as >>> the PharoCore was named rc1, I din't want to name it rc2 because maybe it >>> was confusing. >>> I am not sure, thus. What do you think ? >>> >>>> >>>> Also, the changes files, shouldn't be compressed for each RC and for the >>>> final release? >>> >>> Excellent point. Do you rather to Smalltalk >> condenseChanges ?Â It can >>> be perfectly added. Right now, we are doing all this: >>> >>> >>> Â Â Â MCFileBasedRepository flushAllCaches. >>> Â Â Â MCDefinition clearInstances. >>> Â Â Â Smalltalk removeEmptyMessageCategories. >>> Â Â Â Utilities cleanseOtherworldlySteppers. >>> Â Â Â Undeclared removeUnreferencedKeys. >>> Â Â Â Categorizer sortAllCategories. >>> Â Â Â Symbol compactSymbolTable. >>> Â Â Â Smalltalk at: #ReleaseBuilderDeveloper ifPresent: [:builder | builder >>> new fixObsoleteReferences]. >>> Â Â Â RequiredSelectors initialize. >>> Â Â Â ProvidedSelectors initialize. >>> Â Â Â LocalSends initialize. >>> Â Â Â Smalltalk organization removeEmptyCategories. >>> Â Â Â SystemBrowser removeObsolete. >>> Â Â Â TheWorldMenu removeObsolete. >>> Â Â Â AppRegistry removeObsolete. >>> Â Â Â Set rehashAllSets. >>> Â Â Â Smalltalk cleanOutUndeclared. >>> Â Â Â Smalltalk garbageCollect. >>> >>> >>> Do you think something else should be addded?Â Â Maybe we can reuse >>> ScriptLoader cleanings ? >>> >>> >>>> >>>> Also, the packages.txt file talks about PharoCore1.0 (#10505). Has >>>> someone thought about the name shown in System->About: >>>> >>>> PharoCore1.0rc1 >>>> Latest update: #10505 >>>> >>>> Because this is not a PharoCore image. Shouldn't this read something >>>> like >>>> >>>> Pharo 1.0 Dev image. >>>> Based on PharoCore1.0rc1 >>>> Latest update: #10505 >>>> >>> >>> Yes, that's true. I agree. At least it was not "my falt" as it was >>> already like that. But I am agree we should change that. However, I don't >>> know how to do it. >>> Maybe something related to SystemVersion? Any help ? >>> >>> >>>> >>>> What about the disabling of software updates in the Pharo dev/web >>>> images? Will this be implemented or a careful update stream will be made >>>> in order to not break a dev image with overrides (real difficult I >>>> think). >>>> >>> >>> Maybe. But in addition, sometimes there are bugs that updating just fix >>> them. I am not sure if I want to disable. I rather warn people about it. >>> Do you know if we break some overrrides doing an update? >>> >>>> >>>> Maybe all this setup can be put in a post-script in the >>>> ConfigurationOfPharo class. >>> >>> It is. We have pre and post do its. So, no problem :) >>> >>>> >>>> That's all for now. I'm going to use this image to work the following >>>> days. >>>> >>>> >>>> Cheers and keep the good work. >>>> >>> >>> Thanks Miguel for the excellent feedback. Let's hope to build better >>> images! >>> >>> Mariano >>> >>> >>>> >>>> -- >>>> 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 >>> >>> _______________________________________________ >>> 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 >

Jan. 9, 2010

Re: [Pharo-project] Something I don't understand with ImageSegments

by Mariano Martinez Peck

On Sun, Jan 10, 2010 at 12:00 AM, Martin McClure <martin(a)hand2mouse.com>wrote: > Mariano Martinez Peck wrote: > > > > Exactly. I would expect to have only false and true in the outPointers, > > but not also the Object new. In the case of 'mariano' it is correct and > > only get false and true in the outPointers, but if I put Object new > > instead of 'mariano', in outPointers I get, true, false and that object > > I created. > > > > I don't see the difference between creating a string and an object. > > I tried your example. I see as outPointers true, false, and Object. Not > the object you created, but the class Object. > Uffff yes, you are right. Sorry, it is the class. I am blind at this time. Thanks for the tip Martin. > > But I also fail to see why you'd get the class of one of the referenced > objects but not Association. > Yes, I don't understand neither. > > Regards, > > -Martin > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 9, 2010

Re: [Pharo-project] Something I don't understand with ImageSegments

by Martin McClure

Mariano Martinez Peck wrote: > > Exactly. I would expect to have only false and true in the outPointers, > but not also the Object new. In the case of 'mariano' it is correct and > only get false and true in the outPointers, but if I put Object new > instead of 'mariano', in outPointers I get, true, false and that object > I created. > > I don't see the difference between creating a string and an object. I tried your example. I see as outPointers true, false, and Object. Not the object you created, but the class Object. But I also fail to see why you'd get the class of one of the referenced objects but not Association. Regards, -Martin

Jan. 9, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Miguel Enrique CobÃ¡ Martinez

El sÃ¡b, 09-01-2010 a las 21:00 +0100, Mariano Martinez Peck escribiÃ³: > > > 2010/1/9 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > Hi Mariano, > > good job. Some feedback. > > The installScript has unused variables and your proxy settings > exposed. > Maybe this should be deleted from the final build. > > > hahahahah I knew I was going to forget about that :( > Thanks. Some bash guru that help me to automatize this? I would like > something that automatically removes that from the file if it is > found. > Can you help me Miguel ? Maybe you can use two scripts, one for configuring the proxy and other for the gofer/metacello configuration. Then before zipping the files, delete the proxy settings one. Also, don't the settings remain configured in the image on the snapshot:andQuit message. If so, a post-script to clear the parameter is needed too. > > Shouldn't be this a RC 2? because there is a new build process > and has > nothing to do with the RC1? > > > I thought about putting it RC2, actually, I was going to do that. But > as the PharoCore was named rc1, I din't want to name it rc2 because > maybe it was confusing. > I am not sure, thus. What do you think ? I think that is good to have a RC2. Also this shows progress to the public. > > Also, the changes files, shouldn't be compressed for each RC > and for the > final release? > > Excellent point. Do you rather to Smalltalk >> condenseChanges ? It > can be perfectly added. Right now, we are doing all this: I don't know the exact message to condense changes, but if it is that then yes, should be added near the end of the other instructions. > > > MCFileBasedRepository flushAllCaches. > MCDefinition clearInstances. > Smalltalk removeEmptyMessageCategories. > Utilities cleanseOtherworldlySteppers. > Undeclared removeUnreferencedKeys. > Categorizer sortAllCategories. > Symbol compactSymbolTable. > Smalltalk at: #ReleaseBuilderDeveloper ifPresent: [:builder | > builder new fixObsoleteReferences]. > RequiredSelectors initialize. > ProvidedSelectors initialize. > LocalSends initialize. > Smalltalk organization removeEmptyCategories. > SystemBrowser removeObsolete. > TheWorldMenu removeObsolete. > AppRegistry removeObsolete. > Set rehashAllSets. > Smalltalk cleanOutUndeclared. > Smalltalk garbageCollect. > Respect to this list, and maybe this should be a ticket. Shouldn't be better to have an established message to cleanup the image on release. Something like the cleanUpForImageRelease but generalized and then, the classes that need to do something like this, they implement that message. So on release a new image version you only call something like Smalltalk cleanUpForImageRelease. and inside it search all the classes that implements the message and call them. So, your post-script becomes a single line and each package is responsible of putting inside its own cleanUpForImageRelease whatever needed to initialize itself. But well, just an idea for subsequent releases. > > Do you think something else should be addded? Maybe we can reuse > ScriptLoader cleanings ? Yes, and also the GarbageCollector parameters that John McIntosh is preparing. This must be part of Pharo 1.0 without doubts. > > > > > Also, the packages.txt file talks about PharoCore1.0 (#10505). > Has > someone thought about the name shown in System->About: > > PharoCore1.0rc1 > Latest update: #10505 > > Because this is not a PharoCore image. Shouldn't this read > something > like > > Pharo 1.0 Dev image. > Based on PharoCore1.0rc1 > Latest update: #10505 > > > Yes, that's true. I agree. At least it was not "my falt" as it was > already like that. But I am agree we should change that. However, I > don't know how to do it. > Maybe something related to SystemVersion? Any help ? > > > What about the disabling of software updates in the Pharo > dev/web > images? Will this be implemented or a careful update stream > will be made > in order to not break a dev image with overrides (real > difficult I > think). > > > Maybe. But in addition, sometimes there are bugs that updating just > fix them. I am not sure if I want to disable. I rather warn people > about it. Yes, both options have pros and cons. Pros - Can fix bugs after release - Can aply improvements to the image after release. Cons - Can mess the image of someone by overwriting some overridden method. - Can accidentally update more than intended in someone's image Should we vote? > Do you know if we break some overrrides doing an update? > > Maybe all this setup can be put in a post-script in the > ConfigurationOfPharo class. > > It is. We have pre and post do its. So, no problem :) > > > That's all for now. I'm going to use this image to work the > following > days. > > Cheers and keep the good work. > Thanks Miguel for the excellent feedback. Let's hope to build better > images! > > Mariano > Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Jan. 9, 2010

Re: [Pharo-project] Something I don't understand with ImageSegments

by Mariano Martinez Peck

On Sat, Jan 9, 2010 at 11:49 PM, Martin McClure <martin(a)hand2mouse.com>wrote: > Mariano Martinez Peck wrote: > > Hi guys: I have this little (piece) of test: > > > > > > | segment external internal root | > > > > external := 'mariano'. > > internal := true -> external. > > root := false -> internal. > > internal := nil. > > > > segment := ImageSegment new > > copyFromRoots: (Array with: root with: external) > > sizeHint: 5000 > > areUnique: true. > > > > self assert: segment outPointers size = 2. > > > > > > And that is green. > > > > However, if I change 'mariano' to Object new, I have that segment > > outPointers size is 3 instead of 2. > > > > I really don't understand why. Does someone see something ? > > > > What outPointers do you expect to be present? > Thanks for the answer Martin. I would expect just true and false. > > With my limited understanding of ImageSegment theory I would expect > there to be no outPointers in this example, because there are no > references from objects in the ImageSegment to objects outside the > ImageSegment, except for the well-known objects true and false. > > Exactly. I would expect to have only false and true in the outPointers, but not also the Object new. In the case of 'mariano' it is correct and only get false and true in the outPointers, but if I put Object new instead of 'mariano', in outPointers I get, true, false and that object I created. I don't see the difference between creating a string and an object. Cheers Mariano > Regards, > > -Martin > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 9, 2010

Re: [Pharo-project] Something I don't understand with ImageSegments

by Martin McClure

Mariano Martinez Peck wrote: > Hi guys: I have this little (piece) of test: > > > | segment external internal root | > > external := 'mariano'. > internal := true -> external. > root := false -> internal. > internal := nil. > > segment := ImageSegment new > copyFromRoots: (Array with: root with: external) > sizeHint: 5000 > areUnique: true. > > self assert: segment outPointers size = 2. > > > And that is green. > > However, if I change 'mariano' to Object new, I have that segment > outPointers size is 3 instead of 2. > > I really don't understand why. Does someone see something ? > What outPointers do you expect to be present? With my limited understanding of ImageSegment theory I would expect there to be no outPointers in this example, because there are no references from objects in the ImageSegment to objects outside the ImageSegment, except for the well-known objects true and false. Regards, -Martin

Jan. 9, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Lukas Renggli

> Gofer seaside28 load > > does not work.Â What is the correct way to install Seaside - I can't do much > w/o it. "Does not work" doesn't say much. Can you be more specific? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 9, 2010

[Pharo-project] Issue 1767: Method Finder gives UndefinedObject error on search

by Francisco Ortiz PeÃ±aloza

http://code.google.com/p/pharo/issues/detail?id=1767&sort=-id&colspec=ID%20… Pharo image: Pharo-core Pharo core version: PharoCore1.1ALPHA Latest update: #11146 Virtual machine used: Squeak 4.2.2beta1U | Cocoa Squeak 5.0.0b9 64*32 Steps to reproduce: 1. Open method finder 2. Type 'drawn: in:' (note there's an space between both keywords). 3. Hit <enter> :p Could be somewhat related to #1098 (see http://code.google.com/p/pharo/issues/detail? id=1098) But imo stack traces differ. Francisco

Jan. 9, 2010

[Pharo-project] Something I don't understand with ImageSegments

by Mariano Martinez Peck

Hi guys: I have this little (piece) of test: | segment external internal root | external := 'mariano'. internal := true -> external. root := false -> internal. internal := nil. segment := ImageSegment new copyFromRoots: (Array with: root with: external) sizeHint: 5000 areUnique: true. self assert: segment outPointers size = 2. And that is green. However, if I change 'mariano' to Object new, I have that segment outPointers size is 3 instead of 2. I really don't understand why. Does someone see something ? Thanks Mariano

Jan. 9, 2010