Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 5197e7db16456cc7681952e72a34bcafc81d4fa7
https://github.com/pharo-project/pharo-core/commit/5197e7db16456cc7681952e72a34bcafc81d4fa7
Author: Jenkins Build Server
Date: 2014-07-19 (Sat, 19 Jul 2014
Branch: refs/tags/40101
Home: https://github.com/pharo-project/pharo-core
> I did not check but I imagine you can commit now to the repo?
I didn't try yet. I'm currently rolling my changes into the "official"
Packages and doing some cleanup work (e.g. Tests their own package,
Configuration updates).
CU,
Udo
On 18.07.2014 13:45, stepharo wrote:
Excellent!
We love
I want to find out in case of MNU what the wrong message is , its exact
name ?
You can also answer here
http://stackoverflow.com/questions/24831610/how-to-find-which-was-the-wrong-message-in-a-message-not-understood-message
Apparently I cannot remove the trait TAbleToRotate from a class
If
- I copy SimpleButtonMorph
- remove the use: clause from the class def
- I cannot commit the package anymore.
there is a problem in packageSet
Esteban do you copy me :)
Stef
On 07/18/2014 07:37 AM, stepharo wrote:
> Hi martin
>
> in Moose (working on 3.0) all the tools are working so I do not know the
> status of the published configuration but it should work.
> Have a look at Moose and the configuration repo from there.
Thanks, Stef (and Phil). I'll try loading from
Well,
I fixed the problem by modifying the Pharo.exe file with the 4GB patch
program (http://ntcore.com/4gb_patch.php).
As mentioned before, I think the best solution is that Pharo vms must be
compiled with the flag LARGEADDRESSAWARE, so more memory space is
enabled for 64bits Windows OSs.
Tha
Hi martin
in Moose (working on 3.0) all the tools are working so I do not know the
status of the published configuration but it should work.
Have a look at Moose and the configuration repo from there.
Stef
On 18/7/14 04:15, Martin McClure wrote:
On 07/17/2014 04:37 PM, Sean P. DeNigris wrote
Thanks pavel.
We should continue to repackage and clean.
Tools for example.
I'm currently working on Polymorph.
Stef
Great, now the shrinking to the basic image does not have any
overrides nor ugly hacks.
https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-1.0-Shrink/
--
Hi Esteban,
Moose 5 is still under development. We will likely reach a stable version
within one or two months. In the meantime, it is true that there are some
subcomponents that are stable (such as PetitParser), but we do not have yet
the capacity and the organization to be able to release it ind
Hi guys,
I just published the interview of Clara Allende here:
http://nicolas-petton.fr/blog/interview-clara.html
As this is my last day in the team, I won't have time to interview any
other member of the team (with the exception of Camille, as the
interview is done, I just have to publish it). I
On 18 Jul 2014, at 14:12, Stephan Eggermont wrote:
> Esteban wrote
>> This is a question for the moosers :)
>> Why there is no copy (with stable version) in metarepo of ll configurations
>> that are under the moose umbrella?
>
> That's a question of effort vs results. Moose builds on top of Ph
Hi,
I need to manipulate classes/methods in my tests. E.g. create class, test
something, remove it. Can I do this silently? Because otherwise I get dirty
packages, Epicea log and so on.
Cheers
Uko
Esteban wrote
>This is a question for the moosers :)
>Why there is no copy (with stable version) in metarepo of ll configurations
>that are under the moose umbrella?
That's a question of effort vs results. Moose builds on top of Pharo, which has
no stable.
There are newer builds of Pharo 3 conta
Super!
I should migrate and revisit also some of my chapters.
Stef
On 17/7/14 22:01, Stephan Eggermont wrote:
Thanks to some help by Damien, we now have FunWithPharo
on ci. It generates the whole book and separate chapters.
Stephan
I started Fun With Pharo :)
https://github.com/SquareBracketAssociates/FunWithPharo
Good. I've added the chapter. Can I just copy the ci config from
PharoForTheEnterprise to generate book & chapters?
Anything else to do than change urls?
adding chapters I will have a look now. I thought t
Excellent!
We loved such enhancements.
I did not check but I imagine you can commit now to the repo?
Stef
On 17/7/14 12:08, Udo Schneider wrote:
> What are the changes ?
SSL:
* Addition of LDAPSConnection/LDAPSWorker and instance generation
methods (e.g. LDAPSConnection>>#to:port:ssl:) to use
Damien
what is this looking bad selector?
#wordingProvider:wordingSelector: and who is invoking it?
because we should simply use a default menu.
Stef
On 18/7/14 13:24, Damien Cassou wrote:
On Thu, Jul 17, 2014 at 8:49 PM, Paul DeBruicker wrote:
http://www.samadhiweb.com/blog/2014.05.01.rf
On Thu, Jul 17, 2014 at 8:49 PM, Paul DeBruicker wrote:
> http://www.samadhiweb.com/blog/2014.05.01.rfb.pharo3.html
thank you very much, I pushed the fix to the RFB repository
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another with
Because nobody did it.
Doru
On Fri, Jul 18, 2014 at 12:04 PM, Esteban Lorenzano
wrote:
> Hi,
>
> This is a question for the moosers :)
> Why there is no copy (with stable version) in metarepo of ll
> configurations that are under the moose umbrella?
>
> cheers,
> Esteban
>
> On 18 Jul 2014, at
Hi,
This is a question for the moosers :)
Why there is no copy (with stable version) in metarepo of ll configurations
that are under the moose umbrella?
cheers,
Esteban
On 18 Jul 2014, at 10:00, p...@highoctane.be wrote:
> I load it from the moose team on sth. Works for me, browser included.
Thank you!
On 18 Jul 2014, at 11:01, Marcus Denker wrote:
>>>
>>> I added tests in 099 to check that all binding are correct in Smalltalk
>>> globals and all classPools.
>>>
>>> It seems that someone is adding global somehow with the wrong class
>>> (Association instead of
>>> GlobalVar (a s
Branch: refs/tags/40100
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: fd7e82f07cfab0301e2c96e4761ffd4f271cd48d
https://github.com/pharo-project/pharo-core/commit/fd7e82f07cfab0301e2c96e4761ffd4f271cd48d
Author: Jenkins Build Server
Date: 2014-07-18 (Fri, 18 Jul 2014
>> I added tests in 099 to check that all binding are correct in Smalltalk
>> globals and all classPools.
>>
>> It seems that someone is adding global somehow with the wrong class
>> (Association instead of
>> GlobalVar (a subclass of Association).
>>
>> But #at:put: should do the right thing
On 18 Jul 2014, at 10:38, Marcus Denker wrote:
>
> On 18 Jul 2014, at 10:26, Marcus Denker wrote:
>
>>
>> On 18 Jul 2014, at 10:20, Marcus Denker wrote:
>>
>>>
>>> On 18 Jul 2014, at 10:16, Yuriy Tymchuk wrote:
>>>
Hi,
when my image tries to run startup scripts I get:
>>
Great, now the shrinking to the basic image does not have any overrides nor
ugly hacks.
https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-1.0-Shrink/
-- Pavel
2014-07-18 10:32 GMT+02:00 GitHub :
> Branch: refs/heads/4.0
> Home: https://github.com/pharo-project/phar
On 18 Jul 2014, at 10:26, Marcus Denker wrote:
>
> On 18 Jul 2014, at 10:20, Marcus Denker wrote:
>
>>
>> On 18 Jul 2014, at 10:16, Yuriy Tymchuk wrote:
>>
>>> Hi,
>>>
>>> when my image tries to run startup scripts I get:
>>>
>>> Association(Object)>>doesNotUnderstand: #emitValue:
>>>
>
Branch: refs/tags/40099
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 9ebdd640712f23c1c3055d066972c2034e3ca45e
https://github.com/pharo-project/pharo-core/commit/9ebdd640712f23c1c3055d066972c2034e3ca45e
Author: Jenkins Build Server
Date: 2014-07-18 (Fri, 18 Jul 2014
On 18 Jul 2014, at 10:20, Marcus Denker wrote:
>
> On 18 Jul 2014, at 10:16, Yuriy Tymchuk wrote:
>
>> Hi,
>>
>> when my image tries to run startup scripts I get:
>>
>> Association(Object)>>doesNotUnderstand: #emitValue:
>>
>> Should I report it?
>
>
> Yes. It should not happen.
>
> But
Pharo-4.0-Bootstrap-Step-2.0-ConfigurationOfSUnit job is failing because of
this issue too.
-- Pavel
2014-07-18 10:20 GMT+02:00 Marcus Denker :
>
> On 18 Jul 2014, at 10:16, Yuriy Tymchuk wrote:
>
> > Hi,
> >
> > when my image tries to run startup scripts I get:
> >
> > Association(Object)>>do
On 18 Jul 2014, at 10:16, Yuriy Tymchuk wrote:
> Hi,
>
> when my image tries to run startup scripts I get:
>
> Association(Object)>>doesNotUnderstand: #emitValue:
>
> Should I report it?
Yes. It should not happen.
But startup script are very strange as they somehow hold onto compiled code.
Thanks!
On 18.07.2014, at 10:12, Marcus Denker wrote:
>
> On 18 Jul 2014, at 10:04, Max Leske wrote:
>
>> I’m getting a 503 when trying to access pharo-contribution CI. It was
>> working until half an hour ago. Could someone take a look please?
>>
>> Cheers,
>> Max
>
> I have restarting it
Hi,
when my image tries to run startup scripts I get:
Association(Object)>>doesNotUnderstand: #emitValue:
Should I report it?
Uko
P.S. here is stack:
Association(Object)>>doesNotUnderstand: #emitValue:
OCLiteralVariable>>emitValue:
OCASTTranslatorForValue(OCASTTranslator)>>visitVariableNode:
R
On 18 Jul 2014, at 10:04, Max Leske wrote:
> I’m getting a 503 when trying to access pharo-contribution CI. It was working
> until half an hour ago. Could someone take a look please?
>
> Cheers,
> Max
I have restarting it...
Branch: refs/tags/40098
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: 37babd48dab4fa113e269d4d63e8ecf70f0c0e3c
https://github.com/pharo-project/pharo-core/commit/37babd48dab4fa113e269d4d63e8ecf70f0c0e3c
Author: Jenkins Build Server
Date: 2014-07-18 (Fri, 18 Jul 2014
subj
I’m getting a 503 when trying to access pharo-contribution CI. It was working
until half an hour ago. Could someone take a look please?
Cheers,
Max
I load it from the moose team on sth. Works for me, browser included.
Le 18 juil. 2014 09:24, "Tudor Girba" a écrit :
> In the case of Moose, #development and #bleedingEdge are the same.
>
> Doru
>
>
> On Fri, Jul 18, 2014 at 9:18 AM, Norbert Hartl wrote:
>
>> I think what is loaded by CI is dep
On 18 Jul 2014, at 08:14, Marcus Denker wrote:
>>>
>>> I have added a first GlobalVar hierarchy… it has already the code
>>> generation methods but Opal is not yet forwarding
>>> code generation (and the compiler does not yet compile bindings with the
>>> subclass).
>>>
>>
>> update 40 095
Branch: refs/tags/40097
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/4.0
Home: https://github.com/pharo-project/pharo-core
Commit: a31a276f780b15bfbd294c214a9f317ebb7ad35a
https://github.com/pharo-project/pharo-core/commit/a31a276f780b15bfbd294c214a9f317ebb7ad35a
Author: Jenkins Build Server
Date: 2014-07-18 (Fri, 18 Jul 2014
In the case of Moose, #development and #bleedingEdge are the same.
Doru
On Fri, Jul 18, 2014 at 9:18 AM, Norbert Hartl wrote:
> I think what is loaded by CI is dependent on the workflow of the project.
> IMHO for most projects loading #bleedingEdge is the best thing to do.
>
> Norbert
>
> Am 1
I think what is loaded by CI is dependent on the workflow of the project. IMHO
for most projects loading #bleedingEdge is the best thing to do.
Norbert
> Am 18.07.2014 um 05:21 schrieb Tudor Girba :
>
> It loads #development as any CI job should do.
>
> Doru
>
>
>> On Fri, Jul 18, 2014 at 1:
46 matches
Mail list logo
