On Aug 6, 2013, at 4:47 PM, Stéphane Ducasse stephane.duca...@inria.fr wrote:
#when:do: is there already ;)
even better then :)
#when:send:to: and #when:do:for: should be added though.
what would be when:do:for: ?
sounds good.
Cheers,
Henry
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linux-stable-worker/409/
1 regressions found.
KernelTests.Numbers.LargePositiveIntegerTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/409/
1 regressions found.
KernelTests.Numbers.LargePositiveIntegerTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/409/
1 regressions found.
KernelTests.Numbers.LargePositiveIntegerTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses
30326
-
It probably works….but since the jenkins user interface is so bad I guess that
everything went well. May be we should have several PhD in CS
to understand Jenkins UI. I just have one PhD so I'm probably not qualified
enough.
- issue 11310 Browser newOnClass: is broken
At least the issue 11315 it was integrated :)
2013/8/7 Stéphane Ducasse stephane.duca...@inria.fr
30326
-
It probably works….but since the jenkins user interface is so bad I guess
that everything went well. May be we should have several PhD in CS
to understand Jenkins UI. I just have
Hi Stef,
#nbBindingOf: is an extension on Behavior from the NativeBoost Core package.
I tried and it works:
- using Pharo2.0 Latest update: #20603
- adding http://smalltalkhub.com/#!/~Pharo/NativeBoost
- loading latest version of Core, Examples, Pools, Mac, Unix, Win32, Tests
All NB tests pass.
Hi,
Guille built a new vm with an attept of fixing the key combinations problem.
Can you test it?
http://files.pharo.org/vm/pharo/
(and pick the latest for your platform)
Thanks,
Esteban
thanks I will try it now.
Stef
On Aug 7, 2013, at 1:11 PM, Esteban Lorenzano esteba...@gmail.com wrote:
Hi,
Guille built a new vm with an attept of fixing the key combinations problem.
Can you test it?
http://files.pharo.org/vm/pharo/
(and pick the latest for your platform)
Just to make it clear:
when you get zero-divide error, where you think the bug is , in #/ method,
or maybe in code which passed zero as divisor?
by analogy, when you want to draw an arc with zero length, which makes
it non-arc,
where you think the bug is, in code which implements drawing an arc
On Wed, Aug 7, 2013 at 2:41 PM, Igor Stasenko siguc...@gmail.com wrote:
My understanding how it should be:
- you work in own branch (and in git, repository clone is already a
branch, just on your computer).
If you want to make it public you need to make own branch on gitorious
and commit
Hi
1)
I'm working on an issue related to compact classes index and I discovered
that behaviours implement #becomeCompactSimplyAt:, which has this comment:
Make me compact, but don't update the instances. *For importing segments*
.
This made me think that it's no longer needed in the image
On 7 August 2013 15:55, Guillermo Polito guillermopol...@gmail.com wrote:
On Wed, Aug 7, 2013 at 2:41 PM, Igor Stasenko siguc...@gmail.com wrote:
My understanding how it should be:
- you work in own branch (and in git, repository clone is already a
branch, just on your computer).
If you
me too.
On 7 August 2013 13:23, Stéphane Ducasse stephane.duca...@inria.fr wrote:
thanks I will try it now.
Stef
On Aug 7, 2013, at 1:11 PM, Esteban Lorenzano esteba...@gmail.com wrote:
Hi,
Guille built a new vm with an attept of fixing the key combinations problem.
Can you test it?
now can we get a working keyboard?
On Wednesday, August 7, 2013, Igor Stasenko siguc...@gmail.com wrote:
Agree with everything you said.
As i said, my impression was that Guille pushed unfininowshed/incomplete
pieces.
And that is what i against.
Because if we go that way, then someone will
On 7 August 2013 17:56, Guillermo Polito guillermopol...@gmail.com wrote:
https://pharo.fogbugz.com/default.asp?pre=preSaveFilterProjectixProject=6
They are under the Pharo-VM project.
That way we can handle them easily.
I don't like this move.
If moving issues from one
tracker to another
On Aug 7, 2013, at 5:59 PM, p...@highoctane.be p...@highoctane.be wrote:
now can we get a working keyboard?
Yes here
Hi,
Guille built a new vm with an attept of fixing the key combinations problem.
Can you test it?
http://files.pharo.org/vm/pharo/
(and pick the latest for your platform)
On 7 August 2013 19:06, Stéphane Ducasse stephane.duca...@inria.fr wrote:
On Aug 7, 2013, at 6:34 PM, Igor Stasenko siguc...@gmail.com wrote:
On 7 August 2013 17:56, Guillermo Polito guillermopol...@gmail.com wrote:
https://pharo.fogbugz.com/default.asp?pre=preSaveFilterProjectixProject=6
That's exactly what i was thinking about when registered cog issue tracker.
And since Cog used not just by Pharo, it deserves own separate repository.
Now i would like to know, if somebody asked people who contributing to Cog
development but not to Pharo, if they would like to use
I think that's not true at all.
Our git repo and our vmmaker repo are used to build only the pharo vm
flavor. If we make a fix it does not get magically integrated into eliots
cog.
Maybe they can benefit from the changes but they have to merge back as you
esteban and igor merge in our branch.
Le
Well, my intent was to keep working together on it and be as open as possible to
people who may not work particularly on Pharo, but care/use Cog.
Now my dilemma is, what is the fate of Cog tracker?
On 7 August 2013 20:29, Guillermo Polito guillermopol...@gmail.com wrote:
I think that's not
21 matches
Mail list logo
