- Pharo-dev - lists.pharo.org

[Pharo-project] OSProcess and CommandShell in Pharo 2.0
by Sean P. DeNigris Feb. 13, 2013

Feb. 13, 2013

I think we have it now: - ConfigurationOfOSProcess and ConfigurationOfCommandShell have been updated to work in 1.4 and 2.0 - Each config has been copied to its project repo (e.g. sqs/CommandShell). I was starting to get confused with all the locations (sqs/MetacelloRepository, xyz/MetaRepoForAbc, etc). I think it's a more sane model to keep the configs with the project and then mirror them as necessary. Metacello was designed to manage dialect dependencies, so there should be no need to fork a ConfigurationOfXyz. The only issue we have is when we don't have access to the project's repo, for which it'd be great if we implement per-project inboxes ( maybe in StHub, hint, hint ;) ) Anyway, thanks to David and Steph for all the hard work getting this working. OSP and CommandShell are vitally important projects and it's great to know that they will continue working well in Pharo for the foreseeable future :) -- View this message in context: http://forum.world.st/OSProcess-and-CommandShell-in-Pharo-2-0-tp4669674.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

3 2

[Pharo-project] The monkey is back in town
by Camillo Bruni Feb. 13, 2013

Feb. 13, 2013

I had a sudden urge to program something so I revived the monkey (partly) - full smalltalk implementation (no more ruby) - basic command line handler (could be better but works..) - using OSProcess with FileSystem-Legacy in 2.0 the only thing missing are the couple of changes I proposed for the main image: - http://code.google.com/p/pharo/issues/detail?id=7097 - http://code.google.com/p/pharo/issues/detail?id=7096 - http://code.google.com/p/pharo/issues/detail?id=7095 once they are in, we're ready to roll cami on fernet

13 54

Re: [Pharo-project] Enums with negative values don't work properly.
by Igor Stasenko Feb. 13, 2013

Feb. 13, 2013

Good news: - i reverted the image-side code back in 2.1 version i don't like adding new primitives, and since i found the way to access required symbols on windows VM by exporting them, this will allow the old versions of NB to run without changes on newer VMs. In new VMs, there are also changes to primitive 220 (primitiveVoltage ;). It is mostly dormant NB feature right now, but it is important to have it working correctly for the future. Today we were doing last steps with Esteban, integrating all changes & fixing minor details.. now we are at stage of making things work on jenkins (can take couple more days, because we have to reinstall mac slave). -- Best regards, Igor Stasenko.

1 0

[Pharo-project] [update 2.0] #20543
by Marcus Denker Feb. 13, 2013

Feb. 13, 2013

20543 ----- Issue 7502: Failing test: DiskFileSystemTest>>#testDefaultWorkingDirectory http://code.google.com/p/pharo/issues/detail?id=7502 Diff information: http://ss3.gemstone.com/ss/Pharo20/FileSystem-Tests-Disk-MarcusDenker.13.di…

1 0

[Pharo-project] [ann] glamorous debugger (alpha)
by Tudor Girba Feb. 13, 2013

Feb. 13, 2013

Hi, Over the last following days, Andrei Chis and me have worked on getting the Glamorous Debugger in a usable state (based on the original effort of Toon Verwaest): This debugger is part of the Glamorous Toolkit project, and it is based on Glamour (see the attached screenshots). You can find some details about it here: http://www.humane-assessment.com/blog/announcing-the-glamorous-debugger-alp… Some interesting characteristics: - It has an integrated inspector that shows all variables in one GTInspector with which you can browse in place all relevant variables - Code-wise, the debugger comes with an explicit model that relies neither on the old Debugger nor on the CodeHolder. The model is rather small and intelligible. In total, the entire code totals some 400 lines of code (at the moment). To put it into perspective, the Debugger class has 1096 lines of code (not counting the extra code used by it). Right now, we consider the code to be in a solid alpha, and we need more eyeballs and clicks to test it :). If you are interested in playing with it, you can either find it in the Moose image, or you can load it in Pharo 1.4 via: Gofer new squeaksource: 'glamoroust'; package: 'ConfigurationOfGlamoroust'; load. (Smalltalk at: #ConfigurationOfGlamoroust) loadDevelopment Cheers, Doru -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

7 19

[Pharo-project] About Monticello Meta Data...
by Marcus Denker Feb. 13, 2013

Feb. 13, 2013

Hi, The current image has a size of 28.7MB (#20540). Now execute this expression: MCVersionInfo allInstances do: [ :each | each instVarNamed: 'ancestors' put: nil ]. save the image. Result: 20MB â¦ this means that MC is wasting 8MB of memory with data that should live in the repository. And the problem is that is gets larger with every commitâ¦ The other offender is ScriptLoader. Unload that, do a #cleanUpForRelease ==> 15.6MB Then .changes. Now it is at 32MB, plus 16MB sources. We really need to condense the sources for 2.0â¦ of course the problem is that it's broken (as it should be, because it is not tested). Marcus

4 9

[Pharo-project] Failing Tests 2.0
by Marcus Denker Feb. 13, 2013

Feb. 13, 2013

Hi, Here is a list of the failing tests for 2.0: https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/130/testReport/ Most of them are results of bug fixes we did last weekâ¦ sadly. Marcus

1 1

[Pharo-project] Open Issues 2.0: Down to 15
by Marcus Denker Feb. 13, 2013

Feb. 13, 2013

Hi, http://code.google.com/p/pharo/issues/list?can=2&q=milestone%3D2.0 15 issuesâ¦ it would be nice if everyone would have a look so we can close them soon. Marcus

1 0

[Pharo-project] [update 2.0] #20542
by Marcus Denker Feb. 13, 2013

Feb. 13, 2013

20542 ----- Issue 7496: MethodClassifier should ignore as yet unclassified when looking for other implementors http://code.google.com/p/pharo/issues/detail?id=7496 Issue 7429: FileReferences have a confusing/wrong external representation http://code.google.com/p/pharo/issues/detail?id=7429 Diff information: http://ss3.gemstone.com/ss/Pharo20/System-Support-MarcusDenker.784.diff http://ss3.gemstone.com/ss/Pharo20/FileSystem-Disk-MarcusDenker.48.diff

1 0

[Pharo-project] http://www.squeaksource.com/ShapeST80
by Usman Bhatti Feb. 13, 2013

Feb. 13, 2013

I am moving EyeSee from squeaksource to SThub. EyeSee has a dependency on ShapeST80 (ss/ShapeST80). Should I move this project to Moose team or is this project used somewhere independent of EyeSee? usman

3 2