- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Stateful Traits Literature

by Simon Denier

On 25 mars 2010, at 23:26, Alexandre Bergel wrote: > I agree. Most of our extensions are really complex. > > In my opinion, traits must define variable. Else it defeats the whole purpose of having a better modularity. Each time I use traits, I need variables. > > The solution of Visualworks was quite simple, and I think it makes sense in most of the practical cases: when you compose traits, you simply concatenate the variables defined in the composed traits with the variables defined in the class. Duplicated names are then removed. Easy. Funny, I also need state when I use traits, but in a more conservative approach: by default, I prefer states to be separated and possibly duplicated. I think it's easier to notice that state needs to be shared than to notice a weird bug happens because state is shared in a wrong way. If you need state to be shared, it's easy to refactor the accessors to access the same state. But it's my completely insubstantial opinion (it's a deal between sharing states to have easy consistency and having compatible constraints (pre/post conditions) on shared state) As for the argument with recompiling methods, it's the same deal right now because required methods need to be overridden right? The rule of thumb is that you should not access state directly, but only through pure accessors. So only pure accessors need to be recompiled. But the stuff discussed by Markus could be helpful. As for traitInitialization, I have my ideas but I guess there is no silver bullet. > > Cheers, > Alexandre > > > On 25 Mar 2010, at 17:19, Stefan Marr wrote: > >> Hi Alexandre: >> >> >> Thanks. >> I have read all these papers already, but kind of hoped that there is something I missed so far. >> >> On 25 Mar 2010, at 23:00, Alexandre Bergel wrote: >>> "Stateful Traits and their Formalization" http://scg.unibe.ch/scgbib?_k=OiaJOIuA&query=Berg08e&display=abstract >>> => It describes stateful traits >>> >>> "User-Changeable Visibility: Resolving Unanticipated Name Clashes in Traits" http://scg.unibe.ch/scgbib?_k=NNRwidu5&query=freezable+traits&display=abstr… >>> =>Freezable traits >>> >>> "Adding State and Visibility Control to Traits using Lexical Nesting" http://scg.unibe.ch/scgbib?_k=J-wbMltV&query=tom+cutsem+bergel >>> => Traits for a class-less language >> My problem is, that these proposals involve a lot additional complexity. >> And, Tom's paper is not really applicable to PHP. PHP just does not have a real notion of lexical context. >> >> Thanks >> Stefan >> >> >> >> -- >> Stefan Marr >> Software Languages Lab >> Vrije Universiteit Brussel >> Pleinlaan 2 / B-1050 Brussels / Belgium >> http://soft.vub.ac.be/~smarr >> Phone: +32 2 629 2974 >> Fax: +32 2 629 3525 >> >> >> _______________________________________________ >> 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 -- Simon

March 26, 2010

Re: [Pharo-project] Problem with TransformationMorph

by Lukas Renggli

> If the text background color is consistent, it should be fakeble in image. > Otherwise I'd reckon it requires more BitBlt fixes. Ok, converting the string morph to a bitmap works indeed. The text is readable. However the transparency does not work. I hope the VM gets fixed :-) > Look at the text in a rotated browser first, that's the result you can expect. > Basic way would be to instead of rendering the text glyphs rotated, render the glyphs on top of a bitmap of the proper rotated background, then rotate that opaque bitmap instead. > Not a perfect solution by any means, but it can be done if you're desperate enough... waiting for VM fixes can take a looooong time :( Are there any examples for that? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

March 26, 2010

Re: [Pharo-project] Problem with TransformationMorph

by Henrik Johansen

On Mar 26, 2010, at 11:11 47AM, Lukas Renggli wrote: > Ahh, with Squeak4.2.3beta1 I get the same as you. > > Not perfect, but already better. Any idea how the ugly expanded areas > can be fixed? > > Lukas If the text background color is consistent, it should be fakeble in image. Otherwise I'd reckon it requires more BitBlt fixes. Look at the text in a rotated browser first, that's the result you can expect. Basic way would be to instead of rendering the text glyphs rotated, render the glyphs on top of a bitmap of the proper rotated background, then rotate that opaque bitmap instead. Not a perfect solution by any means, but it can be done if you're desperate enough... waiting for VM fixes can take a looooong time :( Cheers, Henry

March 26, 2010

Re: [Pharo-project] [update 1.1] #11296

by Henrik Johansen

