- Pharo-dev - lists.pharo.org

[Pharo-project] FW: Issue 2476 in pharo: ConnectionQueue broken in 1.0 and 1.1 beta
by Schwab,Wilhelm K June 13, 2010

June 13, 2010

Marcus, I somewhat understand the logic of "if we didn't find it before this, it's not a problem now" but that attitude quickly leads to a trap. Part of why I did not find this sooner is that I have been struggling to adapt to metacello. I am not convinced that there is much information on how to use it, but there is certainly a lot of mis-information. The end result is a big hurdle to adopting new images. You are already producing 1.2. The core is at 1.1 RC - that's great! But here in the trenches, there is nothing approximating a dev image beta, and I can't figure out how to build it. Then I need a Seaside-enabled image on top of that. There is very little of value I can do with a release until Seaside is present. There is a growing tsunami of source code that I have to get into an image in order to be able to work. I built that process initially in terms of the web image; they are gone so I built it in terms of the dev image; now I can't even get that. Some stability (tenacity might be a better word) in the production of what is delivered to the user/developer would help me be a more aggressive tester. As it is, I am hacking the build process rather than applying it to reach a point that I can contribute to testing. In the extreme case, I could retreat to use Seaside's pre-made images and ignore the bleeding edge of Pharo, but that is not something I care to do. At a minimum, the unstable download section should contain a link to an "official" page that shows how to build the dev and web configurations. If we can't do that, work on 1.2 is premature. Back to 2476, it is quite possible that rydier's suggestion of removing the true return value will allow it to work. We are testing a new release, or should be. Does that not seem like a good time to introduce such a simple fix? Bill ________________________________________ From: pharo(a)googlecode.com [pharo(a)googlecode.com] Sent: Saturday, June 12, 2010 3:01 AM To: Schwab,Wilhelm K Subject: Re: Issue 2476 in pharo: ConnectionQueue broken in 1.0 and 1.1 beta Updates: Labels: -Milestone-1.1 Comment #6 on issue 2476 by marcus.denker: ConnectionQueue broken in 1.0 and 1.1 beta http://code.google.com/p/pharo/issues/detail?id=2476 In Pharo-dev 1.0 and 1.1 beta: not a show stopper for 1.1 -- You received this message because you are the owner of the issue. You may adjust your issue notification preferences at: https://code.google.com/hosting/settings

4 9

[Pharo-project] [SIXX] feedback
by Schwab,Wilhelm K June 13, 2010

June 13, 2010

Masashi, I have been trying to do some testing of Pharo 1.1 through a Seaside 3.0 daily image. One of the first things I load is SIXX. Pharo has been addressing underscore assignment problems, and the default is now to treat them as syntax errors, and one was identified in SixxAutoMorphMemento class>>release. I have also noted them in the #instDict and #instDict: accessors. It would be helpful if you could change the underscores to := for future releases. I am not sure how to tell if there are other underscore assignments in the .sar. Thanks for SIXX! Bill

2 1

[Pharo-project] Object>>changed:with: no longer in PharoCore-1.1-11383
by Yanni Chiu June 13, 2010

June 13, 2010

Object>>changed:with: is gone, but strangely, #update:with: is still present. The method is needed for the current Glorp package to run properly (just the logging, nothing critical). Can it be added back?

2 6

[Pharo-project] could not find module vm-display-X11
by spiralofhope June 13, 2010

June 13, 2010

