Re: [Pharo-dev] [pharo-project/pharo-core] e03e64: 40495

:) Ok, this was (more or less) a test run with just some small changes. Now the bigger part. 2015-02-17 11:02 GMT+01:00 Tudor Girba : > This is great indeed! > > Doru > > On Tue, Feb 17, 2015 at 10:17 AM, Sven Van Caekenberghe > wrote: > >> >> > On 17 Feb 2015, at 10:09, Marcus Denker wrote:

Re: [Pharo-dev] About Matrix API access

stepharo wrote > ... > | matrix23 | > matrix23 := Matrix rows: 3 columns: 2. > matrix23 at: 1 at: 1 put: 11. What? #at:at:put:? That *will* cause errors. The "at"s are effectively anonymous keywords. I hope the API can still be changed. e.g. #atRow:column:put: and possibly also #atColumn:row:put:

Re: [Pharo-dev] GSOC 2015 Call for Ideas

We have something like 45 projects ideas at the moment. We really need more project ideas from more people (not only RMOD guys). Even if you have a vague idea, you can contribute. Thank you. Regards, On Sun, Feb 15, 2015 at 3:23 PM, Serge Stinckwich wrote: > Dear pharoers, > > this year Pharo

Re: [Pharo-dev] [pharo-project/pharo-core] e03e64: 40495

This is great indeed! Doru On Tue, Feb 17, 2015 at 10:17 AM, Sven Van Caekenberghe wrote: > > > On 17 Feb 2015, at 10:09, Marcus Denker wrote: > > > > > >> > >> Log Message: > >> --- > >> 40495 > >> 14934 Load new Athens configuration 2.8 > >> https://pharo.fogbugz.com/f/cases/149

Re: [Pharo-dev] [pharo-project/pharo-core] a67750: 40496

> On 17 Feb 2015, at 10:54, Marcus Denker wrote: > > >> --- >> 40496 >> 14935 Load new configuratoin of TxText 2.8.2 >> https://pharo.fogbugz.com/f/cases/14935 >> > > with the following fixes > case 14778 TxAthensLayoutView should not impose a x offset minimal value > case 1477

Re: [Pharo-dev] [pharo-project/pharo-core] a67750: 40496

> --- > 40496 > 14935 Load new configuratoin of TxText 2.8.2 > https://pharo.fogbugz.com/f/cases/14935 > with the following fixes case 14778 TxAthensLayoutView should not impose a x offset minimal value case 14774

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

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

[Pharo-dev] [pharo-project/pharo-core] a67750: 40496

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: a677509d8bbf88ddc617e810a46686feac0d3b1b https://github.com/pharo-project/pharo-core/commit/a677509d8bbf88ddc617e810a46686feac0d3b1b Author: Jenkins Build Server Date: 2015-02-17 (Tue, 17 Feb 2015

Re: [Pharo-dev] [pharo-project/pharo-core] e03e64: 40495

> On 17 Feb 2015, at 10:09, Marcus Denker wrote: > > >> >> Log Message: >> --- >> 40495 >> 14934 Load new Athens configuration 2.8 >> https://pharo.fogbugz.com/f/cases/14934 >> > > > This fixes the following issues > > case 14723 Make StrikeFonts working in Athens (font size r

Re: [Pharo-dev] [pharo-project/pharo-core] e03e64: 40495

> > Log Message: > --- > 40495 > 14934 Load new Athens configuration 2.8 > https://pharo.fogbugz.com/f/cases/14934 > This fixes the following issues case 14723 Make StrikeFonts working in Athens (font size related) case 14710 AthensCairoCanvas setAA not implemented case 14799

Re: [Pharo-dev] Number>>#percent

I'm also in favor to have it as default in the core. It is a so basic thing. I was also searching for this feature a few days ago. On another hand, one could also argue that 12/100 does the job but is less intention revealing. Another thing that I find is missing in the core is the support for cu

[Pharo-dev] [pharo-project/pharo-core] e03e64: 40495

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: e03e6486a5fae6f8a76e3450f7fa43c1672f7279 https://github.com/pharo-project/pharo-core/commit/e03e6486a5fae6f8a76e3450f7fa43c1672f7279 Author: Jenkins Build Server Date: 2015-02-17 (Tue, 17 Feb 2015

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

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

[Pharo-dev] [pharo-project/pharo-core] a1c317: 40494

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: a1c3174a6913eaa3f0d857e6d706cefb1e9cc0ff https://github.com/pharo-project/pharo-core/commit/a1c3174a6913eaa3f0d857e6d706cefb1e9cc0ff Author: Jenkins Build Server Date: 2015-02-17 (Tue, 17 Feb 2015

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

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

Re: [Pharo-dev] how to unclose an issue?

Never mind. I found the Reopen button from the top right. Doru On Tue, Feb 17, 2015 at 9:15 AM, Tudor Girba wrote: > Hi, > > I made a mistake, and I pressed the Resolve & Close button in FogBugz. Is > there a way to unclose it? > > Here is the issue: > https://pharo.fogbugz.com/f/cases/edit/149

[Pharo-dev] how to unclose an issue?

Hi, I made a mistake, and I pressed the Resolve & Close button in FogBugz. Is there a way to unclose it? Here is the issue: https://pharo.fogbugz.com/f/cases/edit/14949/ Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"