September 2013 - Pharo-dev - lists.pharo.org

Pharo (cog) Vm on Windows with 2GB virtual mem
by Oscar E. A. CallaÃº Oct. 4, 2013

Oct. 4, 2013

Hi Guys, I read in this thread http://forum.world.st/out-of-memory-cog-on-windows-td3465621.html that 512 mb limit can be avoided in windows, but a re-compilation is needed. I was wondering if the situation changed, and now we can pass a parameter. Otherwise, I would be interested if any of you has a pre-compiled vm with more mem. I need to run some experiments and I need 2GB (or 1.5 GB at least ) on a cog VM for Windows. Thanks in advance. Oscar

6 8

[ANN] Launching Pharo on Ubuntu
by Damien Cassou Oct. 2, 2013

Oct. 2, 2013

For Ubuntu users who are using my PPA (https://launchpad.net/~pharo/+archive/stable/) you can now launch Pharo from either the Ubuntu Dashboard or the terminal (just type 'pharo'). In both cases, you will see the Pharo Launcher from which you can create new images from templates on the web and launch existing images. http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher No need for manual download of zip files, unpacking, and directory management. The launcher does everything for you. Have fun -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

8 25

State of SVG importer
by Hilaire Fernandes Oct. 2, 2013

Oct. 2, 2013

Hello, What is the state of the SVG importer regarding the standard. Can it parse all the specification to be capable to import any kind ofg SVG graphics? Thanks Hilaire -- Dr. Geo http://drgeo.eu

4 27

Pharo Hangout Session scheduled to Wed 2/10
by Esteban Lorenzano Oct. 2, 2013

Oct. 2, 2013

Hi, So... according to the doodle poll, hangout session will be Wed 2/10. I was thinking on doing it from 12 UTC to 17 UTC, to allow people of the new continent to join... what do you think? Esteban

4 4

XMLParser & PharoExtras, XMLWriter, XPath: status?
by phil＠highoctane.be Oct. 1, 2013

Oct. 1, 2013

In the Pharo 20 image, I see that we do have XMLParser, XMLPullParser, XMLWriter and XPath listed in the configuration (new install with ZeroConf). I am also using Soup. That's because I am working on some OpenData and screen scraping work and wondered what was okay to use. Is Soup depending on these? (I have XMLReader and Writer in my image but don't know from where at the moment - but there are no tests, so only something like #Core was loaded. Also what is different between XMLParser and XMLPullParser? TIA Phil

3 9

Primitives lookupEntryIn:index: fails on mac with the latest vm
by Andrei Chis Oct. 1, 2013

Oct. 1, 2013

Hi, I was trying to merge a slice into the latest Pharo 3 image when I got a FileSystemError in MacStore(DiskStore)>>basicEntry:path:nodesDo:. This happens as 'Primitives lookupEntryIn:index:' returns #badDirectoryPath. The bad part is that it goes into an infinite loop and blocks the image. The same scenario works ok with the stable pharo vm. I can reproduce this by going to the PharoInbox choosing a package that is not merged (let's say NativeBoost-Win32-CamilloBruni.42) and hit merge. If no error appears the first time, close the merge window and select merge again. For almost all packages, after a few time I get the previous error. Has anyone encountered this before? Might it be related to https://pharo.fogbugz.com/f/cases/7559 ? Cheers, Andrei

4 7

Weird issue with removing instance vars from class def: instance vars jumbled
by phil＠highoctane.be Oct. 1, 2013

Oct. 1, 2013

I guess this has happened to other people. In Pharo 20 and while using Seaside, I was adding, removing , changing components which were making a component and it happened that if I had, let say: a b c d e f turned into a c f Well, c kind of pointed to a b in existing instances and f to old c etc; No matter how much I unregister and reregisted my app, this continued. I got out of the problem by filing out the code and filing it in back, which recomplied the whole component. Weird. I can understand that some existing bytecode wasn't updated when rearranging instvars but for someone new to the game, this would really be weird. Clues? Phil

4 8

unexpected lack of Method Version History (due to CI process?)
by btc＠openinworld.com Oct. 1, 2013

Oct. 1, 2013

In the process of reviewing a fix to an issue [1] that I reported with PharoLauncher, I downloaded the latest CI result and browsed to the method I knew had changed [2]. I wanted to directly observe the change in the version history, but was surprised that there was no version history for the method. My uninformed intuition is this relates to some 'clean up for release' run as part of the build process to strip out old versions to compact the image delivered by the CI process, but does it make sense to do this for every build? I can understand not wanting this to grow indefinitely to bloat the image - but perhaps this compaction would be better only for major releases? I guess the downside is that you are then not exercising the 'full release' process every build. However having in image Version History extending a fair way back in time has always seemed to me to be one of the very cool (i.e. useful features of Pharo/Smalltalk). Without this, it feels like 'something' has been lost. The ultimate solution would seem to be linking the method version history to a network resource for the full history only as required per method. Any chance anyone is working on something like that? cheers -ben [1] https://pharo.fogbugz.com/f/cases/11614 [2] PharoLauncher>>createImageFromTemplate

3 4

Re: [Pharo-dev] failing moose tests
by Stephan Eggermont Sept. 30, 2013

Sept. 30, 2013

There has been a fixed package on smalltalkhub since 10 days, so it looks like a configuration problem Name: Moose-Test-HismoImporter-StephanEggermont.5 Author: StephanEggermont Time: 20 September 2013, 2:45:53.012 pm UUID: 766c5b47-daa6-4b51-af8f-091539186c59 Ancestors: Moose-Test-HismoImporter-AndreHora.4 Fixed some tests

1 0

Re: [Pharo-dev] failing moose tests
by Stephan Eggermont Sept. 30, 2013

Sept. 30, 2013

>>> Moose.Test.HismoImporter.MooseHismoImporterTest.testEvery15Days 64 ms 3 >>> Moose.Test.HismoImporter.MooseHismoImporterTest.testEvery2Years 52 ms 3 >>> Moose.Test.HismoImporter.MooseHismoImporterTest.testEvery6Months 51 ms 3 Don't know where they come from. The implementation should be using everyNDays/Months/Years AFAIK Stephan

1 0