- Pharo-dev - lists.pharo.org

[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

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

by Schwab,Wilhelm K

There are times when it is necessary to protect the user from themselves. Modal to a particular window can be a VERY good thing. Several years ago, I remember watching in horror as my chairman was tinkering with a UI I had created that was not sufficiently modal, and he was at extreme risk of losing a lot of "work" as a result. You had to be there... BTW, he's a great guy and would have put it down to a learning experience for us both, not to mention a major bug report. I promptly made it modal, and all was well for years after that. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] Sent: Friday, May 25, 2012 9:12 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Progress bar in the top left I meant modal. > Since when? > > Rule #1 of UI: never block UI. > Because if you do, then we have no right to call it UI. > > do you know why we need this panic button (Alt-.) in our images? > Exactly because every silly thing prefers to block UI at any point, > even if it doesn't necessary. stef

May 26, 2012

Re: [Pharo-project] Working directory

by Igor Stasenko

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

Re: [Pharo-project] Book search: PL history and paradigms

by Frank Shearar

Well, objects are closures, so it makes sense to say that Java has closures. It doesn't have _lightweight_ closures with a decent syntax, but it does still have closures! Message passing is "message passing concurrency", which isn't the "message passing" in "message passing vs method invocation". Of course, the chart isn't meant to imply that some language X with paradigms A, B and C can't support paradigm D: you can, for instance, implement the logic programming paradigm in Scheme (miniKanren), Clojure (core.logic) and, well, not in Smalltalk yet (other than the embedded Prologs) because I haven't finished Nutcracker yet! frank On 25 May 2012 22:56, Hernan Wilkinson <hernan.wilkinson(a)10pines.com> wrote: > I have not read the book, but seeing the principal programming paradigm > poster makes me think about how good it is because Java and Smalltalk are > wrongly categorized, at least for what I understand of the poster (java with > closure, smalltalk not in the message passing category) > > > On Wed, May 23, 2012 at 8:11 AM, Frank Shearar <frank.shearar(a)gmail.com> > wrote: >> >> On 23 May 2012 12:00, Max Leske <maxleske(a)gmail.com> wrote: >> > I'm looking for a good book on programming language history with a focus >> > on the different paradigms (e.g. imperative, functional, â¦). Any >> > suggestions? >> >> Peter Van Roy's and Seif Haridi' "Concepts, Techniques, and Models of >> Computer Programming" [1] has loads on the different paradigms and >> comparing them. Not a lot on the _history_ of those though. >> >> ACM's HOPL conferences would provide the history of particular languages. >> >> Between those two sources you ought to be able to construct something >> like what you need by mapping CTM's "this model uses these paradigms" >> to the HOPL papers. >> >> frank >> >> [1] http://www.info.ucl.ac.be/~pvr/book.html >> >> >> > Thanks, >> > Max >> > > > > -- > HernÃ¡n Wilkinson > Agile Software Development, Teaching & Coaching > Phone: +54 - 011 - 4311 - 8404 > Mobile: +54 - 911 - 4470 - 7207 > email: hernan.wilkinson(a)10Pines.com > site:Â http://www.10Pines.com > Address: ParaguayÂ 523, Floor 7 N, Buenos Aires, Argentina >

May 25, 2012

Re: [Pharo-project] Book search: PL history and paradigms

by Hernan Wilkinson

I have not read the book, but seeing the principal programming paradigm poster makes me think about how good it is because Java and Smalltalk are wrongly categorized, at least for what I understand of the poster (java with closure, smalltalk not in the message passing category) On Wed, May 23, 2012 at 8:11 AM, Frank Shearar <frank.shearar(a)gmail.com>wrote: > On 23 May 2012 12:00, Max Leske <maxleske(a)gmail.com> wrote: > > I'm looking for a good book on programming language history with a focus > on the different paradigms (e.g. imperative, functional, â¦). Any > suggestions? > > Peter Van Roy's and Seif Haridi' "Concepts, Techniques, and Models of > Computer Programming" [1] has loads on the different paradigms and > comparing them. Not a lot on the _history_ of those though. > > ACM's HOPL conferences would provide the history of particular languages. > > Between those two sources you ought to be able to construct something > like what you need by mapping CTM's "this model uses these paradigms" > to the HOPL papers. > > frank > > [1] http://www.info.ucl.ac.be/~pvr/book.html > > > > Thanks, > > Max > > -- *HernÃ¡n Wilkinson Agile Software Development, Teaching & Coaching* *Phone: +54 - 011 - 4311 - 8404** Mobile: +54 - 911 - 4470 - 7207 email: hernan.wilkinson(a)10Pines.com site: http://www.10Pines.com <http://www.10pines.com/>* Address: Paraguay 523, Floor 7 N, Buenos Aires, Argentina

May 25, 2012