Adrian
apparently when I load OB on 10202 and I update it crashes the image.
Stef
On Jan 7, 2009, at 7:06 PM, Adrian Lienhard wrote:
> - Issue 363: fix some traits issues (introduced by changes in
> Metaclass and TestCase)
> - Traits conflict marker methods stored in wrong cache
> - Remove dupl
apparently this could be linked with the faster fasterDayOfYear-brp.1
(Mantis 7156)?
Thanks for reporting
stef
Begin forwarded message:
From: "Rob Rothwell"
Date: January 8, 2009 3:01:07 AM CEST
To: "Stéphane Ducasse"
Subject: Re: [Pharo-project] [ANN] 10203
Reply-To: rj...@sbcglobal.net
2009/1/8 Igor Stasenko :
> by coincidence, i'm currently also working on GLASS, but still using
> old squeak image. :)
> Any success installing gemtools into pharo to use improved OB-based look&feel?
I am interested on that as well
Hilaire
___
Pharo-p
Steph...sorry for the double reply...I missed the list...
Ok...I went back to pharo0.1-10185dev08.12.1 and re-tried
pharo0.1-10196dev08.12.3 again, and they both die the same terrible death
when loading this update.
I think it is shortly after a "recompiling" stage, then it hits a "Loading"
stage
2009/1/7 Torsten Bergmann :
> see http://mue.tideland.biz/2009/01/great-job-guys.html
> --
Since this is alredy OT ...
by coincidence, i'm currently also working on GLASS, but still using
old squeak image. :)
Any success installing gemtools into pharo to use improved OB-based look&feel?
> Pt!
This is a very positive post.
Thanks for sharing with us
Alexandre
On 7 Jan 2009, at 18:24, Torsten Bergmann wrote:
> see http://mue.tideland.biz/2009/01/great-job-guys.html
> --
> Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit
> allen: http://www.gmx.net/de/go/multimessen
Maybe the problem is gone with the fixes I pushed in the 10203 update
as I can't reproduce the problem. What I did is take a fresh core
10203 image, ScriptLoader loadOB, open OB package browser, create a
trait with a method, create a class that uses that trait, remove trait
from class, and
cool
thanks for the pointer.
we hope also to have Pharo by Example in the future
and especially Pharo by Example volume 2 :)
Stef
On Jan 7, 2009, at 10:24 PM, Torsten Bergmann wrote:
> see http://mue.tideland.biz/2009/01/great-job-guys.html
> --
> Pt! Schon vom neuen GMX MultiMessenger geh
see http://mue.tideland.biz/2009/01/great-job-guys.html
--
Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen:
http://www.gmx.net/de/go/multimessenger
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.
yes when I use OB-package browser.
Quite annoying.
Stef
On Jan 7, 2009, at 9:05 PM, Adrian Lienhard wrote:
> Very odd. I've never seen this.
> Does it happen in a Pharo-core image?
>
> Adrian
>
> On Jan 7, 2009, at 19:18 , Stéphane Ducasse wrote:
>
>> When I define a class with a trait and remov
hi rob
I got not problem with the core image.
Stef
On Jan 7, 2009, at 8:43 PM, Rob Rothwell wrote:
> Has anyone successfully loaded this from the System Update... menu
> item?
>
> Whether starting from my own image, or a fresh dev08.12.3 image, it
> eventully goes into debug mode at the bot
Very odd. I've never seen this.
Does it happen in a Pharo-core image?
Adrian
On Jan 7, 2009, at 19:18 , Stéphane Ducasse wrote:
> When I define a class with a trait and remove it after I get all the
> trait methods
> locally defined with a self halt.
> Does anybody know from where such a behavio
Has anyone successfully loaded this from the System Update... menu item?
Whether starting from my own image, or a fresh dev08.12.3 image, it
eventully goes into debug mode at the bottom of the screen, and if left on
it's own, eventually just shuts down...
Rob
On Wed, Jan 7, 2009 at 1:06 PM, Adri
When I define a class with a trait and remove it after I get all the
trait methods
locally defined with a self halt.
Does anybody know from where such a behavior could come from?
Stef
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
thanks
On Jan 7, 2009, at 7:06 PM, Adrian Lienhard wrote:
> - Issue 363: fix some traits issues (introduced by changes in
> Metaclass and TestCase)
> - Traits conflict marker methods stored in wrong cache
> - Remove duplicated method in trait and class that uses it (in
> collection tests)
> - Iss
- Issue 363: fix some traits issues (introduced by changes in
Metaclass and TestCase)
- Traits conflict marker methods stored in wrong cache
- Remove duplicated method in trait and class that uses it (in
collection tests)
- Issue 315: darker colors in diff dialog (thanks to Damien Pollet)
- Iss
On Jan 5, 2009, at 7:56 AM, Lukas Renggli wrote:
>> I published to the inbox some cool collection extension methods that
>> we use all the time in Moose.
>> flatCollect:, collectAsSet:, and groupedBy:
>
> I think Squeak already has far too many of these methods. I would
> rather like to see them
The setting to diff in the PharoInbox repository first appears in the
uploaded image Pharo0.1Core-10172.zip
Thanks, Alex, for tracking this down.
I've never used this feature.
Adrian
On Jan 7, 2009, at 15:37 , Stéphane Ducasse wrote:
> Excellent
> I have no idea how pharoInbox got diffy
>
> S
Excellent
I have no idea how pharoInbox got diffy
Stef
> Dear List,
>
> I dug in the Monticello melting-pot to find where the strange behavior
> some of you are encountering comes from.
>
> **The problem**
> The bug come from the "diffy versions". MC tries to save in PharoInbox
> a "diffy" vers
Dear List,
I dug in the Monticello melting-pot to find where the strange behavior
some of you are encountering comes from.
**The problem**
The bug come from the "diffy versions". MC tries to save in PharoInbox
a "diffy" version of your package. As far as I understood, a "diffy"
version is a
Dear List,
A new version of CollectionsTests is waiting in PharoInbox. Here is
the comments:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
**This version includes the content of version 142**
The most important methods in Dictionary are covered by
DictionaryTest. Some implementation methods in Set are also
>>
> Is the plan for it to end up as a fork of squeak that runs on the
> squeak vm?
probably. what is the other solution?
> Is the underlying vm going to change?
Probably too. if we want to clean up event and other parts there is no
other
way. After our changes are MIT so
> __
22 matches
Mail list logo
