- Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: [squeak-dev] ditching Monticello objects.

by StÃ©phane Ducasse

Begin forwarded message: > From: John M McIntosh <johnmci(a)smalltalkconsulting.com> > Date: February 12, 2009 6:13:50 AM CEST > To: Keith Hodges <keith_hodges(a)yahoo.co.uk> > Cc: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > Subject: Re: [squeak-dev] ditching Monticello objects. > Reply-To: johnmci(a)smalltalkconsulting.com, The general-purpose > Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > > Ok, well I did > > I've been collecting lists of pruning methods so.. > > ScrollBar initializeImagesCache. > GradientFillStyle initPixelRampCache. > NaturalLanguageFormTranslator classPool at: #CachedTranslations > put: nil. > NaturalLanguageTranslator resetCaches. > PartsBin clearThumbnailCache. > PaintBoxMorph classPool at: #ColorChart put: nil. > PaintBoxMorph classPool at: #Prototype put: nil. > ImageMorph classPool at: #DefaultForm put: (Form extent: 1@1 depth: > 1). > Utilities classPool at: #ScrapsBook put: nil. > Project allInstancesDo: [ :each | each setThumbnail: nil ]. > ScriptingSystem stripGraphicsForExternalRelease. > ProjectHistory currentHistory initialize. > Utilities zapUpdateDownloader. > Smalltalk forgetDoIts. > Behavior flushObsoleteSubclasses. > CommandHistory allInstancesDo: #initialize. > ChangeSorter removeChangeSetsNamedSuchThat: [ :each | true ]. > ChangeSet resetCurrentToNewUnnamedChangeSet. > MethodChangeRecord allInstancesDo: [ :x | x noteNewMethod: nil ]. > RequiredSelectors initialize. > ProvidedSelectors initialize. > LocalSends initialize. > SendCaches initializeAllInstances. > Utilities cleanseOtherworldlySteppers. > Smalltalk organization removeEmptyCategories. > Browser initialize. > SMSqueakMap default purge. > SystemBrowser removeObsolete. > TheWorldMenu removeObsolete. > AppRegistry removeObsolete. > FileServices removeObsolete. > MCFileBasedRepository flushAllCaches. > MCDefinition clearInstances. > Undeclared removeUnreferencedKeys. > Smalltalk flushClassNameCache. > 3 timesRepeat: [ Smalltalk garbageCollect. Symbol > compactSymbolTable ]. > Set rehashAllSets. > Smalltalk garbageCollect. > > > > I added these ones. > > ChangeSorter initializeChangeSetCategories. > MCWorkingCopy inspect. > MCRepositoryGroup inspect. > MCCacheRepository inspect. > > and cleaned up the class instance variables & any class vars via the > inspect. > > That removed all the MC packages and MC http repositories from the > MC Browser > > gave me back 4 megabytes of image space. > > Well brute force, still 4 mb wonderful to get back this late in the > project. > > > On 11-Feb-09, at 6:18 PM, Keith Hodges wrote: > >> John M McIntosh wrote: >>> I'm building an image for a limited memory hardware platform. >>> >>> At the point here where I want to *deploy* things and I can see that >>> various parts of Monticello >>> are consuming well over a megabyte of memory to retain MCVersionInfo >>> instances, MCMethodDefinition(s), time stamps, uuids, etc etc >>> >>> I'm wondering if anyone has some code to strip all that out thus >>> returning I suspect a couple of MB back for more constructive usage? >> You may want to look into the cleanUp/freeSomeSpace conventions. >> MC1.5 >> has a few implemented. There are many more available from >> http://bugs.squeak.org/view.php?id=7244 >> >> Keith > > -- > = > = > = > = > = > ====================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > = > = > = > = > = > ====================================================================== > > > > >

Feb. 12, 2009

Re: [Pharo-project] Workspace API

by StÃ©phane Ducasse