On Mar 26, 2010, at 10:27 34AM, Alain Plantec wrote: > StÃ©phane Ducasse a Ã©crit : >> 11296 >> ----- >> >> Issue 2208: Preferences setting >> * range setting: bad widget height in the SettingBrowser >> * improve TimeProfiler (MorphTreeMorph example) > Few words about that: > TimeProfiler is a improvement of the current TimeProfileBrowser. > just try it: > TimeProfiler new openOnBlock: [ 10 timesRepeat: [Transcript show: 'n' asString, String cr]]. > or simply > TimeProfiler new open > and then type-in the code you want to profile. > > For now, it is in the Morphic-MorphTreeWidget-Examples sys cat, > maybe it can replace TimeProfileBrowser in the core. > what do you think ? > > Cheers > Alain Absolutely <3 it! How about a Start profiling (Stop profiling when clicked) button as well, providing functionality equal to the Start profiling... options from the debug menu? I'd replace it in a heartbeat already tbh, with that extra button, we could reduce it to a single entry for profiling in the debug menu :) Cheers, Henry PS. Anyone know a better naming for "Start drawing again" ? I always wondered how you are supposed to access that if you've stopped drawing, afaik it resets the drawError property of the World (aka. PasteUpMorph) so it starts drawing normally again instead of something crossed out red. It is not done for submorphs, so it's not a convenient way of resetting all drawstates, do we really get drawErrors often enough in the PasteUpMorph itself to warrant this item??

March 26, 2010

Re: [Pharo-project] Problem with TransformationMorph

by Lukas Renggli

Ahh, with Squeak4.2.3beta1 I get the same as you. Not perfect, but already better. Any idea how the ugly expanded areas can be fixed? Lukas On 26 March 2010 11:06, Lukas Renggli <renggli(a)gmail.com> wrote: > 2010/3/26 Henrik Johansen <henrik.s.johansen(a)veloxit.no>: >> Hmmm, are you running on the latest VM's? > > I am using the Squeak4.2.2beta1 VM on OS X. > > The vertical text example looks like in the attached file. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > -- Lukas Renggli http://www.lukas-renggli.ch

March 26, 2010

Re: [Pharo-project] Problem with TransformationMorph

by Lukas Renggli

2010/3/26 Henrik Johansen <henrik.s.johansen(a)veloxit.no>: > Hmmm, are you running on the latest VM's? I am using the Squeak4.2.2beta1 VM on OS X. The vertical text example looks like in the attached file. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

March 26, 2010

Re: [Pharo-project] Problem with TransformationMorph

by Henrik Johansen

Hmmm, are you running on the latest VM's? With Pharo 1.1 and squeak 4.1, on both OSX and Windows I do not get black rectangles, but "expanded" black areas like attached. Cheers, Henry On Mar 26, 2010, at 10:41 42AM, Lukas Renggli wrote: >> It's not fixed in Squeak. >> WarpBlt does not work with alpha 0 > < 1. >> Another example is rotating a systemwindow (from the halo menu), its dropshadow will be pure black. (i.e. all non-transparent pixels are rendered with their pure RGB component) > > Ok, but what does this mean exactly? > > Previously it was possible to have rotated text. When rotating text it > now shows the complete bounding box in black, not just the aliased > borders. > > Lukas > >> >> Cheers, >> Henry >> >> (TransformationMorph is removed in Cuis 2.3, rotate halo button is there, but not working) >> >> On Mar 26, 2010, at 9:31 39AM, StÃ©phane Ducasse wrote: >> >>> lukas >>> >>> did you check in the latest version of squeak because I saw some fixes about put Morph in TextMorph? >>> Also in Cuis 2.0 because I imagine that juan got the same transformation. Now it seems that he changed that. >>> >>> Stef >>> On Mar 26, 2010, at 8:58 AM, Lukas Renggli wrote: >>> >>>> I noticed a problem with transformation morphs and created a bug report: >>>> >>>> http://code.google.com/p/pharo/issues/detail?id=2207 >>>> >>>> The problem seems to be that the transformation morph creates a black >>>> rectangle on the rotated clipping bounds. I does not only happen with >>>> TextMorphs but also with (some) other morphs. I tried to convert the >>>> TextMorph to a SketchMorph and the same happens there. I have no idea >>>> how to fix that problem. I need a solution because eCompletion rotates >>>> some text by 90, which is currently not possible. >>>> >>>> | stringMorph transformationMorph | >>>> stringMorph := 'vertical text' asMorph. >>>> transformationMorph := TransformationMorph new asFlexOf: stringMorph. >>>> transformationMorph angle: Float pi / 2. >>>> transformationMorph position: 5@5. >>>> transformationMorph openInWorld. >>>> >>>> Lukas >>>> >>>> -- >>>> Lukas Renggli >>>> http://www.lukas-renggli.ch >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 26, 2010

