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

[Pharo-project] About milestone
by StÃ©phane Ducasse Aug. 19, 2008

Aug. 19, 2008

Hi all I would really like to have soon a first official release. So what do we want to get in/out and before the release: - better look for sure - tests green. I think that this is important to release 0.1 Since I would really like to use the NewCompiler by default and remove the old one. Stef

2 2

[Pharo-project] A thought about Morphic and Seaside
by StÃ©phane Ducasse Aug. 18, 2008

Aug. 18, 2008

Hello guys We were browsing code with marcus and I realized something quite funny about Morphic. Morphic is somehow close to seaside for the following point: There is a list that contains the children. In Seaside you have to return a list containing the children components too. Now this is really interesting to see that a lot of complexity in Morphic code comes from the fact that the programmers avoided to have an instance variable for an element to the pretext that the element was already in the submorphs list. Then you end up with code like label: aString | oldLabel m | (oldLabel := self findA: StringMorph) ifNotNil: [oldLabel delete]. m := StringMorph contents: aString font: TextStyle defaultFont. self extent: m extent + (borderWidth + 6). m position: self center - (m extent // 2). self addMorph: m. m lock label | s | s := ''. self allMorphsDo: [:m | (m isKindOf: StringMorph) ifTrue: [s := m contents]]. ^ s instead of label ^ label label: aString .... where you have to query the submorph of the right kind.... Marcus was mentioning to me that Morphic is a bit like applying GraphTraversal that the law of demeter guy loves so much. And we see the results, an ugly code all over the places. So I will certainly play a bit with this design difference to see what it makes. But I'm sure now it makes a big difference. stef

4 9

[Pharo-project] Fwd: BasicButton for fun
by StÃ©phane Ducasse Aug. 18, 2008

Aug. 18, 2008

Begin forwarded message: > From: StÃ©phane Ducasse <stephane.ducasse(a)univ-savoie.fr> > Date: August 17, 2008 10:43:51 PM CEDT > To: An open mailing list to discuss any topics related to an open- > source Smalltalk <Pharo-project(a)lists.gforge.inria.fr> > Subject: BasicButton for fun > > In fact this is fun to see that even font default are inconsistent... > > TextStyle defaultFont is different from Preferences standardButtonFont > > But it may be worth checking the senders of allMorphDo: or submorph... > > > > > > stef

1 0

[Pharo-project] automatic in stall
by Hilaire Fernandes Aug. 17, 2008

Aug. 17, 2008

On a bare bone image (Without the class Installer), is it possible to install automatically Monticello package. On a -dev image I use to do: (Installer monticello http: 'http://www.squeaksource.com/repos' user: 'hlsf' password: 'xxx') install: 'paquage'. Hilaire -- http://blog.ofset.org/hilaire

3 2

Re: {Spam?} [Pharo-project] [Update] 10055 + new release
by Bill Schwab Aug. 15, 2008

Aug. 15, 2008

Ok, the profiler to the rescue. Instantiating some exception sub-classes should tell us whether there is anything to be gained from a factory of some sort. A quick look does not show much going on on instantiation, so it is probably fine to create the appropriate sub-instance and set any useful aspects, and to pass that to the ouch-block. 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 >>> m.rueger(a)acm.org 8/15/2008 3:48 PM >>> On Fri, Aug 15, 2008 at 8:51 PM, Bill Schwab <BSchwab(a)anest.ufl.edu> wrote: > I think the answer is probably to pass the *class* of the exception. > The default then simply sends the correct #signalWith: message with the > file name as an argument. Hmm, but the instance might hold additional information. Michael _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Re: {Spam?} [Pharo-project] [Update] 10055 + new release
by Bill Schwab Aug. 15, 2008

Aug. 15, 2008

I think the answer is probably to pass the *class* of the exception. The default then simply sends the correct #signalWith: message with the file name as an argument. 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 >>> m.rueger(a)acm.org 08/15/08 11:39 AM >>> Alexandre Bergel wrote: > At the first glance readOnlyFileNamed:ifNone: seems to be a useful > primitive. But this having the file absent might be just one case. You > could have ifNotReadable:, ifParentFolderNotReadable:. > Also, an error when writing in a file may occur in many different > situation (disk full, file read only, ...). > You may also want to provide handler for each of these situation (e.g., > writeFileNamed: aName with: stream ifDiskFull: [...] > ifAlreadyExistingFile: [...]... Agree... >> I agree you are improving on the existing code, but I would prefer >> something like >> >> file := fd readOnlyFileNamed:name ifNone:[ ^self ]. a solution would be to pass in any Exception into the ifNone: block: file := fd readOnlyFileNamed:name ifNone:[:ex| ^self ]. Then depending on whether you are actually interested in the exact reason the file couldn't be created you could look at the exception. Michael _______________________________________________ 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] Controller no view member anymore
by Hilaire Fernandes Aug. 15, 2008

Aug. 15, 2008

Hello, I saw that in recent change, I guess MVC clean up, the Controller class has lost it view instance variable. Are there any reason doing that change? For reference, http://en.wikipedia.org/wiki/Model-view-controller Hilaire -- http://blog.ofset.org/hilaire

1 0

[Pharo-project] Worth considering?
by Hilaire Fernandes Aug. 15, 2008

Aug. 15, 2008

To load Magma Beta version throught Monticello Configuration by Chris, I need the two included fixes in Pharo. Does it worth integrating these fixes in Pharo? Hilaire -- http://blog.ofset.org/hilaire

3 7

Re: {Spam?} [Pharo-project] [Update] 10055 + new release
by Bill Schwab Aug. 15, 2008

Aug. 15, 2008

Stef, I agree you are improving on the existing code, but I would prefer something like file := fd readOnlyFileNamed:name ifNone:[ ^self ]. This is analogous to #at:ifAbsent:, which does not set up an exception handler and raise and handle an exception for something that is known to be handled locally. Then, just as #at: _does_ raise an exception, there should be readOnlyFileNamed:aBlock ^self readOnlyFileNamed:name ifNone:[ FileDoesNotExist signalWith:name. ]. #signalWith: might not be the correct syntax (too tired to look<g>), but hopefully it makes the point that exceptions should be raised, but there should also be "long winded" methods that skip the overhead when it is possible to do so. 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 >>> stephane.ducasse(a)inria.fr 08/11/08 4:15 PM >>> ------------------------------------------------------ update10052 ISSUE #124 While browsing at referencer of FileDoesNotExistException, I discovered the following pattern that is used in many different places. I find this pretty ugly: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= file := [fd readOnlyFileNamed: keysFileName] on: FileDoesNotExistException do:[:ex| nil]. file ifNil:[^self]. "no keys file" -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= The use of exception is completely outwitted. I would rather write: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= [file := fd readOnlyFileNamed: keysFileName] on: FileDoesNotExistException do: [:ex| ^ self]. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

3 2

Aug. 15, 2008

sure I think that mentioning that if the code is published in the pharo squeaksource repository and on any squeaksource repository it is MIT. (I have problem to see people using free resources for private project) would be a good addition. On Aug 15, 2008, at 4:17 AM, Bill Schwab wrote: > Stef, > > I need to sign and send you a copy of the agreement. The terms are > fine > - if I give something away, I intend to do just that, and MIT is fine > (anything not GPL is fine<g>). The only small concern I have is that > the agreement does not specify what distinguishes contributed code. I > gather from elsewhere that loading it into a repository is the > trigger. > Would there be any problem defining that in the agreement? I am > simply > looking ahead to conversations with lawyers; I need to at least talk > to > them about it - they get quite upset if left out of things. > > If you are agreeable to a change, it might be best to wait until we > see > what, if any, other concerns might arise before updating the web site. > > 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 > >

2 1