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

Re: [Pharo-dev] Also "create method" in traits

by Sebastian Tleye

:-) 2013/6/19 Damien Cassou <damien.cassou(a)gmail.com> > On Tue, Jun 18, 2013 at 3:48 PM, Sebastian Tleye <stleye(a)gmail.com> wrote: > > Done :) > > You can download the fix and not suffer anymore :P > > > thank you Sebastian. It's very cool to see you in this mailing list. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

June 19, 2013

Re: [Pharo-dev] Also "create method" in traits

by Damien Cassou

On Tue, Jun 18, 2013 at 3:48 PM, Sebastian Tleye <stleye(a)gmail.com> wrote: > Done :) > You can download the fix and not suffer anymore :P thank you Sebastian. It's very cool to see you in this mailing list. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 19, 2013

Re: [Pharo-dev] Block Printing in 3.0

by Damien Cassou

On Wed, Jun 19, 2013 at 9:35 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Yes, for end users, improving the debugger based on Opal should be the next step. when do we activate the new debugger by default? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 19, 2013

Re: [Pharo-dev] A little demo of Cade

by Tristan Bourgois

2013/6/19 Damien Cassou <damien.cassou(a)gmail.com> > On Tue, Jun 18, 2013 at 11:23 PM, Tristan Bourgois > <tristan.bourgois(a)gmail.com> wrote: > > I hope you like this little demo :) And I hope I could make some others > :) > > > That's really awesome work Tristan. Nevertheless, the 4th part of the > video is completely black for me. When will Cade be open-sourced :-)? > > Oh I forgot to put it in the video. Normally you have a view with more than 4000 shape displaying. May be I will put it in other demo because this demo is a bit old I made some upgrade on the framework especially about performance. When cade will be open-sourced... Hum good question... I have a lot of paperwork to do. > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

June 19, 2013

Re: [Pharo-dev] [update 3.0] #30207

by Damien Cassou

On Wed, Jun 19, 2013 at 8:46 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Yesâ¦ we managed to run out of known bugs. So let's find some moreâ¦ :-) Marcus is on fire this morning!! Keep going. It's not even 10am, so the best is still to come. 2 hours left :-). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 19, 2013

Re: [Pharo-dev] Block Printing in 3.0

by Sven Van Caekenberghe

On 19 Jun 2013, at 08:52, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jun 13, 2013, at 2:48 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On Jun 13, 2013, at 2:23 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >>> Why do we get [...] when Opal is not active? Why can't we keep the old >>> behavior? >>> >> >> >> Soon we will switch to Opal, there are just 2 bugs left (that I know of ;-) >> We where a bit distracted last week so there was no progress on thoseâ¦ soon. >> > > Blocks are now pretty-printed again. > > In addition, the new bytecode->AST->source mapping is active, this should speed > up the Debugger a bit and should fix some long standing highlighting bugs. > > (But due to the inherent complexity of the whole thing, it fire sure will have some > problems, we will see. The good thing is that problems should be easy to debug > due to the explicit AST/IR based mapping) > > Marcus > Yes, for end users, improving the debugger based on Opal should be the next step. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

June 19, 2013

Re: [Pharo-dev] [update 3.0] #30207

by Sven Van Caekenberghe

On 19 Jun 2013, at 08:46, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 30207 > ----- > > 10944 Enable Opal in 3.0 > https://pharo.fogbugz.com/f/cases/10944 > > Just does a > > SmalltalkImage compilerClass: OpalCompiler. > OpalCompiler recompileAll. > > Yesâ¦ we managed to run out of known bugs. So let's find some moreâ¦ :-) Great work. It was impressive to see all this activity the last couple of months. It feels good that so much testing and QA was done. Thx, Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

June 19, 2013

Re: [Pharo-dev] on:do: for shortcuts?

by StÃ©phane Ducasse

excellent so how do we integrate this change? I will chnage the chapter on keymapping :) On Jun 18, 2013, at 9:57 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > I prefer the onKeyCombination* because of the following rationale: > > - to me a shortcut is the association between a key combination and an action > - a key combination is a combination of keys :), which is associated with an action > > Stef, so far I changed the asShortcut => asKeyCombination, following the same idea :). > > Guille > > > On Tue, Jun 18, 2013 at 8:25 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Jun 18, 2013, at 7:21 PM, GOUBIER Thierry <thierry.goubier(a)cea.fr> wrote: > > > The problem with onkeypress, onkeydown, onkeyup is that they are low-level events compared to the shortcuts we are talking about. > > > > A shortcut is at least one key, but is usually a key + a modifier or a sequence of key + modifiers (such as the emacs ^X ^C ($x ctrl, $c ctrl). The Keymapping stuff sits a lot higher than the basic keypress events (which do exist as well) and can recognize multi-keys combinations. If you call that onKeyPress:do:, then you loose in the name part of the power of it. > > > > Hence the onKeyCombination:do: (but I prefer onShortcut:do:) > > onShortcut:do: looks good to me. > > Stef > > > > > > Thierry > > ________________________________________ > > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Esteban A. Maringolo [emaringolo(a)gmail.com] > > Date d'envoi : mardi 18 juin 2013 18:14 > > Ã : Pharo Development List > > Objet : Re: [Pharo-dev] on:do: for shortcuts? > > > > 2013/6/18 ClÃ©ment Bera <bera.clement(a)gmail.com> > > > >> On Javascript, there are : > >> > >> onkeypress > >> onkeydown > >> onkeyup > >> > >> > >> I think we should have same API than other languages, especially popular ones. So 1 of these 3 would be the best for me. > >> > >> Why not onKeyPress:do: ? > > > > +1 to each of the last two statements. > > > > > > >

June 19, 2013

Re: [Pharo-dev] A little demo of Cade

by Damien Cassou

On Tue, Jun 18, 2013 at 11:23 PM, Tristan Bourgois <tristan.bourgois(a)gmail.com> wrote: > I hope you like this little demo :) And I hope I could make some others :) That's really awesome work Tristan. Nevertheless, the 4th part of the video is completely black for me. When will Cade be open-sourced :-)? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

June 19, 2013

Re: [Pharo-dev] Block Printing in 3.0

by Marcus Denker

On Jun 13, 2013, at 2:48 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jun 13, 2013, at 2:23 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > >> Why do we get [...] when Opal is not active? Why can't we keep the old >> behavior? >> > > > Soon we will switch to Opal, there are just 2 bugs left (that I know of ;-) > We where a bit distracted last week so there was no progress on thoseâ¦ soon. > Blocks are now pretty-printed again. In addition, the new bytecode->AST->source mapping is active, this should speed up the Debugger a bit and should fix some long standing highlighting bugs. (But due to the inherent complexity of the whole thing, it fire sure will have some problems, we will see. The good thing is that problems should be easy to debug due to the explicit AST/IR based mapping) Marcus

June 19, 2013