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

Re: [Pharo-project] [Pharo-conf] Pharo Sprint â Saturday 10h00 â RMoD Lab

by Pavel Krivanek

With Markus we plan to meet at 10:00 in front of Gare Lille Flandres. Others can join us. -- Pavel On Sat, May 26, 2012 at 8:14 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > camillo > > I will come after lunch. > > Stef > On May 25, 2012, at 4:09 PM, Camillo Bruni wrote: > >> We would like to invite you to a Pharo Sprint on saturday at 10h00: >> >> Â Â Â http://www.doodle.com/t5uv5fhmm7adi6cs >> >> It will be held in the RMoD lab: >> >> Â Â Â http://rmod.lille.inria.fr/web/pier/contact >> >> The entrance will be closed and can only be opened with a badge. >> For those who standing in front of a closed door, call one of the >> following badge-owners: >> >> Â Â Â Camillo Bruni Â +33 7 86 95 40 78 >> Â Â Â Marcus Denker Â +33 3 62 65 52 58 >> >> see you! >> > > > _______________________________________________ > Pharo-conf mailing list > Pharo-conf(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-conf

May 26, 2012

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

by StÃ©phane Ducasse

thanks a lot for your greta and continuous effort On May 26, 2012, at 7:04 AM, Martin Dias 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 >

May 26, 2012

Re: [Pharo-project] Pharo Sprint â Saturday 10h00 â RMoD Lab

by StÃ©phane Ducasse

camillo I will come after lunch. Stef On May 25, 2012, at 4:09 PM, Camillo Bruni wrote: > We would like to invite you to a Pharo Sprint on saturday at 10h00: > > http://www.doodle.com/t5uv5fhmm7adi6cs > > It will be held in the RMoD lab: > > http://rmod.lille.inria.fr/web/pier/contact > > The entrance will be closed and can only be opened with a badge. > For those who standing in front of a closed door, call one of the > following badge-owners: > > Camillo Bruni +33 7 86 95 40 78 > Marcus Denker +33 3 62 65 52 58 > > see you! >

May 26, 2012

Re: [Pharo-project] Progress bar in the top left

by Bernardo Ezequiel Contreras

Mariano, That behavior was reported as a bug, see http://code.google.com/p/pharo/issues/detail?id=5526 (see my comments) Thanks On Wed, May 23, 2012 at 7:48 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi guys. Some time I ago, I submitted an issue that puts the progress bar > not in the middle of the screen but on the top left. I think it is much > better since it does not disturb you. > Now it seems that, or my change got accidently lost or someoone else put > the previous behavior. > So...was that on purpose or not? > > thanks > > -- > Mariano > http://marianopeck.wordpress.com > > -- Bernardo E.C.

May 26, 2012

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

by Martin Dias

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

May 26, 2012

Re: [Pharo-project] Working directory

by David T. Lewis

On Fri, May 25, 2012 at 05:59:17PM -0700, Sean P. DeNigris wrote: > > Igor Stasenko wrote > > > > we should integrate the chdir fix to osprocess > > into jenkins vms > > > > Oops, I took the error handler off the wrong call... > > ??OSProcess thisOSProcess chDir: ospPwd. > should have been > > ??[ OSProcess thisOSProcess chDir: ospPwd ] on: Exception do: []. > > And, the question still stands as to whether OSP and FS should have two > separate concepts of the working directory... Yes. They probably represent different concepts, so it is OK if they are implemented differently. 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. With respect to OSProcess, it is intentionally maintained separately from Squeak/Pharo and IMO should remain that way. It provides access to the external platform, which is useful. But the metaphorical desktop objects (files, desktops, file folders, etc) are artifacts of various operating systems and computing traditions, and there is no "right way" to represent the concept of a current working directory. OSProcess attempts to report CWD from the point of view of the external platform, but that does not make it right. It is perfectly legitimate for FS to define a concept of current working directory, and hopefully this would have a clear definition in terms of how it is to be used in the image. But there is no reason to expect that this definition of "current working directory" will be the same as the "current working directory" as understood by Unix, Windows, Android, or other computing platforms, some of which may not have any concept of "directory" at all. CommandShell also has a concept of current working directory, and this is also different from the CWD of OSProcess. CommandShell attempts to behave more like a shell, and when running on Windows it keeps track of the current volume (C: drive, D: drive, etc) in addition to the current working directory path associated with each volume. Again, then is platform dependent, and there is no particular reason to expect this concept of "current working directory" to make sense outside of the operating system that it is emulating. Dave

