On 22.02.2009, at 09:59, David Finlayson wrote:
> I tried all the suggestions here (abandon the error and continue;
> download a one-click source and over write the files with the dev
> updates. In both cases, I wound up with an unstable image. I got
> further with the second method and used it for a couple of hours, but
> I am seeing a lot of errors. For example: errors are raised when I
> delete morphs (something to do with the trash can); an error searching
> in OB for the word "morph" raised an error in OBEnhancementMetaNode >>
> Fan ??
Ups. Normally the images are very usable... we need to look at how these
problems where introduced in the last ones.
>
>
> I know that you guys are ripping out a lot of cruft in Squeak and
> things are understandably unstable right now. You've made great
> progress on the UI, that's for sure. I'll come back again when you
> release the first stable build in a couple of months.
>
I hope it's weeks, not months...
Marcus
> Thanks for your work,
>
> David
>
> On Sat, Feb 21, 2009 at 7:44 PM, Rob Rothwell
> <[email protected]> wrote:
>> Is this reproducible then? (It is by me!) Should I report it as
>> an issue?
>>
>> Rob
>>
>> On Sat, Feb 21, 2009 at 9:03 PM, Schwab,Wilhelm K <[email protected]
>> >
>> wrote:
>>>
>>> I'm glad this came up, because I hit that one too and forgot about
>>> it.
>>> The other thing I have found is that more recent images are somewhat
>>> particular about the VM version - they will freeze if the (Windows
>>> is where
>>> I have seen it) vm is too old.
>>>
>>> Bill
>>>
>>> ----
>>> Wilhelm K. Schwab, Ph.D.
>>> bschwab AT anest DOT ufl DOT edu
>>>
>>> ________________________________________
>>> From: [email protected]
>>> [[email protected]] On Behalf Of Rob
>>> Rothwell
>>> [[email protected]]
>>> Sent: Saturday, February 21, 2009 2:15 PM
>>> To: [email protected]; [email protected]
>>> Subject: Re: [Pharo-project] Getting started
>>>
>>> I get that error with the new 10236 dev image as well; I don't
>>> recall
>>> getting it with the 10231 dev image. I think it is related to the
>>> initial
>>> FreeType startup process.
>>>
>>> Start with a 10236 image, click "abandon" and close the debug
>>> window, save
>>> the image, close it, and open it again. At least I don't get the
>>> error the
>>> next time.
>>>
>>> Rob
>>>
>>> On Sat, Feb 21, 2009 at 12:21 PM, David Finlayson
>>> <[email protected]<mailto:[email protected]>> wrote:
>>> What's the trick to getting a pharo image up and running?
>>>
>>> I tried downloading the pharo-dev image 20231 from the downloads
>>> page,
>>> then I added SqueakV39.sources from a Squeak image. When I
>>> launched I
>>> got an error dialog saying:
>>>
>>> Error: a primative has failed.
>>>
>>> I was hoping to take a look around at the work you folks are doing.
>>>
>>> --
>>> David Finlayson
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>>
>>> [email protected]<mailto:[email protected]
>>>
>>> >
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
>
> --
> David Finlayson, Ph.D.
> Operational Geologist
>
> U.S. Geological Survey
> Pacific Science Center
> 400 Natural Bridges Drive
> Santa Cruz, CA 95060, USA
>
> Office: 831-427-4757
> Lab: 831-427-4462
> Fax: 831-427-4748
> E-mail: [email protected]
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
Marcus Denker -- [email protected]
http://www.marcusdenker.de
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
