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

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

by Marcus Denker

On Apr 1, 2010, at 10:11 AM, StÃ©phane Ducasse wrote: > Hi andreas > > You could not resist....... > > and you got trapped to my eyes :). > > http://images2.fanpop.com/images/photos/2800000/Wolf-Eating-wolves-2812984-… > > I was more thinking about this: The "etoy hater Brunnen" in Bern :-) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 1, 2010

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

by StÃ©phane Ducasse

+1 And we know it all! >>>> > It's not hostility. Not at all. It's my *love* for Squeak that was/is the problem. I could just not do nothing, *because* > I loved it so much... my mistake. > >> Even more so since CompiledMethod>>asString DOES NOT EXIST in Squeak. > > So then I was wrong with this analysis... but on the big picture, it is true. And you know it. > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 1, 2010

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

by StÃ©phane Ducasse

Hi andreas You could not resist....... and you got trapped to my eyes :). http://images2.fanpop.com/images/photos/2800000/Wolf-Eating-wolves-2812984-… Stef PS: Marcus you are a bad guy, bad bad bad :) "Oh le vilain" (kid voice) >> >>> Hi, I just bumped into this. Probably this is intended somehow, but it >>> does seem weird enough to ask â¦ >>> >>> (Object>> #hash) asString class >>> >>> returns 'Text'. >>> >>> >> >> I think this is historical. Methods *used* to return Strings, and the Browser highlighted the first line. >> >> Than, when the possibility to have "Rich text" kind of methods (with bold, colors, links) added in Squeak, >> this was "implemented" by the "do the smallest change possible, we will rewrite everything anyway" strategy. >> >> Never clean up! Never Refactor! > > Wow, Marcus. Your hostility towards Squeak is seriously amazing. Even more so since CompiledMethod>>asString DOES NOT EXIST in Squeak. It's a Pharo method. Of course, it's Squeak's fault that in Pharo, and Pharo only, CompiledMethod>>asString returns a text. > >> Of course, like always, the "big rewrite from scratch" never happened. To the contrary, all the time more and >> more "do the smallest change possible" changes where introduced on top, up to the point that the whole system >> was just *bad*. > > So what does that mean given that the method has a stamp of 'stephane.ducasse 8/9/2009 12:05'? > > Cheers, > - Andreas > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 1, 2010

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

by Marcus Denker

On Apr 1, 2010, at 9:43 AM, Andreas Raab wrote: > On 4/1/2010 12:12 AM, Marcus Denker wrote: >> >> On Apr 1, 2010, at 12:00 AM, Niko Schwarz wrote: >> >>> Hi, I just bumped into this. Probably this is intended somehow, but it >>> does seem weird enough to ask â¦ >>> >>> (Object>> #hash) asString class >>> >>> returns 'Text'. >>> >>> >> >> I think this is historical. Methods *used* to return Strings, and the Browser highlighted the first line. >> >> Than, when the possibility to have "Rich text" kind of methods (with bold, colors, links) added in Squeak, >> this was "implemented" by the "do the smallest change possible, we will rewrite everything anyway" strategy. >> >> Never clean up! Never Refactor! > > Wow, Marcus. Your hostility towards Squeak is seriously amazing. It's not hostility. Not at all. It's my *love* for Squeak that was/is the problem. I could just not do nothing, *because* I loved it so much... my mistake. > Even more so since CompiledMethod>>asString DOES NOT EXIST in Squeak. So then I was wrong with this analysis... but on the big picture, it is true. And you know it. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 1, 2010

Re: [Pharo-project] Cuis Editor Port

by StÃ©phane Ducasse

>>>> 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. >>> >>> >> > > > It's because Shout is not installed in the core . > > Missing SHTextStylerST80 Class. > > Maybe it means that we should have a ConfigurationOfCuisEditorPort ? No this is overkill. Texteditor should be really integrated into pharo so we should not lose our time on having them manage as totally separate package. Even if the styler method should be package with Shout. Stef

April 1, 2010

Re: [Pharo-project] cuis editors

by StÃ©phane Ducasse

why not? >> 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] Test for Collection>>sorted

by StÃ©phane Ducasse

On Apr 1, 2010, at 8:50 AM, Hilaire Fernandes wrote: > 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. this is on my todo for the next book but well other people could help... > 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) I do not have time for that. > 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) Yes the idea is that you define a couple of methods in your testTraits testNilSorted testSorted testSortedWithDuplicates testAlreadySorted testSortedCollectionIsANewCollection they will rely on different accessors testNilSorted self assert: self emptyCollection sorted isEmpty ArrayTest uses: TSorted and since emptyCollection is already defined you are done. Now if you have testSorted self assert: self aNonEmptyCollection sorted = self sortedCollection ArrayTest>> aNonEmptyCollection ^ #(3 6 1 20 -3) ArrayTest>> sortedCollection ^ #(-3 1 3 6 20) Stef > > >> Traits are simple, just have a look. I did a presentation at esug about them. > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 1, 2010

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

by Andreas Raab

On 4/1/2010 12:12 AM, Marcus Denker wrote: > > On Apr 1, 2010, at 12:00 AM, Niko Schwarz wrote: > >> Hi, I just bumped into this. Probably this is intended somehow, but it >> does seem weird enough to ask â¦ >> >> (Object>> #hash) asString class >> >> returns 'Text'. >> >> > > I think this is historical. Methods *used* to return Strings, and the Browser highlighted the first line. > > Than, when the possibility to have "Rich text" kind of methods (with bold, colors, links) added in Squeak, > this was "implemented" by the "do the smallest change possible, we will rewrite everything anyway" strategy. > > Never clean up! Never Refactor! Wow, Marcus. Your hostility towards Squeak is seriously amazing. Even more so since CompiledMethod>>asString DOES NOT EXIST in Squeak. It's a Pharo method. Of course, it's Squeak's fault that in Pharo, and Pharo only, CompiledMethod>>asString returns a text. > Of course, like always, the "big rewrite from scratch" never happened. To the contrary, all the time more and > more "do the smallest change possible" changes where introduced on top, up to the point that the whole system > was just *bad*. So what does that mean given that the method has a stamp of 'stephane.ducasse 8/9/2009 12:05'? Cheers, - Andreas

April 1, 2010

[Pharo-project] Cuis Editor Port

by Fernando olivero

On Apr 1, 2010, at 8:33 AM, Fernando olivero wrote: >> >>> 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. >> >> > It's because Shout is not installed in the core . Missing SHTextStylerST80 Class. Maybe it means that we should have a ConfigurationOfCuisEditorPort ?

April 1, 2010

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

by Marcus Denker

On Apr 1, 2010, at 12:00 AM, Niko Schwarz wrote: > Hi, I just bumped into this. Probably this is intended somehow, but it > does seem weird enough to ask â¦ > > (Object >> #hash) asString class > > returns 'Text'. > > I think this is historical. Methods *used* to return Strings, and the Browser highlighted the first line. Than, when the possibility to have "Rich text" kind of methods (with bold, colors, links) added in Squeak, this was "implemented" by the "do the smallest change possible, we will rewrite everything anyway" strategy. Never clean up! Never Refactor! Of course, like always, the "big rewrite from scratch" never happened. To the contrary, all the time more and more "do the smallest change possible" changes where introduced on top, up to the point that the whole system was just *bad*. There is something to be learned from this, I guess. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 1, 2010