-- Forwarded message --
From: Nicolas Cellier
Date: 2013/8/8
Subject: SmalltalkHub down
To: Pharo Development
http://smalltalkhub.com/ -> 502 Proxy Error
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 wrote:
> I think that's not true at all.
>
> Our git rep
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
>>
>>
>
> 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
On 7 August 2013 19:06, Stéphane Ducasse wrote:
>
> On Aug 7, 2013, at 6:34 PM, Igor Stasenko wrote:
>
>> On 7 August 2013 17:56, Guillermo Polito wrote:
>>> https://pharo.fogbugz.com/default.asp?pre=preSaveFilterProject&ixProject=6
>>>
>>> They are under the Pharo-VM project.
>>>
>>> That way w
On Aug 7, 2013, at 5:59 PM, "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)
Thanks,
Esteban
On Aug 7, 2013, at 6:34 PM, Igor Stasenko wrote:
> On 7 August 2013 17:56, Guillermo Polito wrote:
>> https://pharo.fogbugz.com/default.asp?pre=preSaveFilterProject&ixProject=6
>>
>> They are under the Pharo-VM project.
>>
>> That way we can handle them easily.
>>
>
> I don't like this move
On 7 August 2013 17:56, Guillermo Polito wrote:
> https://pharo.fogbugz.com/default.asp?pre=preSaveFilterProject&ixProject=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 would help fixing th
now can we get a working keyboard?
On Wednesday, August 7, 2013, Igor Stasenko 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 start pushing cha
https://pharo.fogbugz.com/default.asp?pre=preSaveFilterProject&ixProject=6
They are under the Pharo-VM project.
That way we can handle them easily.
Guille
Agree with everything you said.
As i said, my impression was that Guille pushed unfinished/incomplete pieces.
And that is what i against.
Because if we go that way, then someone will start pushing changes
which even don't compile.
I hope i made my point clear, what blessed means. It is not synony
me too.
On 7 August 2013 13:23, Stéphane Ducasse wrote:
> thanks I will try it now.
>
> Stef
> On Aug 7, 2013, at 1:11 PM, Esteban Lorenzano 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/phar
IMO is no point on ask for keeping an "all-time-stable" VM in the development
process (it is even a contradiction).
Is the same as asking for a 3.0 stable before release (yes, is the same... we
are trying to have same process for both).
VM development is not stable right now, same way it is no
On 7 August 2013 15:55, Guillermo Polito wrote:
>
> On Wed, Aug 7, 2013 at 2:41 PM, Igor Stasenko 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
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 si
On Wed, Aug 7, 2013 at 2:41 PM, Igor Stasenko 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 there.
> - once
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 o
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 there.
- once you finished with changes and tested it , you are free to merge
wit
I agree, except that as far as i know there is no platform-specific tests yet.
On 7 August 2013 09:49, Torsten Bergmann wrote:
> Hi Igor,
>
> NB includes OS specific classes and examples that will/may require OS
> specific tests.
>
> IMHO it would make sense to change "NativeBoost-Tests" categor
On 7 August 2013 10:03, Alexandre Bergel wrote:
> Hi Igor,
>
> I think have I found a bug when circle are drawn.
>
> I have added "(start = end) ifTrue: [ ^ self ]." in this method:
>
your change just makes it fool-proof.
The bug is in user code which specifies wrong data (drawing arc with
two co
thanks I will try it now.
Stef
On Aug 7, 2013, at 1:11 PM, Esteban Lorenzano 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)
>
> Thanks,
> Esteb
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
Tx, I did the same
except that when I want to integrate the package and I reload it I get this
error.
Now hypothesis one:
- may be this is the verify logic that is not good, because I reload
all the packages without order so
may be we are in the case where a package is loaded before ano
2013/8/5 Francisco Garau
> I'd prefer #when:do: rather than #onAnnouncement:do:
>
> Yes. And it was original API from VisualWorks. And maybe it stay in VW now
> - Francisco
>
> On 5 Aug 2013, at 18:01, Stéphane Ducasse
> wrote:
>
>
> On Aug 5, 2013, at 4:18 PM, Nicolas Cellier <
> nicolas.cell
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.
On Aug 7, 2013, at 8:55 , Stéphane Ducasse wrote:
>
> On Aug 6, 2013, at 4:47 PM, Stéphane Ducasse
> 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: ?
Its use is to sp
At least the issue 11315 it was integrated :)
2013/8/7 Stéphane Ducasse
> 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 proba
Hi Igor,
NB includes OS specific classes and examples that will/may require OS specific
tests.
IMHO it would make sense to change "NativeBoost-Tests" category into
- "NativeBoost-Tests-Core"
- "NativeBoost-Tests-Mac"
- "NativeBoost-Tests-Unix"
- "NativeBoost-Tests-Win32"
while still keepi
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
htt
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/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=linux-stable-worker/409/
1 regressions found.
KernelTests.Numbers.LargePositiveIntegerTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses
32 matches
Mail list logo
