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

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

by Benjamin

Why not something like bindKeyCombination:toAction: ? Ben On Jun 19, 2013, at 9:28 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > 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 Tristan Bourgois

2013/6/19 Erwan Douaille <douailleerwan(a)gmail.com> > Where is the demo/video ? :) > > There : http://www.youtube.com/watch?v=gGlEKtNKl7s :) > > 2013/6/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> tristan could you change the title to: >> Cade a Thales Framework in Pharo >> >> On Jun 19, 2013, at 9:56 AM, Tristan Bourgois <tristan.bourgois(a)gmail.com> >> wrote: >> >> >> >> >> 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 >>> >>> >> >> > > > -- > Best regards, > > Douaille Erwan <douaille.erwan(a)gmail.com> >

June 19, 2013

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

by Tristan Bourgois

2013/6/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > tristan could you change the title to: > Cade a Thales Framework in Pharo > > Done! > On Jun 19, 2013, at 9:56 AM, Tristan Bourgois <tristan.bourgois(a)gmail.com> > wrote: > > > > > 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] A little demo of Cade

by Erwan Douaille

Where is the demo/video ? :) 2013/6/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > tristan could you change the title to: > Cade a Thales Framework in Pharo > > On Jun 19, 2013, at 9:56 AM, Tristan Bourgois <tristan.bourgois(a)gmail.com> > wrote: > > > > > 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 >> >> > > -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

June 19, 2013

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

by StÃ©phane Ducasse

tristan could you change the title to: Cade a Thales Framework in Pharo On Jun 19, 2013, at 9:56 AM, Tristan Bourgois <tristan.bourgois(a)gmail.com> wrote: > > > > 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

Barcodes

by Torsten Bergmann

>About barcodes generation, why don't use Artefact directly ? If you look at the implementation you will see that barcode generation is mostly about implementing the correct encoding (to get a string with 0s and 1s) With this one can easily draw the lines on a form, a morph/canvas or directly in PDF. An easy way now is by using a form, see "BarcodeEAN13 example asForm" and then display this form in PDF via Artefact or use "asMorph openInWorld" Bye T.

June 19, 2013

[Ann] VMMaker + Cog building in Pharo20

by Guillermo Polito

So, I finished committing and made a last smoke test. VMMaker loads in Pharo2.0 and uses (mostly) Filesystem. I used the rewriting engine to rewrite some parts, and some others I made manually... To sum up: - I created a new version in configuration of cog: 6.5 (in the way I touched ConfigurationOfAsmJit for those related...) - I uploaded this configuration to old MetacelloRepository and MetaRepoForPharo20 in ss3. So you can use either of these: Gofer it squeaksource: 'MetacelloRepository'; configurationOf: 'Cog'; load. Gofer it squeaksource3: 'MetaRepoForPharo20'; configurationOf: 'Cog'; load. - Version 6.5 is intended to be used in Pharo 2.0. (ConfigurationOfCog project version: '6.5') load. - I tested building a pharo vm and a simple cog, *only in mac*. So, further testing is needed :) But it's a start. PharoVMBuilder buildMacOSX32. CogCocoaIOSConfig new generateForRelease; addExternalPlugins: #( FT2Plugin ); addInternalPlugins: #( UnixOSProcessPlugin ); "addThirdpartyLibrary: 'cairo';" generateSources; generate. So a next step is to update the gitorious scripts to use pharo 2.0 + cog 6.5 instead of pharo 1.4 + cog 6.4. And we probably have to review the numbering inside ConfigurationOfCog :). Guille

June 19, 2013

Re: [Pharo-dev] Block Printing in 3.0

by Marcus Denker

On Jun 19, 2013, at 9:58 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > 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? > We really need to take care to not enable too many things at once. For the Debugger, the next step is to enable by default the new Inspector implementationâ¦ Marcus

June 19, 2013

Re: [Pharo-dev] Block Printing in 3.0

by ClÃ©ment Bera

2013/6/19 Damien Cassou <damien.cassou(a)gmail.com> > 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? > > We cannot activate both Opal and the new debugger at the same time or we will not know from which of the 2 the highlighting / temp names bugs come from. So in at least a month. Moreover, the new debugger relies also on the new inspectors. So first the new inspectors should be activated by default (I will do that with Camillo in a few days / weeks), then 1 month after the new debugger can be activated. > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Asc*

June 19, 2013

Re: [Pharo-dev] Block Printing in 3.0

by Marcus Denker

On Jun 19, 2013, at 9:35 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > 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. > So what we already have is a first step towards "per AST Node" break/watch/inspect points. Together with the new debugger implementation and the new editor this will allow some quite fancy debugger improvements. Marcus

June 19, 2013