May 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Bug in SimpleSwitchMorph

by stephane ducasse

may be the behavior is normal because it wants to encode that - if we press and keep pressed and get outside the morph then nothing should happen once we release the button. Now there is still something strange. It is really slow and this behavior should be customised because for certain cases I just want to get the click in any situation. Stef (good night now for real). On May 20, 2013, at 10:50 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > It seems that the bug is link with the fact that the cursor get outside the bounds or not. > If you click and do not move or move but stay inside the morph it is ok > Now if you click and the mouse gets outside the bounds we get the funny and bad behavior. > > I'm definitely exhausted now to thinkâ¦. but here is the code for the night hackers :) > > > > > mouseDown: evt > > oldColor := self fillStyle. > > mouseMove: evt > > (self containsPoint: evt cursorPoint) > ifTrue: [self setSwitchState: (oldColor = offColor)] > ifFalse: [self setSwitchState: (oldColor = onColor)]. > > mouseUp: evt > > (self containsPoint: evt cursorPoint) > ifTrue: [ "toggle and do action" > self setSwitchState: (oldColor = offColor). > self doButtonAction] > ifFalse: [ "restore old appearance" > self setSwitchState: (oldColor = onColor)]. > >

May 20, 2013

Re: [Pharo-dev] Bug in SimpleSwitchMorph

by StÃ©phane Ducasse

Hi It seems that the bug is link with the fact that the cursor get outside the bounds or not. If you click and do not move or move but stay inside the morph it is ok Now if you click and the mouse gets outside the bounds we get the funny and bad behavior. I'm definitely exhausted now to thinkâ¦. but here is the code for the night hackers :) mouseDown: evt oldColor := self fillStyle. mouseMove: evt (self containsPoint: evt cursorPoint) ifTrue: [self setSwitchState: (oldColor = offColor)] ifFalse: [self setSwitchState: (oldColor = onColor)]. mouseUp: evt (self containsPoint: evt cursorPoint) ifTrue: [ "toggle and do action" self setSwitchState: (oldColor = offColor). self doButtonAction] ifFalse: [ "restore old appearance" self setSwitchState: (oldColor = onColor)].

May 20, 2013

Bug in SimpleSwitchMorph

by StÃ©phane Ducasse

Hi guys We found a bug programming lightsout. Apparently when we click and do not move the mouse, one click event is received. Now if we click and move the mouse, it looks like two clicks are received. You can see that really easily on the Class side toggle in Nautilus or in the slice selector, since both use the SwitchMorph. I'm going to bed now but I think that we should have a look at it and smash it :) Stef

May 20, 2013

Re: [Pharo-dev] collaborActive book refers to SS

by Serge Stinckwich

About the current pull requests: - I merge 1 of them that correct some typo: https://github.com/SquareBracketAssociates/PharoByExample-english/pull/18 I close (that was apparently an experiment from Ben): https://github.com/SquareBracketAssociates/PharoByExample-english/pull/16 There is 2 pull requests left: - https://github.com/SquareBracketAssociates/PharoByExample-english/pull/8 Some work about DBXTalk done by Guile. Not sure if this work has been integrated in PBE2 ? - https://github.com/SquareBracketAssociates/PharoByExample-english/pull/19 Some modifications proposed by Frank but this is for a new version of PBE1 (for Pharo 2.0). Stef, apparently you remove everything related to PBE2 in this repository. This is great ! We should focused in this repository on PBE1 versions. Some months ago, I made a Pharo1.4 branch for updating the PBE1 book to 1.4 but unfortunately no work has been done. I think we can remove this branch now. Can we discuss about a workflow for managing the PBE1 versions. I suggest using something like that: http://nvie.com/posts/a-successful-git-branching-model/ The master branch used for last stable version of the book and a devel branch for new version. Comments ? Regards, On Mon, May 20, 2013 at 11:13 AM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > Thanks, Serge. > > frank > > On 20 May 2013 09:20, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> Frank, nobody take care about pull issues on this repository. >> There is 4 of them here : >> https://github.com/SquareBracketAssociates/PharoByExample-english/pulls >> I can try to merge some of them. >> >> Regards, >> >> On Sat, May 18, 2013 at 7:50 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>> Hi Stef, >>> >>> I mean this guy: >>> https://github.com/SquareBracketAssociates/PharoByExample-english/pull/19 >>> >>> frank >>> >>> On 18 May 2013 15:52, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>> frank you are about Pharo by example (which is hosted on github)? >>>> >>>> I'm checking because PBE2 is on github but this is an old version since I moved the chapter to svn. >>>> >>>> Stef >>>> >>>> >>>> On May 16, 2013, at 12:44 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>> >>>>> >>>>> On May 16, 2013, at 12:13 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>>>> >>>>>> On 16 May 2013 10:38, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>>>>> >>>>>>> On May 16, 2013, at 11:23 AM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>>>>>> >>>>>>>> http://book.pharo-project.org/book/Tidbits/FAQ/Packages/ >>>>>>>> >>>>>>>> talks about how you can create a SqueakSource project. Presumably we >>>>>>>> want this to explain either how to create an SS3 project or a StHub >>>>>>>> project? >>>>>>>> >>>>>>>> If all I need to do is issue a pull request to >>>>>>>> https://github.com/SquareBracketAssociates/PharoByExample-english/ I'm >>>>>>>> happy to update it to whichever you prefer. >>>>>>> >>>>>>> please do :) >>>>>> >>>>>> I'm guessing you'd want to point to StHub? >>>>> >>>>> yes >>>>> >>>>>> (I use ss3 for everything, >>>>>> but it seems most of the Pharo devs are pushing for StHub.) >>>>> >>>>> Yes >>>>> >>>>> >>>> >>>> >>> >> >> >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

