- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [squeak-dev] code coverage

by Marcus Denker

On Feb 21, 2013, at 9:52 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > On 21 February 2013 19:52, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> Hi All, >> >> anyone have any bytecode-to-bytecode transformation tools for >> doing basic-block resolution coverage? > > Is it possible that Jejak [1] might vaguely fit this bill? It's a > tracing tool, but maybe one could hack something on the side to turn > it into a coverage tool? > > Certainly I've wanted a fine resolution (branch/block level) coverage > tool for a long time. > In Pharo 3.0 we will add Opal to the release (with the old Compiler to be an unload able package, to be killed as the first action in 4.0) This will allow *a lot* of very very interesting things to be done. Imagine this combined with -> a Parser that can parse code with syntax errors (in Pharo 2.0) -> a new ClassBuilder -> The first class Slots replacing instance variables (see the OOPLSA Paper) -> the new Debugger Model and UI -> the new text model It (slowly) start to get interesting! :-) Marcus

Feb. 22, 2013

[Pharo-project] Migrating ProfStef from Squeaksource to PharoExtras

by StÃ©phane Ducasse

Hi guys I'm migrating ProfStef to SmalltalkHub/PharoExtras. I'm also copying the configurationOf from MetacelloRepository and I will produce a new configuration for 2.0 and for SmalltalkHub. Stef

Feb. 21, 2013

Re: [Pharo-project] Pharo brainstorming workshop to produce Request For Improvements

by Sean P. DeNigris

StÃ©phane Ducasse wrote > So it would be good if we could organize a workshop where we do not code > but produce > Documented Requests for Improvement. > ... > What do you think? Great idea! And, it would be great to have a way to participate virtually for those that can't attend ;) -- View this message in context: http://forum.world.st/Pharo-brainstorming-workshop-to-produce-Request-For-I… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 21, 2013

Re: [Pharo-project] About Pharo extras

by phil＠highoctane.be

Same. 2013/2/21 Sean P. DeNigris <sean(a)clipperadams.com>: > StÃ©phane Ducasse wrote >> Everybody is welcome to be member and to help us > > Please add me to the team! > > Sean > > > > -- > View this message in context: http://forum.world.st/About-Pharo-extras-tp4671374p4671379.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Feb. 21, 2013

Re: [Pharo-project] About Pharo extras

by Sean P. DeNigris

StÃ©phane Ducasse wrote > Everybody is welcome to be member and to help us Please add me to the team! Sean -- View this message in context: http://forum.world.st/About-Pharo-extras-tp4671374p4671379.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 21, 2013

[Pharo-project] Pharo in Debian

by phil＠highoctane.be

Hello I am currently attempting to build the VM on Debian Linux (I grew tired of OSX lack of support for tools like Sourcenavigator and the like and Macports breaking all the time with the Xcode 4.x and so on). So, a question came to minid: Is there any reason why there is a squeak package in the Debian Linux but nothing about Pharo? (Or I didn't find it) I'd love to be able to do apt-get install pharo and just run. This would be nice to have just that, especially now that we can run headless, etc... I don't have a clue about Debian packaging but as there is already squeak, we may be able to reuse a bit. Phil

Feb. 21, 2013

Re: [Pharo-project] Pharo brainstorming workshop to produce Request For Improvements

by phil＠highoctane.be

Just food for tought: here is how this is done/documented in the TCL community: TIP: http://wiki.tcl.tk/983 We'd have a PIP, which sounds cool :-) Here is a sample list w/ format: http://www.tcl.tk/cgi-bin/tct/tip (TCT is Tcl Core Team) Phil 2013/2/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi guys > > we often meet to hack together and I would really like to take the time that > as a group we think about the improvements we want for the system. > For example luc and noury told me that the finalization for socket was brittle or combersome to use > and I imagine many other cases. > > I would like that we collect them so that we can address such points. > So it would be good if we could organize a workshop where we do not code but produce > Documented Requests for Improvement. > > Name > > Description: one line description > > Problem: > > Solution: > > What do you think? > > Stef > > > >

Feb. 21, 2013

[Pharo-project] About Pharo extras

by StÃ©phane Ducasse

Hi Pharoers We got a discussion in the team to see how we will handle packages that are not in the Pharo image but that some of us maintain or participate to maintain. For example Soup and XMLWriter, XMLSupportâ¦. ProfStef,â¦. We decided to create a separate team on SmalltalkHub named PharoExtras to host such projects. http://smalltalkhub.com/#!/~PharoExtras/ Everybody is welcome to be member and to help us. We want that each of these projects get also associated with a jenkins job that runs automatically the tests of the projects. Like that we can immediately see if a change get an impact on the close ecosystem. I started with camillo to do it for XMLWriter and I will do it some the projects I'm using. https://ci.inria.fr/pharo-contribution/job/XMLWriter/ http://smalltalkhub.com/#!/~PharoExtras/XMLWriter Stef

Feb. 21, 2013

Re: [Pharo-project] PharoConf Tutorial

by phil＠highoctane.be

Key concepts made clear. Examples for all widgets. Comments in classes. An explanation of how the whole thing works from a design principles point of view. Phil 2013/2/21 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com>: > Hi guys, > > if I do a Spec tutorial at Bern for the PharoConf, what would you like to be > the tutorial about ? :) > > Ben >

Feb. 21, 2013

Re: [Pharo-project] Pharo brainstorming workshop to produce Request For Improvements

by Tudor Girba

I think this is a very good idea. We could allocate a first slot at the PharoConf for this. Cheers, Doru On Feb 21, 2013, at 10:00 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > we often meet to hack together and I would really like to take the time that > as a group we think about the improvements we want for the system. > For example luc and noury told me that the finalization for socket was brittle or combersome to use > and I imagine many other cases. > > I would like that we collect them so that we can address such points. > So it would be good if we could organize a workshop where we do not code but produce > Documented Requests for Improvement. > > Name > > Description: one line description > > Problem: > > Solution: > > What do you think? > > Stef > > > > -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

Feb. 21, 2013