Reading here: http://www.pharo-project.org/pharo-download It says this file "contains all necessary files", so I downloaded it: http://gforge.inria.fr/frs/download.php/26828/Pharo-1.0-OneClick.zip It says "run the executable". I don't know what executable it's referring to, so I'm trying Pharo.sh When I do, I get: could not find module vm-display-X11 I've done general searches as well as searches through the Pharo forum and mailing lists. I haven't seen anyone else with this problem, so I'm still not sure what to do and I need help. I'm running Linux i686.. it's only a release candidate distro (Unity Linux), so I wouldn't be surprised to learn that there are distro/library issues. I can give additional system information if you need. The website doesn't mention any dependencies, but could I be missing some? --- Reading here: http://www.pharo-project.org/pharo-download I see a section for "Custom downloads". The instructions say: To run Pharo you need an image, changes, and a sources file, as well as a VM for your platform. When downloads are completed, uncompress all files and put them into the same directory (this directory should then contain a .image, .changes, and a .sources file). Then start the VM. I downloaded these files: Image and Changes: http://gforge.inria.fr/frs/download.php/26790/Pharo-1.0.zip Sources: https://gforge.inria.fr/frs/download.php/24391/PharoV10.sources.zip Virtual Machine: http://gforge.inria.fr/frs/download.php/24736/pharo-vm-0.15.2f-linux.zip I unzipped them all into the same directory. Pharo-1.0.zip already had a PharoV10.sources within it, so I used the one from PharoV10.sources.zip I see these files in the same directory: Pharo-1.0.image Pharo-1.0.changes PharoV10.sources I don't know what to do now, there are no instructions for running Pharo after those steps. --- I've done a lot of playing outside of the above steps, but I'm completely ignorant of how Pharo is installed (or compiled?) and run. So far it's nothing like the other software I've used. Any advice is appreciated. I'm also willing to try a LiveCD of any Linux/BSD distro if that'll help me get Pharo working more easily. My goal here is just to check Pharo out, so I could deal with using another distro temporarily. -- http://spiralofhope.com

3 4

[Pharo-project] [update 1.2] #12007
by StÃ©phane Ducasse June 12, 2010

June 12, 2010

12007 ----- - Issue 2290: new windows (e.g. workspaces) appear wherever they feel like - SystemChangeNotifier-Tests from 3.9. - Issue 2381: We should probably remove slideToTrash

1 0

[Pharo-project] PointerFinder & PointerExplorer
by Johan Brichau June 12, 2010

June 12, 2010

Issue #156 (http://code.google.com/p/pharo/issues/detail?id=156) states that PointerFinder and PointerExplorer both have issues leaving out some pointers. Andy and I have been looking at the implementation of PointerFinder and PointerExplorer in Pharo1.1 to fix this. We came to the decision to throw out PointerFinder, replace its uses to uses of PointerExplorer and move PointerFinder's #pointersTo* class methods to ProtoObject because: - PointerFinder's (instance) behavior seems to be really old code that was not using the pointsTo: (primitive) method, while its #pointersTo* class methods were using the pointsTo: (primitive) method - It also seems the instance behavior of PointerFinder was wrong (it did not give us all pointers *at all*) - PointerExplorer offers the same functionality using a tree view and eventually used the #pointersTo* class methods of PointerFinder... The fix is in SLICE-PointerFinderRemove-AndyKellens.1 and should be for 1.2 Maybe anyone has another opinion? ---------------------------- Johan Brichau johan.brichau(a)uclouvain.be

3 5

[Pharo-project] [update 1.2] #12006
by StÃ©phane Ducasse June 12, 2010

June 12, 2010

12006 ----- - Issue 1795: look for squeak everywhere. Thanks Veronica Stef

1 0

[Pharo-project] [update 1.2] #12005
by Marcus Denker June 12, 2010

June 12, 2010

12005 ----- Redo the changes of 11400: Issue 2548: NewTestMorphTests>>#testAcceptContents fails Issue 2547: FilesStreamTest>>testPositionPastEndIsAtEnd Issue 2506: Browsing hierarchy of Traits crashes OB -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 3

June 12, 2010

12004 ----- - ScriptLoaderTest fixes - Issue 2487: Morph cleaning - Issue 2455: testIsAllDigits Stef

1 0

Re: [Pharo-project] OB Debugger
by Lukas Renggli June 12, 2010

June 12, 2010

Hi Johan, > We found you have implementation of an OB-Debugger in your omnibrowser repo. Yes, in the package OB-Tools there are functional implementations of debugger, filesystem browser, object browser (inspector), process browser, workspace, and transcript. > Could you comment to us what is the state of that code? I haven't looked into the code lately, so it might be slightly out of sync with the current OmniBrowser code. The code was functional and provided about 90% of the functionality the original Smalltalk-80 tools provided. At the time the tools were built they were notably slower than the original tools. I doubt that that this is still a big problem, because the meta-model has seen various major optimizations. The worst thing about the code is that there are no tests. There is no excuse for that. This is plain bad. > Is there a newer version? Not that I know. Dale from GemStone had been working on the tools for a while, but I think all his changes are in my repository. > Does it makes sense for us to pick up the project and see what we can do with it? I think that would be beneficial. Imagine we could extend our debuggers and inspectors the same way as the browsers. Lukas -- Lukas Renggli www.lukas-renggli.ch

1 0