Re: [Pharo-project] Problem with TransformationMorph

by Lukas Renggli

> It's not fixed in Squeak. > WarpBlt does not work with alpha 0 > < 1. > Another example is rotating a systemwindow (from the halo menu), its dropshadow will be pure black. (i.e. all non-transparent pixels are rendered with their pure RGB component) Ok, but what does this mean exactly? Previously it was possible to have rotated text. When rotating text it now shows the complete bounding box in black, not just the aliased borders. Lukas > > Cheers, > Henry > > (TransformationMorph is removed in Cuis 2.3, rotate halo button is there, but not working) > > On Mar 26, 2010, at 9:31 39AM, StÃ©phane Ducasse wrote: > >> lukas >> >> did you check in the latest version of squeak because I saw some fixes about put Morph in TextMorph? >> Also in Cuis 2.0 because I imagine that juan got the same transformation. Now it seems that he changed that. >> >> Stef >> On Mar 26, 2010, at 8:58 AM, Lukas Renggli wrote: >> >>> I noticed a problem with transformation morphs and created a bug report: >>> >>> Â http://code.google.com/p/pharo/issues/detail?id=2207 >>> >>> The problem seems to be that the transformation morph creates a black >>> rectangle on the rotated clipping bounds. I does not only happen with >>> TextMorphs but also with (some) other morphs. I tried to convert the >>> TextMorph to a SketchMorph and the same happens there. I have no idea >>> how to fix that problem. I need a solution because eCompletion rotates >>> some text by 90, which is currently not possible. >>> >>> | stringMorph transformationMorph | >>> stringMorph := 'vertical text' asMorph. >>> transformationMorph := TransformationMorph new asFlexOf: stringMorph. >>> transformationMorph angle: Float pi / 2. >>> transformationMorph position: 5@5. >>> transformationMorph openInWorld. >>> >>> Lukas >>> >>> -- >>> Lukas Renggli >>> http://www.lukas-renggli.ch >>> >>> _______________________________________________ >>> 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 >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

March 26, 2010

Re: [Pharo-project] [update 1.1] #11296

by Alain Plantec

StÃ©phane Ducasse a Ã©crit : > 11296 > ----- > > Issue 2208: Preferences setting > * range setting: bad widget height in the SettingBrowser > * improve TimeProfiler (MorphTreeMorph example) Few words about that: TimeProfiler is a improvement of the current TimeProfileBrowser. just try it: TimeProfiler new openOnBlock: [ 10 timesRepeat: [Transcript show: 'n' asString, String cr]]. or simply TimeProfiler new open and then type-in the code you want to profile. For now, it is in the Morphic-MorphTreeWidget-Examples sys cat, maybe it can replace TimeProfileBrowser in the core. what do you think ? Cheers Alain

March 26, 2010

Re: [Pharo-project] Problem with TransformationMorph

by Henrik Johansen

It's not fixed in Squeak. WarpBlt does not work with alpha 0 > < 1. Another example is rotating a systemwindow (from the halo menu), its dropshadow will be pure black. (i.e. all non-transparent pixels are rendered with their pure RGB component) Cheers, Henry (TransformationMorph is removed in Cuis 2.3, rotate halo button is there, but not working) On Mar 26, 2010, at 9:31 39AM, StÃ©phane Ducasse wrote: > lukas > > did you check in the latest version of squeak because I saw some fixes about put Morph in TextMorph? > Also in Cuis 2.0 because I imagine that juan got the same transformation. Now it seems that he changed that. > > Stef > On Mar 26, 2010, at 8:58 AM, Lukas Renggli wrote: > >> I noticed a problem with transformation morphs and created a bug report: >> >> http://code.google.com/p/pharo/issues/detail?id=2207 >> >> The problem seems to be that the transformation morph creates a black >> rectangle on the rotated clipping bounds. I does not only happen with >> TextMorphs but also with (some) other morphs. I tried to convert the >> TextMorph to a SketchMorph and the same happens there. I have no idea >> how to fix that problem. I need a solution because eCompletion rotates >> some text by 90, which is currently not possible. >> >> | stringMorph transformationMorph | >> stringMorph := 'vertical text' asMorph. >> transformationMorph := TransformationMorph new asFlexOf: stringMorph. >> transformationMorph angle: Float pi / 2. >> transformationMorph position: 5@5. >> transformationMorph openInWorld. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> 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 >

March 26, 2010