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

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

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

by Damien Cassou

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

Feb. 6, 2009

Re: [Pharo-project] Presentation

by Alexandre Bergel

Sure Alexandre On 5 Feb 2009, at 21:45, Adrian Lienhard wrote: > Alex, could you post a new version afterwards? I'll then take another > look and give you further feedback, if you want. > We can also put the slides on the web page. > > Cheers, > Adrian > > On Feb 5, 2009, at 21:31 , Alexandre Bergel wrote: > >> I will take your comments into account, thanks Doru >> >> Alexandre >> >> >> On 5 Feb 2009, at 20:08, Tudor Girba wrote: >> >>> Hi Alex, >>> >>> Nice idea. Here are a couple of things you could improve: >>> >>> - I would replace the front page with just the logo and the url. >>> >>> - use a white background because the screenshots will look better as >>> they have behind a white background that looks ugly due to the >>> rounded >>> corners of the windows (see for example slide 7). Alternatively, you >>> can set the background of the Pharo image to black and retake the >>> screenshots. >>> >>> - in any case, the motif of the background does not help. >>> >>> - Slide 2 is weak and tries to do too much. The text in parantehesis >>> is not needed given that your audience is new to Smalltalk. What is >>> Seaside? I would suggest to make a dedicated part of the >>> presentation >>> Seaside-related. The line in italics is confusing. Use the logo >>> instead of the title. Remove the bullets :). In fact, I would make >>> the >>> logo appear in the same place as on the previous slide, and only >>> change the text. This will make for a nice transition. >>> >>> - the screenshot on Slide 6 has too small fonts >>> >>> - On Slide 7 you use centered text, but everywhere else you use left >>> aligned text. Stick with the left aligned one. >>> >>> - Slide 12 needs some alignment. I would suggest to make the blue >>> regions the same width and height and align them vertically. >>> >>> - Also, I think the font of the white text from slide 12 is not as >>> light as it is in the rest of the presenation. >>> >>> - The explanations in red on slide 13,14 are too small and not >>> useful >>> like that. Make them bigger. Potentially you can also use animations >>> to introduce them. >>> >>> - Slide 15 needs alignment >>> >>> - The green in Slide 16 does not look nice :). If you replace the >>> black background with white, it will fit better. Alternatively, you >>> have to edit the diagram again in omnigraffle and make white on >>> black. >>> In fact you anyway have to edit the diagram to make it use the same >>> font as in the presentation (which I guess is Helvetica Neue Light) >>> >>> - Slide 17 needs alignment >>> >>> - Slide 18 is not so useful. >>> >>> - Slide 19 has too many messages. What does that mean strong >>> community? >>> >>> - No need for the bullets on Slide 20 >>> >>> - I won't say anything about slide 21 :) >>> >>> >>> >>> >>> Cheers, >>> Doru >>> >>> >>> On Feb 5, 2009, at 7:43 PM, Bill Schwab wrote: >>> >>>> Alexandre, >>>> >>>> That looks pretty good. I would probably get the debugger to show >>>> itself off just a bit more - if only by picking a more interesting >>>> method for the source pane. >>>> >>>> You said that all control structures are realized by message sends. >>>> Is >>>> that really true? What about optimizations? >>>> >>>> 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) 273-6785 >>>> FAX: (352) 392-7029 >>>> >>>>>>> Alexandre.Bergel(a)inria.fr 02/05/09 12:32 PM >>> >>>> >>>> Dear List, >>>> >>>> I made up few slides about Pharo. The goal is to give in less than >>>> 30 >>>> minutes the essence of Pharo. >>>> Please, shot at me, I like that :-) >>>> >>>> http://bergel.eu/Pharo.pdf >>>> >>>> I provide the .keynote upon request. >>>> >>>> Alexandre >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> 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 >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing should have the right to be different." >>> >>> >>> >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > 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. 5, 2009

Re: [Pharo-project] Presentation

by Chris Kassopulo

On Thu, 05 Feb 2009 18:32:24 +0100, Alexandre Bergel wrote: > Dear List, > > I made up few slides about Pharo. The goal is to give in less than 30 > minutes the essence of Pharo. > Please, shot at me, I like that :-) > > http://bergel.eu/Pharo.pdf > > I provide the .keynote upon request. > > Alexandre Slide 5: Perhaps should read "Everything happens by sending messages to objects". Slides 12 and 13: The pointers from label to text are not visible against the black background. Slide 13: The labels should be the same color as on slide 12. Slide 18: Should follow slide 19.

Feb. 5, 2009

Re: [Pharo-project] a couple of issues

by StÃ©phane Ducasse

We were thinking to have a preference to manage that. And seriously I do not understand why people do not follow uppercase for shared and lowercase for private. Janko told me that he fixed that in Swazoo. Stef > > did anyone answer this question about the warnings? I believe they > are new compiler warnings which was discussed in another thread. I'm > a bit out of date, i'm not sure we implemented a conclusion? My vote > is with these not being forced by the compiler but using the code > critic as Lukas suggested. Or as you say, presenting them all at the > end. i get these too loading Cryptography packages so it is not a > convenient default behaviour. > > thanks, > > Mike > > 2009/2/1 Tudor Girba <girba(a)iam.unibe.ch>: >> There was a warning complaining that some instance variable is in >> capital letter. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 5, 2009