Re: [Pharo-dev] [REMEMBER] Tech meeting rue 27/09 16UTC - We'll talk about current PharoVM ongoing development

I noticed only in a side conversation recently (rather than an announcement, did I miss something?) that the change of development process to now just submit slices to inbox and configurations get sorted later (which makes things simpler - but I wonder how configurations are then maintained.

Re: [Pharo-dev] [REMEMBER] Tech meeting rue 27/09 16UTC - We'll talk about current PharoVM ongoing development

I noticed only in a side conversation recently (rather than an announcement, did I miss something?) that the change of development process to now just submit slices to inbox and configurations get sorted later (which makes things simpler - but I wonder how configurations are then maintained.

Re: [Pharo-dev] FFI callout arguments - references to internal objects

Hi Esteban, Your advice lead me to make some progress. Could you have a review? http://blog.openinworld.com/2016/09/pharo-libclang-ffi-part-5-client-data-and-recursive-visitorcallbacks/ Its perhaps a little low level and I'd like to make CXClientData a wrapper for some of the complexity. But

Re: [Pharo-dev] Traits explicitRequirement -- and TClassDescription

I would like to remove traits users from metaclass class description. I do not think that they are worht hteh complexity they bring. Stef Le 26/9/16 à 16:16, Ben Coman a écrit : I'm not familiar with the #explicitRequirement I see sent in Slice 17798. Could someone explain why that is better

Re: [Pharo-dev] [REMEMBER] Tech meeting rue 27/09 16UTC - We'll talk about current PharoVM ongoing development

Ah yes, I forget the “small detail” of linking my channel :) https://www.livecoding.tv/estebanlm/ (I never tried, so this can fail ;) cheers, Esteban > On 26 Sep 2016, at 16:40, Esteban Lorenzano wrote: > > Hello, > > I will

[Pharo-dev] [REMEMBER] Tech meeting rue 27/09 16UTC - We'll talk about current PharoVM ongoing development

Hello, I will handle the first tech meeting tomorrow, as preview. After several considerations, I will be trying “livecoding.tv” (no idea if this is worst or better than twitch… and I’m not very happy with the fact that this is a “tv format” and not a “conversation format”, but well, we’ll

Re: [Pharo-dev] Traits explicitRequirement -- and TClassDescription

> On 26 Sep 2016, at 15:16, Ben Coman wrote: > > I'm not familiar with the #explicitRequirement I see sent in Slice 17798. > Could someone explain why that is better than calling... > self setName: aSymbol. > Traits don’t have instance variables, so you somehow need

[Pharo-dev] Traits explicitRequirement -- and TClassDescription

I'm not familiar with the #explicitRequirement I see sent in Slice 17798. Could someone explain why that is better than calling... self setName: aSymbol. Also, another thing I've been curious about for a while, what is the advantage of having TClassDescription when it only has one user

[Pharo-dev] Full-Time Academic Position, University of Chile

Dear All, We have an open academic position. Full-Time Academic Position Computer Science Department, University of Chile http://www.dcc.uchile.cl The Computer Science Department of the University of Chile (DCC) is offering a full-time permanent position to carry out research and teaching,

Re: [Pharo-dev] comparison statistics

Well no complains from me, I think Pharo is doing great. Hope I can find a nice way to use it with a C++ executable, so I can use it in my games. On Mon, Sep 26, 2016 at 7:01 AM Ben Coman wrote: > Of course the saying goes "There are three types of lies: lies, damn > lies

Re: [Pharo-dev] AbstractLayout class comment

On Mon, Sep 26, 2016 at 2:54 PM, Marcus Denker wrote: > yes, needs update. can you add an issue? https://pharo.fogbugz.com/default.asp?19142 P.S. If its easier for you to type the comment here, I can issue to slice. cheers -ben > >> On 26 Sep 2016, at 07:50, Ben Coman

Re: [Pharo-dev] glitches in text selection

2016-09-25 4:50 GMT+02:00 Sean P. DeNigris : > Nicolai Hess-3-2 wrote > > Yes, see case 19113, fixed in 60233 > > Is this related to > https://pharo.fogbugz.com/f/cases/19036/Bizarre-Text- > Selection-in-Pharo-5-0 No. > > ? If so, I strongly suggest we backport it. The

Re: [Pharo-dev] AbstractLayout class comment

yes, needs update. can you add an issue? > On 26 Sep 2016, at 07:50, Ben Coman wrote: > > Minor thing... > AbstractLayout class comment says... > > "There are special cases of layouts without slots, like NilLayout or > BitsLayout." > > but I see no NilLayout in the