June 2008 - Pharo-dev - lists.pharo.org

[Pharo-project] 2 new updates
by StÃ©phane Ducasse June 4, 2008

June 4, 2008

Hi guys I harvested some fixes proposed: - file test cleaning - number parsing tests - nebraska cleaning I cleaned up the inbox. Tomorrow I will try to take a look at MVC step 1 :) Stef

1 0

[Pharo-project] About on:
by StÃ©phane Ducasse June 4, 2008

June 4, 2008

> From: pharo-project-owner(a)lists.gforge.inria.fr > Date: June 3, 2008 6:43:05 AM CEDT > To: ducasse(a)iam.unibe.ch > Subject: About on: > > You are not allowed to post to this mailing list, and your message has > been automatically rejected. If you think that your messages are > being rejected in error, contact the mailing list owner at > pharo-project-owner(a)lists.gforge.inria.fr. > > > From: stÃ©phane ducasse <ducasse(a)iam.unibe.ch> > Date: June 3, 2008 6:42:33 AM CEDT > To: An open mailing list to discuss any topics related to an open- > source Smalltalk <Pharo-project(a)lists.gforge.inria.fr> > Subject: About on: > > > Hi damien > > here is what I propose for on: > I will move your package out of the inbox so that the discussion can > go on and > I try to integrate all the other changes. > Then with bill and others you propose how to proceed. > Is it ok ? > > Stef > > >

2 2

[Pharo-project] why removing testhex?
by StÃ©phane Ducasse June 4, 2008

June 4, 2008

Hi serge why did you remove testHex? BTW I did not receive your nice license agreement

2 4

[Pharo-project] EToys
by Gary Chambers June 4, 2008

June 4, 2008

Just joined the mailing list. Was wonderering if you/we were looking at removing EToys. I'd be happy to help with that (it cuts deep into Morphic so should lead to some simplification). A "patch up" package could be made, perhaps, to reintegrate EToys after loading. Regards, Gary.

5 14

Re: [Pharo-project] EToys
by Bill Schwab June 4, 2008

June 4, 2008

My hunch is that Stef is against loading it in its current state. Any well-factored and optional package should be welcome. I am thrilled to see Gary on board! Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029 >>> damien.cassou(a)gmail.com 6/3/2008 10:50 AM >>> On Tue, Jun 3, 2008 at 5:47 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Tue, Jun 3, 2008 at 5:39 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: >> Damien, >> >> I don't, particularly! Just wondering what the approach is here... quite >> happy to rip it out altogether (might get a bit zealous with it!). Early >> indications are that around 200 methods can be dropped from Morph alone! >> >> Will wait for the inbox to settle first before applying my investigations to >> Pahro though. > > I was asking the question to StÃ©phane who said: > > "No reload of Etoy (as its current state) is important else it will > reintroduce cruft" Now that I read again the sentence, I think it can have 2 different meanings: "No ! reload of etoy is important !" or "reload of etoy is not important" Which one is correct? Knowing Stef, I would vote for 2 but I thought he meant 1. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ 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] Tools-AlexandreBergel.83 adds a dependency to OmniBrowser
by Damien Cassou June 3, 2008

June 3, 2008

There is a reference to OB specific classes in Tools-AlexandreBergel.83. OB must not be part of pharo in my opinion. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

2 1

[Pharo-project] Missing development tools in Pharo
by Oscar Nierstrasz June 3, 2008

June 3, 2008

I am missing some things in Pharo, starting with the Refactoring Browser and the VB-regex package. I sympathize with the principle of keeping Pharo small, but it would be really nice if we had in the Squeak flap some buttons to load in much of this standard stuff. How hard would it be to do this? It will surely be needed for Pharo development itself, no? - on

2 2

Re: {Spam?} [Pharo-project] Some questions on how to help
by Bill Schwab June 2, 2008

June 2, 2008

Norbert, I have also noted the "return nil on error" in parsers, and (my current mission) streams. IMHO, these decisions were questionable before structured exception handling, and are all the more unfortunate now. My preference would be to create something like #readFrom:onError: and then re-write #readFrom: in terms of it, raising an error inside the block. Failing to do that risks intermittent downstream failures due to "unexpected" garbage values. I like my bad news early, and in context. Skipping to the end of your message, I am hopeful that Pharo will not suffer from Squeak's barriers to adoption of good code, but I cannot promise same. It is probably best to start small and ask up-front whether people want what you propose. I suspect you will find that good work will be included in Pharo. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029 >>> norbert(a)hartl.name 6/2/2008 2:28:15 PM >>> Hi, I really appreciate the existence of the pharo project. For me I declared it as a good starting point for me to dive into the deeper waters of squeak/pharo. My biggest problem is that I do not know how exactly things have to be done. I don't want to just submit changes without to know if the worth it. A little story. I started last week to toy around with the newest pharo release. On the web site I read that all tests green is a primary goal. So I started to let the test runner run all tests. After having some trouble I found a failing test in NumberParsingTest. The test is failing because the test case expects Number>>readFrom: to throw an error if a number couldn't be parsed. Searchig the ST80 book I found nothing about Number>>readFrom:. Searching the web I found a thread on squeak-dev from january where the outcome was: - readFrom: returns 0 on unsuccesful read attempt to satisfy the parser (sounds like some history thing) - readExactlyFrom: does throw an error an unsuccesful read attempt. And it utilizes sqNumberParser So what to do? I tried to be least aggressive and fixed the test case to use readExactlyFrom: (and then splitting the test case into two because the test does different things). Not thinking first I would have asked a lot of questions on this list: - Do we want to preserve the current readFrom: ? - Should we integrate sqNumberParser completely avoiding mulitple implementations? - Is it only me having slightly problems having a class Number which uses a class SqNumberParser instead of integrating the code into the Number hierarchy? Is there a way to get this questions answered without generating a lot of noise on the list? Other questions: - I scanned the image for obsolete references and found some. I don't know how to deal with it in an update. Using ServerDirectory resetServers. FileServices removeObsolete. PackageOrganizer default unregisterPackageNamed: 'FlexibleVocabularies' I have removed all obsolete references but one. How is this integrated into the upstream? - Trying to solve the last obsolete references I found an obsolete class referenced in PasteUpMorph. The method which referenced it is PasteUpMorph>>isSafeToServe. The method is in category Nebraska. I thought Nebraska has been removed from the system. Thinking that I would have removed all methods of this category but one because they have no senders. One method transferRemoteServerFrom: is referenced from Project>>enter: returningFlag revert: revertFlag saveForRevert: saveForRevert Is it ok to rip this call out (by trying to understand what it does in class Project ;) ) Some words of advice would be helpful to get a feeling about those things. I don't have a problem preparing some stuff and put it into the Inbox. A problem would be to have a patch rejected without explanation :) Norbert _______________________________________________ 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] Lots of modifications waiting in PharoInbox
by Serge Stinckwich June 2, 2008

June 2, 2008

There is now a lots of package modifications waiting in the inbox. Is Stef the only one to integrate the changes inside Pharo ? -- Serge Stinckwich http://blog.doesnotunderstand.org/

2 1

June 2, 2008

> > > > 0006834: Delay class>>timeoutSemaphore:afterMSecs: doesn't. > Description The implementation for Delay > class>>timeoutSemaphore:afterMSecs: doesn't even use its first > parameter, so it can't do what it says it does. > > This method should be deprecated or removed entirely. > Additional Information + tests > > + obsolete references identified by norbert > > Stef > > >

1 0