December 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: semantics of overrides
by StÃ©phane Ducasse Dec. 23, 2009

Dec. 23, 2009

> Hi > > I'm starting to think to add override to my new implementation of Package. > Now I wonder how PackageInfo keeps information the fact that when an overridding method > is unload, the overridden is added back to the class. > May be this is MC that does this? Does anybody knows about it? > > Then I have also another question related to the order > > P1>>*m > p1 > P2>>*m > p2 > P3>>*m > p3 > > right now is the load order preserved? > ie does P3 takes precedence over p2 and p1 > > If I unload P2 and P3 do I get P1, I remember that alex got problems > with that some years ago. > > Stef > >

3 6

[Pharo-project] Fwd: [squeak-dev] The Trunk: Collections-ul.260.mcz
by StÃ©phane Ducasse Dec. 23, 2009

Dec. 23, 2009

Hi Levente why don't you help us too? Stef > From: commits(a)source.squeak.org > Date: December 23, 2009 12:29:08 PM GMT+01:00 > To: squeak-dev(a)lists.squeakfoundation.org, packages(a)lists.squeakfoundation.org > Subject: [squeak-dev] The Trunk: Collections-ul.260.mcz > Reply-To: squeak-dev(a)lists.squeakfoundation.org > > Levente Uzonyi uploaded a new version of Collections to project The Trunk: > http://source.squeak.org/trunk/Collections-ul.260.mcz > > ==================== Summary ==================== > > Name: Collections-ul.260 > Author: ul > Time: 23 December 2009, 12:23:32 pm > UUID: de4b02f8-b0aa-5e47-93f7-4a3e3c300060 > Ancestors: Collections-ul.259 > > - make sure that SortedCollection's #sort and #sort: update the sortBlock > > =============== Diff against Collections-ul.259 =============== > > Item was added: > + ----- Method: SortedCollection>>sort: (in category 'sorting') ----- > + sort: aSortBlock > + "Sort this collection using aSortBlock. The block should take two arguments > + and return true if the first element should preceed the second one. > + If aSortBlock is nil then <= is used for comparison." > + > + super sort: aSortBlock. > + sortBlock := aSortBlock! > >

2 5

[Pharo-project] Fwd: All mailinglist messages on gmane are dublicated
by StÃ©phane Ducasse Dec. 23, 2009

Dec. 23, 2009

> > can somebody have a look? > > Stef > > >

3 2

[Pharo-project] [update 1.1] #11112
by Marcus Denker Dec. 23, 2009

Dec. 23, 2009

11112 ----- Issue 1652: Behavior >> #allSubclassesDo: depends on #subclassesDo: which is defined in Class and friends only Thanks, Adrian Kuhn Issue 1633: Object allSubInstances appears to loop forever Thanks, Eliot Miranda (from Squeak) Issue 1655: MethodFinder Fixes Thanks, Bert Freudenberg (from Squeak) Issue 1654: SpeedUpCommandHistory Thanks, Eliot Miranda (from Squeak)

3 4

Re: [Pharo-project] did you check in 1.1 how the old browser now support the creation of new method cat
by StÃ©phane Ducasse Dec. 23, 2009

Dec. 23, 2009

I sent that to the list because this is really important. >> one of these days we will have to have some pharo specific tools. > > There will be nobody that maintains them. There will be nobody that takes responsibility and that writes and runs tests. You can see that with Davids browser, it is dead. You can see that with Services, they are dead. And many others ... Yes but pharo is moving so slowly we will get more people taking care of packages. > But that is not the real problem. And I didn't mean Squeak (although that's a problem too, but I personally don't care). What I ment is the difference between Pharo 1.0 and Pharo 1.1. You lost me there :) > These two versions are killing any progress on the tool front and makes any maintainer of external packages a lot of pain. Why why don't you freeze a version for pharo1.0 Else we can just stop now. because this will be the same with pharo1.1 and 1.2 and 1.0 > I spent the complete Thursday and Friday trying to get Helvetia running in Pharo 1.1, but that doesn't work because it requires some significant changes in packages like the Refactoring Rngine, the AST, Shout, eCompletion and OB that are also supposed to work on Pharo 1.0. No there are not supposed to work in 1.0 CERTAIN frozen versions are supposed to work on 1.0 and others won't. A lot of software on mac does not run automatically on snowleopard and 10.2 Tell me if Im wrong but we should use release and version. > Adding the category dialog to OB makes it depend on 1.1, thus people cannot use it in 1.0 anymore. So the category dialog can maybe happen in a year from now. I cannot use 1.1 at the moment, I am stuck with the frozen 1.0 version.

