Re: [Pharo-dev] Color yzw

And it is in 50556 2016-01-29 13:39 GMT+01:00 Nicolai Hess : > > > 2016-01-29 13:10 GMT+01:00 Denis Kudriashov : > >> Hi Nicolai. >> Now your proposals in slice 17496 >>

[Pharo-dev] [pharo-project/pharo-core] c99e24: 50558

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: c99e24992162ba83eaacf95176c92ec9338c70c6 https://github.com/pharo-project/pharo-core/commit/c99e24992162ba83eaacf95176c92ec9338c70c6 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50558 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 6456a3: 50555

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 6456a3f5d3400e8efce6941a99ea425f7c3da45a https://github.com/pharo-project/pharo-core/commit/6456a3f5d3400e8efce6941a99ea425f7c3da45a Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50555 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 0def64: 50557

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 0def643003d9b5298ee0a5c4f06a3e6f4f8daa18 https://github.com/pharo-project/pharo-core/commit/0def643003d9b5298ee0a5c4f06a3e6f4f8daa18 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50557 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Nitpick: Launcher Colors

CyrilFerlicot wrote > When the launcher is in full screen and the label of the image/template > is short, it allow to click on the right row where there is nothing. > In Windows it happen a lot that the window is in full screen. Got it! Thanks for the explanation. I retract my suggestion :)

Re: [Pharo-dev] Color yzw

2016-01-29 13:10 GMT+01:00 Denis Kudriashov : > Hi Nicolai. > Now your proposals in slice 17496 > > . > We change it a little bit: we

Re: [Pharo-dev] Color yzw

Hi Nicolai. Now your proposals in slice 17496 . We change it a little bit: we make SelectorsTable lazy. And code completion uses it too. 2016-01-16 22:17

Re: [Pharo-dev] [pharo-project/pharo-core] 6456a3: 50555

this is, again, not true… integrator is seriously broken… looking at it now. > On 29 Jan 2016, at 12:28, GitHub wrote: > > Branch: refs/heads/5.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 6456a3f5d3400e8efce6941a99ea425f7c3da45a > >

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50556 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 885c7e: 50556

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 885c7e53d4beeb012d4bdeb6212400b8d5a36e4c https://github.com/pharo-project/pharo-core/commit/885c7e53d4beeb012d4bdeb6212400b8d5a36e4c Author: Jenkins Build Server Date:

Re: [Pharo-dev] Disable assertions (design by contract)

I tried to experiment with such behavior a while ago. I added an opal compiler extension here: http://smalltalkhub.com/mc/ClementBera/NeoCompiler/main . One needs to recompile the package after it is loaded as it uses a compiler extension. The idea was to introduce [ "some code" ] Cvalue, with

[Pharo-dev] Smalltalkhub scheduled maintenance next monday (February, 1st)

Hello, Smalltalk will be down next monday (february, 1st) from 12:30 to 13:30 (french local time). IT will add storage to the root partition. Regards, Christophe

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50559 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Contributing to Pharo

On 01/29/2016 09:02 AM, Bernhard Pieber wrote: Hi Dale, I am trying to understand this a little better. If a package containing metadata would be changed using a dialect which cannot interpret the metadata, wouldn’t or at least couldn’t it be broken or lost afterwards for a dialect which

Re: [Pharo-dev] Travis CI integration added to OSSubprocess and FFICHeaderExtractor

BTW, Esteban Maringolo asked me if the Travis scripts were "sharable". Well, Esteban Lorenzano shared them with me and I improved them a bit for my needs, so of course they are shareable! And all my projects listed as MIT, they are all MIT all the way down. Cheers, On Fri, Jan 29, 2016 at 3:36

[Pharo-dev] [pharo-project/pharo-core] 03f485: 50559

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 03f48517e360f34d4c97b75a5f3a77f32988a4de https://github.com/pharo-project/pharo-core/commit/03f48517e360f34d4c97b75a5f3a77f32988a4de Author: Jenkins Build Server Date:

Re: [Pharo-dev] Travis CI integration added to OSSubprocess and FFICHeaderExtractor

Cobrale! Cobrale! ;) > On 29 Jan 2016, at 18:28, Mariano Martinez Peck wrote: > > BTW, Esteban Maringolo asked me if the Travis scripts were "sharable". Well, > Esteban Lorenzano shared them with me and I improved them a bit for my needs, > so of course they are

Re: [Pharo-dev] Contributing to Pharo

Hi Dale, I am trying to understand this a little better. If a package containing metadata would be changed using a dialect which cannot interpret the metadata, wouldn’t or at least couldn’t it be broken or lost afterwards for a dialect which tries to interpret the metadata? At least if my

Re: [Pharo-dev] Contributing to Pharo

Hi David, > On Jan 29, 2016, at 2:45 PM, David Allouche wrote: > > Thanks Dale for all the explanations. > > How Monticello and version control relate in the big picture is starting to > make sense for me. > > Now, I better understand why filetree ended up uses a

Re: [Pharo-dev] Use cases for methods with optional parameters

On 23 January 2016 at 16:12, stepharo wrote: > If you have >>mother1 := foo:(bar:zork:fork) >>mother2 := foo:bar:(zork:bork:) >> > I'm not sure that this is allows in the same class. We should check that > in Python or ruby. > In Ruby: def m(x=42, y=51) → calling m(3)

[Pharo-dev] QualityAssistant feedback

I've just noticed for "Temporary variables not read AND written" that the offending variable in the temporary variable definition is highlighted. Is this new? Its very nice to have this visual indication. cheers -ben

Re: [Pharo-dev] Disable assertions (design by contract)

Eliot Miranda-2 wrote > Hi Richard, > >> On Jan 28, 2016, at 2:15 PM, Richard Sargent > richard.sargent@ > wrote: >> >> Aliaksei Syrel wrote >>> Hi >>> >>> Assertions play an important role in design by contract. It is great to >>> have assertions in Pharo out of box (Object>>#assert:).

Re: [Pharo-dev] Contributing to Pharo

Thanks Dale for all the explanations. How Monticello and version control relate in the big picture is starting to make sense for me. Now, I better understand why filetree ended up uses a file-per-method format, even though that is relatively hostile to git user interfaces optimised for other

Re: [Pharo-dev] Disable assertions (design by contract)

On Sat, Jan 30, 2016 at 9:34 AM, Richard Sargent wrote: > To that end, I was wondering about hacking the compiler to test the > association with the reference I've named Assert (but probably in a general > approach for any name). The code generator would send a

[Pharo-dev] GTDebugger feedback - Setup/TearDown tabs for test cases

I really like the SetUp/TearDown tabs when debugging a failed test, however it seems a waste to devote a whole half of window to them causing lines in the Source tab to wrap unnecessarily. Could they be moved adjacent to the Source tab? I guess the Browse button would equally apply to #setUp and

Re: [Pharo-dev] Travis CI integration added to OSSubprocess and FFICHeaderExtractor

For building Pharo, Squeak or GemStone projects on travis there is also the SmalltalkCI project: https://github.com/hpi-swa/smalltalkCI/blob/master/README.md Smalltalk language is supported by travis ;-) Sent from my iPhone > On 29 janv. 2016, at 18:28, Mariano Martinez Peck

Re: [Pharo-dev] [pharo-project/pharo-core] 075ec6: 50550

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 27/01/2016 16:07, GitHub wrote: > Branch: refs/heads/5.0 Home: > https://github.com/pharo-project/pharo-core Commit: > 075ec66df6ea08e7be71d5275b08ca095432aa2b > https://github.com/pharo-project/pharo-core/commit/075ec66df6ea08e7be7