April 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Test for Collection>>sorted

by Hilaire Fernandes

StÃ©phane Ducasse a Ã©crit : > On Mar 31, 2010, at 5:38 PM, Hilaire Fernandes wrote: > >> I wrote two tests on the ArrayTest collection to test #sorted and #sorted: >> #sorted broke, it is easy to fix. >> >> I guess we need to write these tests for the whole CollectionTest hierarchy. I noted there is a CollectionRootTest using trait, however when looking at the asSortedCollection tests, it is reapeatly written for almost each classes of the hierarchy, and not in the CollectionRootTest using inheritance mechanism. >> Any reason for that? > > Hilaire you should read the paper on traits. pointer on *one* good tutorial? I think I already read something. A small memento on the syntax to define and to use trait will be enough to get started comfortably. If there are such a things I suggest we add it in good place in the pharo web site (along a paper on unit test); these features are essential parts -- features -- of Pharo, so why not emphasis it. Btw, it would be a nice idea to convert an html version of the Pharo by example book, so we can have direct pointer to chapter from the pharo web site. It should be doable with latex2html. In the past I used hyperlatex to produce both nice html and pdf version of DrGeo manual (http://documentation.ofset.org/drgeo/fr/drgenius_51.html) > Probably sorted does not make sense on all collection so we define a trait and apply it when needed. Yes. What about writing like bellow? Is it acceptable or is it cumbersome? testSorted self unsortedCollection ifNotNil: [self assert: ....] Matrix>>unosrtedCollection ^ nil Arary>>unosrtedCollection ^ #(5 9 1 3 2) > Traits are simple, just have a look. I did a presentation at esug about them.

April 1, 2010

Re: [Pharo-project] Test for Collection>>sorted

by Hilaire Fernandes

StÃ©phane Ducasse a Ã©crit : > On Mar 31, 2010, at 5:38 PM, Hilaire Fernandes wrote: > >> I wrote two tests on the ArrayTest collection to test #sorted and #sorted: >> #sorted broke, it is easy to fix. >> >> I guess we need to write these tests for the whole CollectionTest hierarchy. I noted there is a CollectionRootTest using trait, however when looking at the asSortedCollection tests, it is reapeatly written for almost each classes of the hierarchy, and not in the CollectionRootTest using inheritance mechanism. >> Any reason for that? > > Hilaire you should read the paper on traits. pointer on *one* good tutorial? I think I already read something. A small memento on the syntax to define and to use trait will be enough to get started comfortably. If there are such a things I suggest we add it in good place in the pharo web site (along a paper on unit test); these features are essential parts -- features -- of Pharo, so why not emphasis it. Btw, it would be a nice idea to convert an html version of the Pharo by example book, so we can have direct pointer to chapter from the pharo web site. It should be doable with latex2html. In the past I used hyperlatex to produce both nice html and pdf version of DrGeo manual (http://documentation.ofset.org/drgeo/fr/drgenius_51.html) > Probably sorted does not make sense on all collection so we define a trait and apply it when needed. Yes. What about writing like bellow? Is it acceptable or is it cumbersome? testSorted self unsortedCollection ifNotNil: [self assert: ....] Matrix>>unosrtedCollection ^ nil Arary>>unosrtedCollection ^ #(5 9 1 3 2) > Traits are simple, just have a look. I did a presentation at esug about them.

April 1, 2010

Re: [Pharo-project] CompiledMethod asString is a text

by Marcus Denker

On Apr 1, 2010, at 4:39 AM, Igor Stasenko wrote: > On 1 April 2010 01:52, Randal L. Schwartz <merlyn(a)stonehenge.com> wrote: >>>>>>> "Niko" == Niko Schwarz <niko.schwarz(a)googlemail.com> writes: >> >> Niko> Hi, I just bumped into this. Probably this is intended somehow, but it >> Niko> does seem weird enough to ask â¦ >> >> Niko> (Object >> #hash) asString class >> >> Niko> returns 'Text'. >> >> It has to be, to hold styled text, right? >> > as to me, asking to string, should return string, not text. > Yes. And if a tool wants bold, it calls asText. Another example of the "principle of the least surprise". That's the reason why, for example, "Browser open" opens a Browser, not a Workspace Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 1, 2010

Re: [Pharo-project] cuis editors

by Fernando olivero

On Mar 31, 2010, at 9:54 PM, StÃ©phane Ducasse wrote: > I suggest that you post that to the mailing-list since lot of people are interested. Stef, you suggest that i give global read rights to this package now? > > > On Mar 31, 2010, at 1:05 AM, Fernando olivero wrote: > >> >> Hi, thanks for the patience. >> >> I've decided to created a package at squeak source, instead of the SLICE. >> >> MCHttpRepository >> location: 'http://www.squeaksource.com/CUISEditorPort' >> user: 'FerO' >> password: '' >> I've added both of you as developers, because for now the read/write global access is false. >> Please download the package and test the examples, >> >> EntryFieldMorph class>>example1 > > fixed and I will publish > Great! Do you agree on using Announcements for announcing acceptedContents and escape? IMO this would allow us to remove PluggableTextMorphs, and unify them with the TextMorphs family. > > >> NewTextMorph class>>example1 >> >> (this one's i added as subclasses of NewTextMorph, for convenience) >> MethodMorph class>>example1 > > > styler > | styler | > styler := self stylerClass new. > styler classOrMetaClass: self codeClass . > ^ styler > > > > stylerClass is not know. > > Fill fix it now. >> ClassDefinitionMorph class>>example1 >> >> Please let me know what you think! >> >> I can even post some uses to show the benefits of having the Editor and morph decoupled. >> For example, it made straightforward to implement a searchWidget for Gaucho . >> >> >

April 1, 2010

Re: [Pharo-project] CompiledMethod asString is a text

by Igor Stasenko

On 1 April 2010 01:52, Randal L. Schwartz <merlyn(a)stonehenge.com> wrote: >>>>>> "Niko" == Niko Schwarz <niko.schwarz(a)googlemail.com> writes: > > Niko> Hi, I just bumped into this. Probably this is intended somehow, but it > Niko> does seem weird enough to ask â¦ > > Niko> Â Â (Object >> #hash) asString class > > Niko> returns 'Text'. > > It has to be, to hold styled text, right? > as to me, asking to string, should return string, not text. > -- > Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 > <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> > Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. > See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Best regards, Igor Stasenko AKA sig.

April 1, 2010

Re: [Pharo-project] The Pharo Linux Vm [WAS] Squeak VM+FT2Plugin, all Pharo 1.0 rc3 tests green

by John M McIntosh

Thank you very much for the work. Given your efforts I proceeded to spend a couple of hours again today to resolve the problem. I took a slightly different approach and made a number of changes to properly deal with the window size not working properly when the size is not a multiple of four. . I've checked these changes into the V5 tree. You should check out the current source and see what changed. It does draw the window properly now even when the window size is not a multiple of 4. However there is some work to resolve what to do when the window is in live resize. What happens now is that it appears to display pixels from video memory as it's attempting to resize the window size. I'm not quite sure exactly *why* it's wrong yet. One of the problems is that the window size changes, but the display buffer in squeak doesn't change right away. It's possible we may have to show a snapshot of the screen surface when the resize starts, then update it after the resize terminates. On the other hand the side effect is interesting, as long as it doesn't crash it's not high on the list to fix. On 2010-03-31, at 6:07 AM, Henrik Johansen wrote: > sqSqueakOSXInfoPlistInterface.h -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

April 1, 2010