6 23

[Pharo-project] Issue 1659: WACallSuperImplementationRule>>checkClass: on a SmalllintContext ObjectTracer causes walkback
by Stan Shepherd Dec. 23, 2009

Dec. 23, 2009

VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update: #10074] Image: PharoCore1.0rc1 [Latest update: #10500] SystemBrowser default = Browser Steps to reproduce: 1.From Browser, right click any class 2.refactor > code critics 3.opens Code Critics: All checks on Smalltalk 4. walkback occurs checking ObjectTracer - no superclass -- View this message in context: http://n2.nabble.com/Issue-1659-WACallSuperImplementationRule-checkClass-on… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

3 5

[Pharo-project] Exploiting a new method trailer format(s)
by Igor Stasenko Dec. 23, 2009

Dec. 23, 2009

Hello guys, i am a dreamer. Did i say that? Yesterday i started coding a new class, called a SourceCodeManager which will eventually replace the old stuff with SourceFileArray, RemoteString manual parsing preambles , like (stephaneducasse 2/4/2006 20:32 Â· accessing Â· 2 implementors Â· in no change set Â· ) etc etc.. Initially, this facility will be responsible for retrieving a preamble info + source by given sourcePointer. But this is not all. There is a basic class, BasicSourceCodeManager which declares protocol, so you can make a subclass of it. Also, it doesn't forcing you to use sourcePointer to be only integer values. This means, that by fusing a new trailer formats + new, more flexible, source code manager we can make a great leap towards the future: use a remote storage for our source code, publicly available. Use it in a fashion, envisioned by Goran (DeltaStreams) + techniques, used by git (add, commit, push ), easily migrate the code, browse other's update streams , diff , merge etc etc.. These thoughts can't leave my mind once i started thinking how small the efforts needed to make things rolling: - JSON (already there http://www.squeaksource.com/JSON) + CouchDB (alredy there http://www.squeaksource.com/CouchDB, but have to be revised... no idea why it using curl, while squeak has own means to use HTTP stuff) + write CouchDBCodeManager (to be implemented) you know what it means? It means that any code which you accepting in browser, could be automatically posted on server. And you can even configure image to not use local files at all! CouchDB is extremely easy to use and fits for version-tracking, because its inherently supports document versioning. -- Best regards, Igor Stasenko AKA sig.

1 0

Dec. 23, 2009

Igor I saw that method trailer were pushed into squeak. Do you plan to provide us a version for pharo? Or will we have to dig into squeak? Stef

4 10

Dec. 23, 2009

> > > Hi guys > > I have a design question. I'm working on RPackage a new package class. > RPackages are stored in RPackageOrganizer singleton. > Now to be able to run the tests without touching RPackageOrganizer singleton > I provided a Mock (subclass of RPackageOrganizer) > > RPackage class>>packageOrganizerClass as classVar > and > RPackage class>>packageOrganizerClass: > > Now I write tests as > setUp > > RPackage packageOrganizerClass: RMockPackageOrganizer. > p1 := self createNewPackageNamed: 'P1'. > p2 := self createNewPackageName > ... > tearDown > b2 := nil. > a3 := nil. > RPackage packageOrganizerClass: RPackageOrganizer. > > > So far so good. > Now however, I had to change > ClassDescription>>package > ^ RPackage packageOrganizerClass default packageOf: self name. > "use RPackage packageClassOrganizer instead of the singleton > because tests use the mock" > > instead of simply > > ClassDescription>>package > ^ RPackage default packageOf: self name. > > > I was thinking that if I really want to be as fast as possible I could > separate the package and put the tests in a separate package and use overrides..... > so that > > ClassDescription>>package > ^ RPackage packageOrganizerClass default packageOf: self name. > "use RPackage packageClassOrganizer instead of the singleton > because tests use the mock" > > is only used when the tests are loaded > Berk > > So do we have another simple solution at hand? > > Stef > > > >

3 7

[Pharo-project] SeasideXUL demo
by Pavel Krivanek Dec. 23, 2009

Dec. 23, 2009

Hi, I created a short demonstration video with SeasideXUL http://www.youtube.com/watch?v=pkfSh4pAbdM Cheers, -- Pavel

3 2