May 20, 2013

Re: [Pharo-dev] AST Everywhere, Reflectivity

by Frank Shearar

On 20 May 2013 19:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On May 20, 2013, at 8:13 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > >> >> Like with ifTrue:, whileTrue: and friends: you can still use futures >> in Squeak if you don't have FutureNode in your image, but things will >> just run slower. >> > > But there is no IfTrueNode, either. > > The AST models the grammar of the language, that's why it is called Syntax treeâ¦. Sure. I have no idea why it's implemented that way. Perhaps it was easier or desirable to keep the transformation out of the base image or something. Josh Gargus might know. I would imagine that in Opal you wouldn't need to do that :) You'd hook in custom emitters somewhere, and be done. frank > Marcus > > >

May 20, 2013

Re: [Pharo-dev] AST Everywhere, Reflectivity

by stephane ducasse

Hacking inside the compiler instead of extending it to support a good static way of declaring transformations is way to: - make the system more complex, less modular - hamper tools to use a good infrastructure - push hacks and hidden knowledge in all the layers. Definitively not a good idea. This is why opal has a open architecture for plugins. Stef >>>>> I just started following this Dev mailing list, and I saw that 'AST >>>>> Everywhere' and 'Reflectivity' were mentioned as very promising (I >>>>> already know about Slots). >>>>> Can someone in a nutshell please describe these developments? Thanks, >>>> >>>> >>>> Right now, the compiler uses it's own AST, Syntax highlighting uses a very minimal >>>> token stream (and it's own parser), the refactoring engine has one, too. >>>> And then there is Bytecode which is used by the Debugger, for example. >>>> >>>> As a first step we plan to use the Refactoring AST for everything >>>> (Compiler, Refactoring, Syntax highlighting ) >>> >>> I keep forgetting to ask - does the Refactoring AST have an equivalent >>> of Squeak's FutureNode? (It's not semantically necessary to have one >>> to support futures; it's a performance enhancer.) >> >> what do you mean by performance enhancer? > > Like with ifTrue:, whileTrue: and friends: you can still use futures > in Squeak if you don't have FutureNode in your image, but things will > just run slower. > > frank > >>> frank >>> >> >> >

May 20, 2013

Re: [Pharo-dev] AST Everywhere, Reflectivity

by Marcus Denker

On May 20, 2013, at 8:13 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > > Like with ifTrue:, whileTrue: and friends: you can still use futures > in Squeak if you don't have FutureNode in your image, but things will > just run slower. > But there is no IfTrueNode, either. The AST models the grammar of the language, that's why it is called Syntax treeâ¦. Marcus

May 20, 2013

Re: [Pharo-dev] AST Everywhere, Reflectivity

by Frank Shearar

On 20 May 2013 18:35, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > > On May 20, 2013, at 6:15 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > >> On 20 May 2013 16:57, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> On May 20, 2013, at 4:44 PM, Paul Davidowitz <pdavidow(a)fastmail.fm> wrote: >>> >>>> I just started following this Dev mailing list, and I saw that 'AST >>>> Everywhere' and 'Reflectivity' were mentioned as very promising (I >>>> already know about Slots). >>>> Can someone in a nutshell please describe these developments? Thanks, >>> >>> >>> Right now, the compiler uses it's own AST, Syntax highlighting uses a very minimal >>> token stream (and it's own parser), the refactoring engine has one, too. >>> And then there is Bytecode which is used by the Debugger, for example. >>> >>> As a first step we plan to use the Refactoring AST for everything >>> (Compiler, Refactoring, Syntax highlighting ) >> >> I keep forgetting to ask - does the Refactoring AST have an equivalent >> of Squeak's FutureNode? (It's not semantically necessary to have one >> to support futures; it's a performance enhancer.) > > what do you mean by performance enhancer? Like with ifTrue:, whileTrue: and friends: you can still use futures in Squeak if you don't have FutureNode in your image, but things will just run slower. frank >> frank >> > >

May 20, 2013

Re: [Pharo-dev] AST Everywhere, Reflectivity

by stephane ducasse

On May 20, 2013, at 6:15 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 20 May 2013 16:57, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On May 20, 2013, at 4:44 PM, Paul Davidowitz <pdavidow(a)fastmail.fm> wrote: >> >>> I just started following this Dev mailing list, and I saw that 'AST >>> Everywhere' and 'Reflectivity' were mentioned as very promising (I >>> already know about Slots). >>> Can someone in a nutshell please describe these developments? Thanks, >> >> >> Right now, the compiler uses it's own AST, Syntax highlighting uses a very minimal >> token stream (and it's own parser), the refactoring engine has one, too. >> And then there is Bytecode which is used by the Debugger, for example. >> >> As a first step we plan to use the Refactoring AST for everything >> (Compiler, Refactoring, Syntax highlighting ) > > I keep forgetting to ask - does the Refactoring AST have an equivalent > of Squeak's FutureNode? (It's not semantically necessary to have one > to support futures; it's a performance enhancer.) what do you mean by performance enhancer? > > frank >

May 20, 2013

Re: [Pharo-dev] AST Everywhere, Reflectivity

by Marcus Denker

On May 20, 2013, at 6:52 PM, Paul Davidowitz <pdavidow(a)fastmail.fm> wrote: > All this sounds fascinating, but has any thought been given to ease of > maintainability, understandability, and debuggability of software > written using these features? > You don't write software using these features. You write *Tools* and you *change* the language using this. Normal programmers should not use it for anything. Marcus

May 20, 2013