May 26, 2012

[Pharo-project] Jenkins

by Sean P. DeNigris

Pharo 1.3 build failing - why in last month? Are fixes still being applied? Pharo 1.4 Tests - windows build not running tests -- View this message in context: http://forum.world.st/Jenkins-tp4631891.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 26, 2012

Re: [Pharo-project] Working directory

by Sean P. DeNigris

Igor Stasenko wrote > > we should integrate the chdir fix to osprocess > into jenkins vms > Oops, I took the error handler off the wrong call... > Â OSProcess thisOSProcess chDir: ospPwd. should have been > Â [ OSProcess thisOSProcess chDir: ospPwd ] on: Exception do: []. And, the question still stands as to whether OSP and FS should have two separate concepts of the working directory... -- View this message in context: http://forum.world.st/Working-directory-tp4631865p4631888.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 26, 2012

Re: [Pharo-project] Working directory

by Igor Stasenko

On 26 May 2012 02:33, David T. Lewis <lewis(a)mail.msen.com> wrote: > +1 > > Thanks Igor. > yeah.. one of the problems, that we're running Pharo image tests on successfull build. But these tests are not including the tests for "optional" components, like OSProcess.. Because if we ship VM with PluginA, PluginB, apparently we should run tests which testing those plugins, to check that they are functional, even if they are not used by default into Pharo image(s). > Dave > > On Sat, May 26, 2012 at 02:13:34AM +0200, Igor Stasenko wrote: >> we should integrate the chdir fix to osprocess >> into jenkins vms >> >> On 25 May 2012 22:17, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> > When OSProcess is integrated, we will have two different concepts of the >> > working directory: >> > ??fsPwd := '/Volumes/Sean''s Universe/sean/.jenkins/jobs/Dynabook/' >> > asFileReference. >> > ??[ FileSystem disk changeDirectory: fsPwd ] on: Exception do: []. >> > ??FileSystem disk workingDirectory = fsPwd. "true" >> > >> > ??ospPwd := '/Volumes/Sean''s >> > Universe/sean/.jenkins/jobs/Dynabook/workspace'. >> > ??OSProcess thisOSProcess chDir: ospPwd. >> > ??FileSystem disk workingDirectory = ospPwd. "false" >> > ??(PipeableOSProcess command: 'pwd') output trimRight = ospPwd "true" >> > >> > -- >> > View this message in context: http://forum.world.st/Working-directory-tp4631865.html >> > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > >> >> >> >> -- >> Best regards, >> Igor Stasenko. > -- Best regards, Igor Stasenko.

May 26, 2012

Re: [Pharo-project] Working directory

by David T. Lewis

+1 Thanks Igor. Dave On Sat, May 26, 2012 at 02:13:34AM +0200, Igor Stasenko wrote: > we should integrate the chdir fix to osprocess > into jenkins vms > > On 25 May 2012 22:17, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > When OSProcess is integrated, we will have two different concepts of the > > working directory: > > ??fsPwd := '/Volumes/Sean''s Universe/sean/.jenkins/jobs/Dynabook/' > > asFileReference. > > ??[ FileSystem disk changeDirectory: fsPwd ] on: Exception do: []. > > ??FileSystem disk workingDirectory = fsPwd. "true" > > > > ??ospPwd := '/Volumes/Sean''s > > Universe/sean/.jenkins/jobs/Dynabook/workspace'. > > ??OSProcess thisOSProcess chDir: ospPwd. > > ??FileSystem disk workingDirectory = ospPwd. "false" > > ??(PipeableOSProcess command: 'pwd') output trimRight = ospPwd "true" > > > > -- > > View this message in context: http://forum.world.st/Working-directory-tp4631865.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > > -- > Best regards, > Igor Stasenko.

May 26, 2012