Re: [Pharo-dev] About the non-use of Announcer in Bloc

Probably from the use of critical (mutex), the way #subscriptionsHandling: is done, and that Announcer is built for X number of announcers and Y number of subscribers, which means that each announcement the announcer has to filter and find the correct subscribers. | ann a | ann :=

[Pharo-dev] About the non-use of Announcer in Bloc

Hi all, Doru, Stephan, Norbert, Denis and me spoke at ESUG about the non-use of Announcer in Bloc. I made some test cases in Bloc-Tests to compare performances between Announcer and BlEventRegistry. The result is that Announcer is at least 5x slower in all tested cases. Bloc has only specific

Re: [Pharo-dev] Iceberg: success and fail

I wrote an issue here: https://github.com/npasserini/iceberg/issues/124 There are several PRs apparently than you can push Nicolas I guess: https://github.com/npasserini/iceberg/pulls Thank you for the good job. On Sat, Aug 27, 2016 at 12:06 AM, Nicolas Passerini wrote:

Re: [Pharo-dev] looking into Pharo VM

> On 28 Aug 2016, at 15:38, Ben Coman wrote: > > Peter, The plan seems to be [1] to make the OpenSmalltalkVM a submodule under > the pharo-vm. > > Esteban, Is this still the current plan, and when will this be done? I can't > see an osvm folder at [2] yet. Are the

Re: [Pharo-dev] looking into Pharo VM

Peter, The plan seems to be [1] to make the OpenSmalltalkVM a submodule under the pharo-vm. Esteban, Is this still the current plan, and when will this be done? I can't see an osvm folder at [2] yet. Are the build instructions there still valid? Is there anything I can do to help? cheers -ben

Re: [Pharo-dev] About Pharo 60

> what are the points you are working on and that would deserve more focus and > help from the community? I once started with a refactored version of GetText, covered with tests and tools. Code status I reached so far is here: http://www.smalltalkhub.com/#!/~TorstenBergmann/Gettext Idea

Re: [Pharo-dev] broken GitFileTree/IceBerg on Windows because of ProcessWrapper

On Sat, Aug 27, 2016 at 08:24:32AM -0300, Hernán Morales Durand wrote: > Just checked and the download URL is working. > If you send me mirror URLs then I can update the configuration to support > multiple download locations. The University's whole website was down when I was trying to access it,

Re: [Pharo-dev] looking into Pharo VM

> Why you say so? It is maintained, and still the official pharo distribution. Because of this: ​ which coincided with the announcement of OpenSmalltalkVM... that's why I wasn't sure what is the mainline. (Or maybe you took a vacation, which is also an explanation :)... which reminds me that I

Re: [Pharo-dev] looking into Pharo VM

By the way first thing I would do is to remove FT2 plugin and see how it works > On 28 Aug 2016, at 14:38, Peter Uhnak wrote: > > Hi, > > I wanted to start looking into VMs a bit (because crashing several times a > day for months now is really pushing my temper), but now I

Re: [Pharo-dev] looking into Pharo VM

Hi, > On 28 Aug 2016, at 14:38, Peter Uhnak wrote: > > Hi, > > I wanted to start looking into VMs a bit (because crashing several times a > day for months now is really pushing my temper), but now I am not sure what > is actually the VM. > > This is what it used to be

[Pharo-dev] looking into Pharo VM

Hi, I wanted to start looking into VMs a bit (because crashing several times a day for months now is really pushing my temper), but now I am not sure what is actually the VM. This is what it used to be https://github.com/pharo-project/pharo-vm, but it's maintained anymore. So there's this

Re: [Pharo-dev] Binary selector and special characters

See RBParserTest>>#testBinarySelectors It's based on the draft ANSI Smalltalk-80 standard. You integrated it. It tests the RBParser's parsing of binary method definitions and message sends of all binary selectors from 1 char upto 3 chars. (The Blue Book is more restrictive than ANSI, limiting

Re: [Pharo-dev] About Pharo 60

Hi, The answer was that Spotter is not different in any way than any other global shortcut. This means that if we want to have an interactive solution, we should do it at the level of the Keymapping framework not at the level of individual tools. In the meantime, how do we manage this?

Re: [Pharo-dev] Layout in bloc

Other questions, where are the layout you have showed me at ESUG? Is there a tree layout? If no, then I can port the one of Roassal. Alexandre > On Aug 28, 2016, at 5:18 AM, Aliaksei Syrel wrote: > > Hi > > Thanks for the example. Exactly, ability to have elements that

Re: [Pharo-dev] Layout in bloc

Thanks Alex! Cheers, Alexandre > On Aug 28, 2016, at 5:18 AM, Aliaksei Syrel wrote: > > Hi > > Thanks for the example. Exactly, ability to have elements that are visible > but not participate in layout is very important. But first I would like to > describe bloc

Re: [Pharo-dev] Layout in bloc

Hi Thanks for the example. Exactly, ability to have elements that are visible but not participate in layout is very important. But first I would like to describe bloc layout a bit more. - If you think for a second about the meaning of "layout" you would realize

Re: [Pharo-dev] About Pharo 60

> On 28 Aug 2016, at 00:55, Cyril Ferlicot D. wrote: > > Le 27/08/2016 à 14:32, Esteban Lorenzano a écrit : >> yes, some years ago I made a package for this. >> later Ben tried something similar with the user manager. >> none of those approaches worked as general

Re: [Pharo-dev] ensure blocks in TestCase>>tearDown are not run if an error occurs inside ensured block when test itself was halted ...

Hi dale Le 8/8/16 à 15:00, Dale Henrichs a écrit : Max, Thanks for looking into this. Do you think that this bug will be fixed in Pharo5.0? When I'm debugging the tests with this fatal pattern, my only recourse is to start and stop images between test runs ... Definitively. We do

Re: [Pharo-dev] ensure blocks in TestCase>>tearDown are not run if an error occurs inside ensured block when test itself was halted ...

Thank you all for taking care and feeling like Pharo is your baby :). Stef Le 8/8/16 à 09:11, Max Leske a écrit : Thanks Nicolai. I’ve opened an issue on phogbugz: https://pharo.fogbugz.com/f/cases/18885/Ensure-blocks-in-test-tear-down-not-always-executed. On 8 Aug 2016, at 09:03,

Re: [Pharo-dev] [Pharo-users] [ann] GTExamples alpha

Hi, > On Aug 26, 2016, at 10:01 PM, Nicolai Hess wrote: > > > > 2016-08-26 0:51 GMT+02:00 Tudor Girba : > Hi, > > I just tried again, and the latest GToolkit image does contain FileSystem > class >> gtExampleZip: > > Yes, it is there, but not

Re: [Pharo-dev] [ann] GTExamples alpha

Hi Nicolai, > On Aug 26, 2016, at 10:08 PM, Nicolai Hess wrote: […] > > And the menu entries are ... unfortunate (see screenshot), what you put in, > > the whole source as menu label? > > Hmm. Something is strange there. I get the name of a method, not the source >

Re: [Pharo-dev] About better communication in the community

Hi, I think this is a great idea. Thanks for opening the issues. Now, the only question is where to put these. You suggest the package Manifest. I think this would work for individual packages, but as we are moving to projects (with Metacello), I would suggest to put these methods in the

Re: [Pharo-dev] About Pharo 60

Thanks Cyril Now we have to check what is synectique specific from what should be pushed to Pharo. Since we moved to a Seaside application not so long after I joined Synectique we only disable some basic things. If I don't say anything wrong here is what we did: - Remove repositories