My new 1.4 image is behaving a *little* better than its predecessors, but there is still a problem. It seems to happen after invoking Metacello loads, even with the mirror. Odd behaviors include: (1) can't open debugger (2) can't open process browser (3) intermittent flashing/alternating cursors in text editors. Whatever happens, it seems to be saved into the image as MC works, because killing the image and reloading results in a hobbled system. At least with 1.4, I can sometimes break into a debugger, presumably because something is busy in a tight loop. That might be a/the parser?? BTW, in an hour (max) of playing around, I've generated a 38 MB debug log - too big to read :( There are mentions of a parser, but my grep creativity has not allowed me to pull out any useful information. Perhaps I can start over with a clean log, let it get into some trouble, and review the log at a smaller size. Suggestions? Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Schwab,Wilhelm K [bschwab@anest.ufl.edu] Sent: Thursday, February 09, 2012 3:15 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 - better from Jenkins One snag: I'm still getting strangely broken images (won't open process browser or debugger) after trying to download some things. I have mirrored squeak source, BUT, some things (SIXX, ODBC) don't appear to have working configs, so I'm trying to grab the latest packages, and *that* might not be mirrored. I might need to specify the mirror server in my code to make them work. Still, I don't get how simply asking MC to download something will permanently mar the image w/o my doing an explicit save. Does MC snapshot before/during an attempted load? It seems very misguided that an innocent attempt to load something can hobble an image?? One other crazy possibility: is killing a vm from the (Ubunutu) system monitor somehow not sufficient to clear what is running? Dumb question? Maybe, but I'm stumped. Any ideas? Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of blake [dsblakewatson@gmail.com] Sent: Thursday, February 09, 2012 2:58 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 - better from Jenkins I just downloaded the latest CogWin and Pharo 1.4 image and I got "WARNING: Manufactured file handle detected!" at the bottom, and popup full of startup errors. But! It's all actually very friendly! I can look through the errors and try to figure out what caused them. It's way cleaner than the old style mega-DNU-stacks. Nice work! On Thu, Feb 9, 2012 at 11:06 AM, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
I grabbed 1.4 and cog/unix from jenkins, dumped all the files in one directory, made a shell script to run the image using Cog, and all I can say is "wow."
The usability problems I was having are gone. In particular, the context menus work. I loaded Migrate and set preferences, with a really nice appearance resulting.
One question: why did ClassDescription>>package go away? That seems to be a really useful message.
I'll try to build an image using the SqueakSource mirror. No promises, but 1.4 "suddenly" looks a LOT more polished than it did. Are the links on the Pharo page old, or did somebody just do a lot of work to make things better?
Bill