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

Re: [Pharo-dev] Survey - needing Protocol Chooser when creating methods from the debugger

by Ben Coman

Ben Coman wrote: > Just surveying opinion, when pressing the 'Create' (method) button in > the debugger, how critical do people consider the need for the > Protocol Chooser at that time? Personally I find it interrupts my > flow, since often I don't feel comfortable with the conventions to > choose which protocol it should go in. It makes me go searching in > another browser to try to determine the convention from other existing > methods. A few options to start with: > 1. Like it just the way it is. > 2. Dump the new method in unclassified and clean up later (plus a > protocol sorting refactoring tool) > 3. Having Protocol Chooser provide a short list of suggestions, > perhaps somehow indicating the rule used and weighting. For example: > "accessors (100 methods matching instance variables)" ; "testing (20 > items match 'is' prefix)"". > btw, In 2.0 the Protocol Chooser came up with a massive list (actually > where this survey question stems from) but in 3.0 the Protocol Chooser > comes up empty for my use cases. Can anyone suggest an example in 3.0 > that populates the Protocol Chooser? doh! I only needed to start typing to populate the Protocol Chooser. Now it still presents too many choices for my sensibilities. cheers -ben

June 15, 2014

[ann] beacon - a slim announcement-based logging engine

by Tudor Girba

Hi, I like very much the new energy people are putting into creating the SystemLogger engine for Pharo. I think this is a specifically important area for which we have to have a solution out of the box. At the same time, I also think that Pharo provides an infrastructure that makes room for ideas that are otherwise hard to reach in other languages or environments. Stef asked for collaborations around this project, so here is my literally small contribution: a rather different logging engine. It is called Beacon, it is based entirely on Announcements, it has ~200 lines of code, it has no tags or levels, and in my opinion it is fully functional. You can see a detailed description here including some informal comparisons with SystemLogger: http://www.humane-assessment.com/blog/beacon Please let me know what you think. I would be happy to join forces to reach a mature solution that is both versatile and that can show how Pharo is different. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

June 15, 2014

Survey - needing Protocol Chooser when creating methods from the debugger

by Ben Coman

Just surveying opinion, when pressing the 'Create' (method) button in the debugger, how critical do people consider the need for the Protocol Chooser at that time? Personally I find it interrupts my flow, since often I don't feel comfortable with the conventions to choose which protocol it should go in. It makes me go searching in another browser to try to determine the convention from other existing methods. A few options to start with: 1. Like it just the way it is. 2. Dump the new method in unclassified and clean up later (plus a protocol sorting refactoring tool) 3. Having Protocol Chooser provide a short list of suggestions, perhaps somehow indicating the rule used and weighting. For example: "accessors (100 methods matching instance variables)" ; "testing (20 items match 'is' prefix)"". btw, In 2.0 the Protocol Chooser came up with a massive list (actually where this survey question stems from) but in 3.0 the Protocol Chooser comes up empty for my use cases. Can anyone suggest an example in 3.0 that populates the Protocol Chooser? cheers -ben

June 15, 2014

Re: [Pharo-dev] ConfigurationOfIDE, ConfigurationOfMorphicUI

by stepharo

I love that. I got sick last week now I will try to allocate time to finish the widgets repackaging and your suggestions. stef On 10/6/14 22:02, Pavel Krivanek wrote: > Hi, > > I were successful in two small battles on the remodularization front. > Firstly I'm able again to build image with ConfigurationOfIDE: > > https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-3… > > This job takes the shrinked image and tries to load (almost) > everything back using configuration. > > The second goal I were able to reach is to take Morphic-Core image and > load the rest of Morphic packages without tools into it (only > Workspace and Transcript are present). > > https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-3… > > Both images are still dirty and unfinished, e.g. the second one has > some repainting problems, but we move forward. > > Cheers, > -- Pavel > >

June 15, 2014