May 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 2.0] #20100

by Marcus Denker

We retract that update.... some strange error happens headless on macos. On May 26, 2012, at 4:17 PM, Marcus Denker wrote: > 20100 > ----- > > Issue 5964: WeakRegistry dictionary grows indefinitely large > http://code.google.com/p/pharo/issues/detail?id=5964 > -- > Marcus Denker -- http://marcusdenker.de > -- Marcus Denker -- http://marcusdenker.de

May 26, 2012

Re: [Pharo-project] Working directory

by David T. Lewis

On Sat, May 26, 2012 at 10:44:15AM +0200, Camillo Bruni wrote: > > On 2012-05-26, at 06:41, David T. Lewis wrote: > > > What is a "working directory"? And for that matter, what is a "directory"? > > These are concepts and metaphors that have been used in various ways by > > some (but not all) operating systems, and that do not automatically have > > a well defined meaning independent of those metaphors and operating systems. > > There is really no such thing as "current working directory" in Squeak/Pharo, > > so if you want to create such a concept you are free to do so in any way > > you please. > > well on all unix there is a very clear precise definition of it "getcwd()"! > and on all decent platforms there's a more or less clear notion of > what is a file and what is a directory? > > Talking about Pharo, which platforms do we target? > - Linux > - OS X > - Win You're right about that of course. I guess I just like to remind people that unix is not the only good operating system that has ever been invented, and that ideas like "files" are just part of a metaphor that was invented decades ago to help people relate their computer to something they already understood (a physical desk with a desktop and with file cabinets filled with folders that contained paper documents). With cell phones, tablets, and solid state storage it is quite possible that the ancient "desk with file cabinet" metaphors will become obsolete, so it is good to keep an open mind. > > maybe I am wrong, but I think we could assume a common denominator here? > (Using python and ruby yields to the same results AFAIK) I don't know. But OS X may well be an example of an environment that presents a file system view to the user that is different from the file system view at the unix file system or unix shell level. And Windows 7 appears to be trying to imitate OS X in that regard. If you implement a concept of "current working directory" in the image, you are free to define it in whatever way makes good sense. But there is no fundamental reason why you need to use a definition that matches the unix file system view (as reported by OSProcess). You might instead prefer to use a definition that matches what the OS X user expects to see in the finder, and maybe that is a different thing (I am not an OS X user, so apologies if I am getting this wrong). Dave

May 26, 2012

[Pharo-project] Pharo-2.0-Tests Â» 32,mac - Build # 100 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

May 26, 2012

[Pharo-project] Pharo-2.0-Tests Â» 32,mac - Build # 99 - Failure!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

May 26, 2012

[Pharo-project] [update 2.0] #20100

by Marcus Denker

20100 ----- Issue 5964: WeakRegistry dictionary grows indefinitely large http://code.google.com/p/pharo/issues/detail?id=5964 -- Marcus Denker -- http://marcusdenker.de

May 26, 2012

[Pharo-project] RPackage problem with obsolete classes

by Guillermo Polito

This test illustrate the problem: testMethodPackageFromObsoleteClass | pack method | pack := self createNewPackageNamed: 'P1'. foo := self createNewClassNamed: #FooForTest inPackage: pack. foo compileSilently: 'bar ^42'. method := foo>>#bar. foo removeFromSystem. self assert: (method packageFromOrganizer: pack organizer)equals: foo package. This seems to happen in non silent tests that - create a class/trait for test - sends an announcement with a compiled method instance (like, method recategorized) - remove the class/trait because they are for test only :) - then, since the announcements are handled asychronously, a method from an obsolete category reaches somewhere, and RPackage explodes. WIll open an issue. Guille

May 26, 2012

[Pharo-project] [update 2.0] #20099

by Marcus Denker

20099 ----- Issue 5983: update package names for Fuel 1.8 http://code.google.com/p/pharo/issues/detail?id=5983 Issue 5980: System Setting Browser broken: DNU #selectedNodePath http://code.google.com/p/pharo/issues/detail?id=5980 Issue 5976: Add explicit pad methods http://code.google.com/p/pharo/issues/detail?id=5976 Issue 5956: Let morphs announce when focus changes http://code.google.com/p/pharo/issues/detail?id=5956 -- Marcus Denker -- http://marcusdenker.de

May 26, 2012

[Pharo-project] [update 2.0] #20098

by Marcus Denker

20098 ----- Issue 5982: integrate Fuel 1.8 http://code.google.com/p/pharo/issues/detail?id=5982 -- Marcus Denker -- http://marcusdenker.de

May 26, 2012

[Pharo-project] [update 2.0] #20097

by Marcus Denker

20097 ----- Issue 5981: Make Model class independent on UI http://code.google.com/p/pharo/issues/detail?id=5981 Issue 5914: Object>>notYetImplemented currently impractical for TDD, uses #inform: which does not fail the tests. http://code.google.com/p/pharo/issues/detail?id=5914 Issue 5936: DateAndTime DOS conversion http://code.google.com/p/pharo/issues/detail?id=5936 -- Marcus Denker -- http://marcusdenker.de

May 26, 2012

Re: [Pharo-project] [ANN] Fuel Release Version 1.8

by Edgar J. De Cleene

On 5/26/12 2:04 AM, "Martin Dias" <tinchodias(a)gmail.com> wrote: > Hi all, > > We are proud to announce Fuel 1.8 with a lot of new features and > documentation. Of course, we don't stop working but it was time to > freeze a stable version. > > Fuel is an open-source general-purpose object serialization framework > developed in Pharo Smalltalk environment. More information on our > website [1]. > > Fuel works out of the box in Pharo from 1.1 up to 2.0 (checked at > #20094). Please check our documentation [2] for complete installation > and use guides. > > Below, there are some remarkable changes. > > - Much more complete user guides. > - Improved API for customizing how graph is traced. > - FuelMetalevel: serialization of stuff like classes and compiled > methods moved to an optional package. > - Customize objects to be treated as globals. > - Migrations: declare at materialization time class and variables renames. > - Weak references properly managed. Thanks to Juan Vuletich and Levente. > - Thanks Pavel for helping us improving FuelPackageLoader with > wonderful ideas and bug reports. > - Serialization speed up on large graphs by using specialized > collections. Thanks Levente. > - Encoder and Decoder: new reifications that clarify the design. > Thanks Colin Putney. > - Optimized serialization of "clean" BlockClosures, which don't need > the whole stack of contexts. Thanks Juan Vuletich and Eliot Miranda. > - Added a clear error hierarchy. > - Debug facilities, including graph visualization using Roassal. > Thanks Alexandre and Doru. > - Many more new tests. Including those from extension packages, we > have almost 600 tests. > - Repository moved from 'http://www.squeaksource.com/Fuel' to > 'http://ss3.gemstone.com/ss/Fuel'. > > If you are a Fuel user we are not aware of, please let us know! > > Best regards, > Martin and Mariano > > [1]: http://rmod.lille.inria.fr/web/pier/software/Fuel > [2]: > http://rmod.lille.inria.fr/web/pier/software/Fuel/Version1.8/Documentation > Congrats and start to read and try... Edgar

May 26, 2012