- Pharo-dev - lists.pharo.org

[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

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