- Pharo-dev - lists.pharo.org

[Pharo-project] More Polymorph

by Gary Chambers

Just to let you all know that there's some newer versions of Polymorph-Widgets and Polymorph-ToolBuilder that integrate Alain's submission as part of his work on removing PopUpMenu things. A few other tweaks too, FileList should now work again. Regards, Gary

Feb. 6, 2009

[Pharo-project] looking for Unicode testers

by Michael Rueger

Hi all, finally I have something to look at :-) http://impara.de/michael/unicode.zip It is the pharo one click with a modified (slightly outdated) image and an updated Unix VM. The image is not cleaned up at all, just so you are warned ;-) Please try out this version on different platforms and check if unicode keyboard input, clipboard copy and paste as well as filenames are working. There are probably still plenty of bugs in there, that's why I need extra testers :-) Please also point out any existing patches I missed to include in this image. Enjoy Michael

Feb. 6, 2009

[Pharo-project] [ANN] 10221

by StÃ©phane Ducasse

Hi all I decided to unload for now the collection extensions I did since some require a much better stream implementation. So we will use them and debug them in our own development on top of Nile for now. Stef

Feb. 6, 2009

[Pharo-project] method add: in class Set

by Laval Jannik

Hi all, The method add: in the class Set return an error if the parameter is nil. Maybe, we can return nil and manage the error outside the method. Currently, the method is --- | index | newObject ifNil: [self error: 'Sets cannot meaningfully contain nil as an element']. index := self findElementOrNil: newObject. (array at: index) ifNil: [self atNewIndex: index put: newObject]. ^ newObject --- We can do something like this. (the same as VisualWorks) --- | index | newObject ifNil: [^newObject]. index := self findElementOrNil: newObject. (array at: index) ifNil: [self atNewIndex: index put: newObject]. ^ newObject --- Jannik

Feb. 6, 2009

Re: [Pharo-project] Copy the debugger stack

by StÃ©phane Ducasse

in the old debugger you have an option but not in the OB one. Stef On Feb 6, 2009, at 10:40 AM, Alexandre Bergel wrote: > Do you mean having a textual representation of the method call stack? > Have a look at your folder, you should have SqueakDebug.log. This file > is generated at each not caught exception I believe. > > Cheers, > Alexandre > > > On 6 Feb 2009, at 10:29, Laval Jannik wrote: > >> Hi all, >> >> How can I copy the stack of the debugger in pharo. >> There is no command in the menu. >> >> Thanks >> >> Jannik >> >> _______________________________________________ >> 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 6, 2009

Re: [Pharo-project] A step by step tutorial about Traits

by Hilaire Fernandes

Thanks for this short how-to Hilaire 2009/2/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hilaire > > have a look at CollectionsTest there are really simple example of > traits. > In 5 minutes you should get that: > > You have a trait TRemoveTest > > Trait named: #TRemoveTest > uses: {} > category: 'CollectionsTests-Abstract' > > easy > > TRemoveTest>>testRemoveElementFromEmpty > "self debug: #testRemoveElementFromEmpty" > > self should: [self empty remove: self nonEmpty anyOne] raise: Error > > Easy > self empty is undefined and it will return an empty collection > self nonEmpty and nonEmpty one > > testRemoveElementThatExists > "self debug: #testRemoveElementThatExists" > > | el res | > el := self nonEmpty anyOne. > self shouldnt: [res := self nonEmpty remove: el ] raise: Error. > self assert: res == el > > > testRemoveElementReallyRemovesElement > "self debug: #testRemoveElementReallyRemovesElement" > > | size | > size := self nonEmpty size. > self nonEmpty remove: self nonEmpty anyOne. > self assert: (size -1) = self nonEmpty size > > OK now you use the trait in a class > For example > > Object subclass: #MySetTest > uses: TRemoveTest > instanceVariableNames: 'full empty > > You define > > setUp > full := Set new add: 5 ; add: 6 ;yourself > empty := Set new. > > nonEmpty > > ^ full > > empty > ^ empty > > > This is it!!!!! > You can reuse your traits in another Test. > > Now if you do not like a trait method you can remove it or redefine it > in your class > > DONE!!! > > Stef > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://blog.ofset.org/hilaire

Feb. 6, 2009

Re: [Pharo-project] Copy the debugger stack

by Alexandre Bergel

Do you mean having a textual representation of the method call stack? Have a look at your folder, you should have SqueakDebug.log. This file is generated at each not caught exception I believe. Cheers, Alexandre On 6 Feb 2009, at 10:29, Laval Jannik wrote: > Hi all, > > How can I copy the stack of the debugger in pharo. > There is no command in the menu. > > Thanks > > Jannik > > _______________________________________________ > 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. 6, 2009

[Pharo-project] Rename a package

by Laval Jannik

Hi all, How can I rename a package in Pharo ? Thanks Jannik

Feb. 6, 2009

[Pharo-project] Copy the debugger stack

by Laval Jannik

Hi all, How can I copy the stack of the debugger in pharo. There is no command in the menu. Thanks Jannik

Feb. 6, 2009

Re: [Pharo-project] Getting rid of INRIA SSL(https) certificate problem

by Alexandre Bergel

Safari is not supported apparently. Use Firefox instead Alexandre On 6 Feb 2009, at 06:10, Damien Cassou wrote: > Hi, > > INRIA certifies its own servers and people itself. You web browsers > are not configured to consider INRIA as a valid certificate provider. > If you want to get rid of the error messages or if you trust INRIA, > just go to > > https://igcgen.national.inria.fr/INRIA-Standard/?lang=fr&ca=INRIA-Standard&… > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > 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. 6, 2009