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

[Pharo-project] Monticello Confusion

by Camillo Bruni

I have SLICE-Issue-4773-rename-includesAnyOf-and-includesAllOf-CamilloBruni.1 on the ss3.gemstone.com/ss/PharoInbox. If I use the GUI in the latest Pharo Image and check for changes with this version - nothing. If I load the code I get failing dependencies => so there are changes introduced by this version. Has anyone a clue? best cami

Sept. 30, 2011

[Pharo-project] RPackage and update?

by Alexandre Bergel

Hi! I experienced several problems with RPackage, essentially due to some missing update. Am I the only one to experience this? I could not load Nautilus because apparently, some classes where supposed to be defined in an RPackage. And I deleted these classes some time ago. Also, I could not find an easy way to rename a package. Changing the category of a class put the system in an incoherent state. I know that this task is difficult, but I am wondering what is the plan. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 30, 2011

Re: [Pharo-project] SystemReporter for Pharo [WAS] Fwd: [update 1.4] #14177

by Alexander LazareviÄ

Mariano, great that you made it work in Pharo. Below method was just a work in progress. Thanks, Alex 2011/9/30 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi guys. This is a small tool done by Alexander LazareviÄÂ to get > information from the system. Very useful when reporting bugs. So keep it in > mind. > You can do SystemReporter open. or directly open it from the menu System -> > SystemReporter. > > Alexandre: we found an implemented message #environ in: > reportOSEnvironment: aStream > > Â Â Â | env | > Â Â Â self header: 'Operating System Environment' on: aStream. > Â Â Â env := [Smalltalk os environ] on: Error do: [^self]. > Â Â Â env keys asSortedCollection do: [:name | > Â Â Â Â Â Â aStream nextPutAll: name; nextPut: $=; nextPutAll: (env at: name); > cr] > > so...it seems broken. > > If you want to take a look to the changes we have to do in order to make it > work in Pharo: > > http://www.squeaksource.com/SystemReporterPharo > > Cheers > > > ---------- Forwarded message ---------- > From: Marcus Denker <marcus.denker(a)inria.fr> > Date: Fri, Sep 30, 2011 at 11:43 AM > Subject: [Pharo-project] [update 1.4] #14177 > To: An open mailing list to discuss any topics related to an open-source > Smalltalk <Pharo-project(a)lists.gforge.inria.fr> > > > 14177 > ----- > > Issue 4851: Â Â We should integrate systemReporter > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=4851 > > > > -- > Marcus Denker -- http://marcusdenker.de > > > > > > -- > Mariano > http://marianopeck.wordpress.com > >

Sept. 30, 2011

[Pharo-project] [update 1.3] #13313

by Marcus Denker

13313 ----- Issue 4867: DiÃ¡logo de Implementeros y de Senderos no protestan quando cÃ³digo cambia http://code.google.com/p/pharo/issues/detail?id=4867 -- Marcus Denker -- http://marcusdenker.de

Sept. 30, 2011

[Pharo-project] [update 1.4] #14180

by Marcus Denker

14180 ----- Issue 4876: Add Announcement on Tests (Part2) http://code.google.com/p/pharo/issues/detail?id=4876 Issue 4876: Add Announcement on Tests http://code.google.com/p/pharo/issues/detail?id=4876 Issue 4874: syler missplaced... left over http://code.google.com/p/pharo/issues/detail?id=4874 -- Marcus Denker -- http://marcusdenker.de

Sept. 30, 2011

[Pharo-project] [update 1.4] #14179

by Marcus Denker

14179 ----- Issue 4876: Add Announcement on Tests (Part1) http://code.google.com/p/pharo/issues/detail?id=4876 -- Marcus Denker -- http://marcusdenker.de

Sept. 30, 2011

[Pharo-project] [update 1.3] #13312

by Marcus Denker

13312 ----- Issue 4874: syler missplaced... left over http://code.google.com/p/pharo/issues/detail?id=4874 -- Marcus Denker -- http://marcusdenker.de

Sept. 30, 2011

[Pharo-project] SystemReporter for Pharo [WAS] Fwd: [update 1.4] #14177

by Mariano Martinez Peck

Hi guys. This is a small tool done by Alexander LazareviÄ to get information from the system. Very useful when reporting bugs. So keep it in mind. You can do SystemReporter open. or directly open it from the menu System -> SystemReporter. Alexandre: we found an implemented message #environ in: reportOSEnvironment: aStream | env | self header: 'Operating System Environment' on: aStream. env := [Smalltalk os environ] on: Error do: [^self]. env keys asSortedCollection do: [:name | aStream nextPutAll: name; nextPut: $=; nextPutAll: (env at: name); cr] so...it seems broken. If you want to take a look to the changes we have to do in order to make it work in Pharo: http://www.squeaksource.com/SystemReporterPharo Cheers ---------- Forwarded message ---------- From: Marcus Denker <marcus.denker(a)inria.fr> Date: Fri, Sep 30, 2011 at 11:43 AM Subject: [Pharo-project] [update 1.4] #14177 To: An open mailing list to discuss any topics related to an open-source Smalltalk <Pharo-project(a)lists.gforge.inria.fr> 14177 ----- Issue 4851: We should integrate systemReporter http://code.google.com/p/pharo/issues/detail?id=4851 -- Marcus Denker -- http://marcusdenker.de -- Mariano http://marianopeck.wordpress.com

Sept. 30, 2011

[Pharo-project] [update 1.4] #14177

by Marcus Denker

14177 ----- Issue 4851: We should integrate systemReporter http://code.google.com/p/pharo/issues/detail?id=4851 -- Marcus Denker -- http://marcusdenker.de

Sept. 30, 2011

[Pharo-project] [update 1.4] #14176

by Marcus Denker

14176 ----- Issue 4855: Add warning handling for tests http://code.google.com/p/pharo/issues/detail?id=4855 -- Marcus Denker -- http://marcusdenker.de

Sept. 30, 2011