On Feb 11, 2009, at 7:34 PM, Keith Hodges wrote: > StÃ©phane Ducasse wrote: >> Where? When? >> Keith >> in the long run it would be nice that yu do not bash us >> systematically. >> Yes we have a different way of working but normally this is often by >> pure lack of time or information >> that we do not check what exist. >> >> Stef >> > I was concerned to find code in Pier that did not seem to be > compatible > with squeak, while I thought that the Workspace issue had come up > before. no idea. > Your different way of working..... as I see it: > > You want more tests, you develop more tests, you add more tests to the > image. Are those tests useful to the rest of the squeak community? No. > Should they be? YES. > > If there was a way of marking those tests that are pharo only tests, > as > such, and also marking those tests that should work in squeak. Then > the > squeak/pharo communities could use one testing package for all squeak > images, and pharo. may be > So to enable this to happen you need to think about testing in a > broader > sense and you need improved tools to handle it, and you need to > develop > or assess those tools FIRST. Yes. > hmm, so August 2006, I thought this through, that to support diversity > in the squeak community we needed something like that, and > SUnit-improved was the result. That was its purpose, to support > forks of > squeak, I believe in forking squeak.... I know I should have a look at SUnit-Improved but my time is limited > All the tools I have worked on for 2 years are to enable working with > diverse images, and to facilitate packages to work in different > images. > Thus reducing the dependency upon a specific kernel-image and thus > releasing the kernel-image to be improved. > > What I don't believe in was the pharo approach of going your own way > WITHOUT considering anyone else, to the extent that you ignore all of > the extensive work that has been carried out to provide tools that > would > enable you to participate. The main goal of the 3.11 effort hasn't > been > a particular image, but a tool set, and a process, that would enable > folks to work on diverse projects, while considering each other. Our goal is to make progress. Squeak is dying don't see it? > And you are ignoring those tools, because you dont see them as > important. No. The problem is the noise ratio with them (nul pattern, bad formatting, extensive extensions....) > I cant work out why you dont see them as important is because > you have sucessfully harnessed a lot of enthusiasm for improving > squeak. > YET you dont have a process for using that enthusiam effectively. You > still have the same old bottlenecked controlled process where there is > no actual plan (you do what you feel like when you get up in the > morning), and two people get to hack at the image day and night and > everyone else is contributing to a moving target. I would love to have a buildServer and also run automatically SmallLint rules on the code now either pharo does not exist because we build those tools or pharo exist. So we are going slowly on both side. I was hoping to get such buildserver and this is why we started to write on Installer (and you know that this is not only for pharo so you should be happy). Now you should ask yourself the question why people are not all using your tool extensions. Conservatism? stupidity? lack of time? lack of trust? Dont'care? Stef

Feb. 12, 2009

Re: [Pharo-project] Workspace API

by StÃ©phane Ducasse

About MC1.5 here is what I received as a private email. So I imagine that the person is a bit too negative too but you can understand that we pay attention and need time to ***really*** look at it. I hope you don't include Monticello 1.5 in Pharo. All code that we have seen so far from Keith cases trouble. I have nothing to support this except the people reporting problems with Monticello 1.5. Stef On Feb 11, 2009, at 6:55 PM, Keith Hodges wrote: > Alexandre Bergel wrote: >> I was wondering, how many people saved their workspace content in a >> file? >> >> Cheers, >> Alexandre >> > MC1.5 supports files so if you want to manage scripts and readmes > having > a workspace that knows its file, is a good idea. > > Also Bob wants a way to (optionally) show you the script that it > used to > build the image. > > http://bugs.squeak.org/view.php?id=5669 > > Keith > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 12, 2009

Re: [Pharo-project] Issue #505

by StÃ©phane Ducasse

thanks a lot! Stef On Feb 11, 2009, at 5:28 PM, HernÃ¡n Morales Durand wrote: > http://code.google.com/p/pharo/issues/detail?id=505 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 12, 2009

Re: [Pharo-project] Pharo Smalltalk now also on Nabble

by StÃ©phane Ducasse

Thanks ! Stef On Feb 11, 2009, at 10:46 PM, Geert wrote: > > The Pharo Smalltalk mailing list should now also be available on > http://n2.nabble.com/Pharo-Smalltalk-f2305563.html www.nabble.com . > -- > View this message in context: http://n2.nabble.com/Pharo-Smalltalk-now-also-on-Nabble-tp2311636p2311636.h… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 12, 2009

Re: [Pharo-project] Issue #505

by Damien Cassou

2009/2/11 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > http://code.google.com/p/pharo/issues/detail?id=505 Thank you very much HernÃ¡n. I pushed your change to PharoInbox -- Damien Cassou http://damiencassou.seasidehosting.st

Feb. 12, 2009

Re: [Pharo-project] DNU error in OB

by Serge Stinckwich

On Wed, Feb 11, 2009 at 7:43 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Wed, Feb 11, 2009 at 1:10 PM, Serge Stinckwich > <Serge.Stinckwich(a)gmail.com> wrote: >> i have a DNU error each time i didn't select any category when i open >> a new OB browser and i search a class with CTRL-F. > > I also think this has been fixed. Please download a more recent pharo-dev. Ok, thank you. It works on more recent pharo-dev image. -- Serge Stinckwich IRD - UR 079 Geodes, MSI Team, Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

Feb. 12, 2009

Re: [Pharo-project] Pharo Smalltalk now also on Nabble

by Alexandre Bergel

Thanks for this. Cheers, Alexandre On 11 Feb 2009, at 22:46, Geert wrote: > > The Pharo Smalltalk mailing list should now also be available on > http://n2.nabble.com/Pharo-Smalltalk-f2305563.html www.nabble.com . > -- > View this message in context: http://n2.nabble.com/Pharo-Smalltalk-now-also-on-Nabble-tp2311636p2311636.h… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 11, 2009

[Pharo-project] Pharo Smalltalk now also on Nabble

by Geert

The Pharo Smalltalk mailing list should now also be available on http://n2.nabble.com/Pharo-Smalltalk-f2305563.html www.nabble.com . -- View this message in context: http://n2.nabble.com/Pharo-Smalltalk-now-also-on-Nabble-tp2311636p2311636.h… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 11, 2009

Re: [Pharo-project] Adding a new class category

by David RÃ¶thlisberger

> Thanks David. Let me know, I am ready to test again I fixed it. You can give it a try using OBAlpha. David

Feb. 11, 2009