- Pharo-dev - lists.pharo.org

[Pharo-project] SystemTracer

by Benjamin

Hello guys, for one of my projects, I'm trying to use SystemTracer to create anew image, but it appears that it doesn't work on Pharo ... I can create a new image, but I can't open it. I've tried with an older VM (Squeak 3.8.18beta1U), but it's the same ... Did someone already have this problem ? Does someone have a solution ? Thanks in advance, Ben

Jan. 27, 2011

Re: [Pharo-project] [squeak-dev] check out my blog "This Context" for Spoon and Naiad news

by Juan Vuletich

Craig Latta wrote: > Hi all-- > > Spoon 3 is nearing release (scheduled for the moment of equinox on > 20 March), featuring the first usable version of Naiad, Spoon's change > management system. Please check out my blog "This Context"[1] for news, > and the Spoon IRC channel[2] and mailing list[3] for discussion. > > > thanks! > > -C > > [1] http://thiscontext.wordpress.com > [2] irc://irc.freenode.net/#spoon > [3] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/spoon > > -- > Craig Latta > www.netjam.org/resume > + 31 020 894 6247 > + 1 415 287 3547 > It is great to know Spoon is alive! Cheers, Juan Vuletich

Jan. 27, 2011

[Pharo-project] [ANN 1.2] re-built Core 1.2 RC2 #12324

by Marcus Denker

https://gforge.inria.fr/frs/download.php/28189/PharoCore-1.2rc2-12324.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 27, 2011

[Pharo-project] [update 1.2] #12324

by Marcus Denker

12324 ----- RC2 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 27, 2011

[Pharo-project] Issue 3602 in pharo: Code evaluation possible in About box ...

by pharo＠googlecode.com

Status: Accepted Owner: Torsten....(a)astares.de Labels: Milestone-1.3 New issue 3602 by Torsten....(a)astares.de: Code evaluation possible in About box ... http://code.google.com/p/pharo/issues/detail?id=3602 One can open the about box, select the word "LICENSE" and hit Cmd+D (which is a "do it"). => gives an error that this class is missing This could also make it possible to "break into" a deployed image that uses the about box for own purposes since one can select "define new class" from the menu then and in the next page (where one typically edits the class creation message one can enter any expression like "Browser open" or whatever).

Jan. 27, 2011

Re: [Pharo-project] Issue 3601 in pharo: Recommended Seaside version in Pharo-1.2 outdated

by pharo＠googlecode.com

Comment #3 on issue 3601 by Torsten....(a)astares.de: Recommended Seaside version in Pharo-1.2 outdated http://code.google.com/p/pharo/issues/detail?id=3601 Yes, but it looks like your fix ("ImageForDevelopers-pharo-JohanBrichau.248") was not yet integrated into ConfigurationOfPharo. Fixed in ConfigurationOfPharo-tbn.128

Jan. 27, 2011

Re: [Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem

by pharo＠googlecode.com

Updates: Status: Closed Comment #20 on issue 3489 by marcus.d...(a)gmail.com: Pharo 1.2-dev still uses Preferences in BaseSoundSystem http://code.google.com/p/pharo/issues/detail?id=3489 (No comment was entered for this change.)

Jan. 27, 2011

Re: [Pharo-project] Issue 3601 in pharo: Recommended Seaside version in Pharo-1.2 outdated

by pharo＠googlecode.com

Comment #2 on issue 3601 by johanbri...(a)me.com: Recommended Seaside version in Pharo-1.2 outdated http://code.google.com/p/pharo/issues/detail?id=3601 I fixed this already in #3540

Jan. 27, 2011

Re: [Pharo-project] About FileSystem (probably not for 1.3)

by StÃ©phane Ducasse

On Jan 27, 2011, at 10:07 AM, Tudor Girba wrote: > Hi Stef, > > I think your mail can easily be misunderstood to say that Filesystem is crap and that the authors did a bad job. I believe your intention was simply to push people to write more comments and give Filesystem as an example of a fine system that does not have comments :). Exact :) > Filesystem is a nice piece of work and the authors did a good job. yes > I understand that there are no comments, but the documentation found on Lukas' website provides a better overview than most class comments in Pharo: > http://www.lukas-renggli.ch/blog/filesystem-1 > http://www.lukas-renggli.ch/blog/filesystem-2 > > So, why not just copy these into the help system? This is not a solution. This would be a workaround. This is incomplete and missing important information. Then we should also review some api like workingDirectory returning a path. I started to write important class comments like DO NOT USE subclasses of FSDisk.... directly. Let FSDiskFilesystem returns the current filesystem. FSPath is for internal framework use. That I learned the hard way = spending 5 times more time than expected to do something. Documentation is not a by product. Finally I started to reorganize the package because there is no point directing people to **I want a comment for every single method.** I hate a system that tells me in permanence that I'm an idiot because what is written is not obvious to me. Sorry to be stubborn but I will not move on micrometer on that. ****Code without documentation and comments does not exist*** If the community wants a better filesystem then we should have comments in FS. Since I want it I will slowly and painfully try to understand that I'm idiot because I do not understand and reverse engineer what could have been written up front. I will slowly do it since there is no other paths. But I guess that you understand my deep state of mind. Stef

Jan. 27, 2011

Re: [Pharo-project] [ANN 1.3] pre-build Core 1.3a#13021

by Marcus Denker

On Jan 27, 2011, at 11:07 AM, laurent laffont wrote: > Shouldn't we have Pharo 1.3 (Dev) added on Hudson too ? Early feeback seems better to me. > Yes, this is on the TODO. Especially for the Full image, continuous integration is needed. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 27, 2011