- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Which ConfigurationOfPharo should use in Pharo 1.2 ?

by GermÃ¡n Arduino

Thanks by the explanations Dale. Thanks Guillermo and Markus by the points. Until moment any way of installation I tried failed with different sort of messages. By now I downloaded the ready image pointed by Markus but would like to build my own. Thanks! 2011/2/4 Dale Henrichs <dhenrich(a)vmware.com>: > Sure: > > Â http://gemstonesoup.wordpress.com/2011/01/17/metacello-1-0-beta-28-unearthe… > > Be sure to look at the section of development cycle ... and tools support, too... > > Dale > > On Feb 4, 2011, at 6:37 AM, Guillermo Polito wrote: > > Dale, Is there a place where I can read how to configure the symbolic versions? > > Thx! > Guille :) > > On Fri, Feb 4, 2011 at 11:29 AM, Dale Henrichs <dhenrich(a)vmware.com<mailto:dhenrich@vmware.com>> wrote: > ConfigurationOfPharo should have a #stable symbolic version defined that specifies the version that should be used in 1.2, 1.1, and 1.0 ... then one just loads the #stable version: > > Â (ConfigurationOfPharo project version: #stable) load > > and you'll get the right version loaded for the platform version ... even though the version is under development I think it is valid to specify a #stable symbolic version for Pharo1.2, just so folks don't have to ask this question over and over again ... Don't let the name 'stable' scare you ... > > The intent is that the #stable symbolic version specifies the version that should be loaded .... the developer decides which versions are #stable for each platform version and when a new version becomes "the version to use" the developer updates the specification. > > The users of a configuration shouldn't have to think ... remember in the past the recommended pattern was: > > Â ConfigurationOfPharo project latestVersion load > > and that worked fine until Pharo1.1 and Pharo1.2 were introduced. The expression: > > Â (ConfigurationOfPharo project version: #stable) load > > is intended to replace the use of #latestVersion because it makes it possible to explicitly specify the "latest version" on a platform by platform and platform version basis... > > Sorry if I appear to be ranting ... I'm just trying to get the message out:) > > Dale > > On Feb 4, 2011, at 6:01 AM, Guillermo Polito wrote: > > I'm Using '1.2-beta2'. > > Should we remove invalid and unused versions? Â I'll add a few comments at lunch time ;) > > On Fri, Feb 4, 2011 at 10:53 AM, GermÃ¡n Arduino <garduino(a)gmail.com<mailto:garduino@gmail.com><mailto:garduino@gmail.com<mailto:garduino@gmail.com>>> wrote: > I tried the 2 latest Beta and fail, also the 1.1 version fail. > > Which ConfigurationOfPharo I should use with Pharo 1.2 ? > > Cheers. > > > > > > > > -- ================================================= GermÃ¡n S. ArduinoÂ <gsa @ arsol.net>Â Â Twitter: garduino Arduino Software & Web HostingÂ Â http://www.arduinosoftware.com PasswordsProÂ http://www.passwordspro.com =================================================

Feb. 4, 2011

Re: [Pharo-project] The Comment Game - MMORPG for real

by Guillermo Polito

Shoot On Fri, Feb 4, 2011 at 2:13 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > I propose a little game. > > Each day (not Sunday) I will take a not commented class in PharoCore (in > development - 1.3) and tell it on this list. The game is to propose a > comment and at the end of the day the best comment will be integrated with > the name of his author. > > One day - One comment. > > Ready ? > > Laurent Laffont - @lolgzs <http://twitter.com/#%21/lolgzs> > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ >

Feb. 4, 2011

Re: [Pharo-project] About FS: sad reality.

by Tudor Girba

Thanks, Max. I am sure that would help the situation. Cheers, Doru On 4 Feb 2011, at 18:09, Max Leske wrote: > I'll try to give it a shot in the next two or three months if that's any comfort. > > Max > > > On 04.02.2011, at 17:36, StÃ©phane Ducasse wrote: > >> Hi guys >> >> I'm sorry but I stopped working on FS. I cannot guess what is private or not, what is the interface of this code. >> I spent my time guessing and guessing wrong. So I stop. Simple. >> In addition I will veto the integration of this code in this state to be added into pharo (sad I started to write an help but >> it is probably full of mistakes). I HATE undocumented code that tell me eveyr minutes that I'm a fucking idiot. >> Too bad I'm not smart enough. Now without decent comments (I mean more than a line in class comment when there is one) we cannot accept code. >> Sad but true. Good luck if you want to use it and improve it. >> >> Stef > > -- www.tudorgirba.com "Speaking louder won't make the point worthier."

Feb. 4, 2011

[Pharo-project] The Comment Game - MMORPG for real

by laurent laffont

I propose a little game. Each day (not Sunday) I will take a not commented class in PharoCore (in development - 1.3) and tell it on this list. The game is to propose a comment and at the end of the day the best comment will be integrated with the name of his author. One day - One comment. Ready ? Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

Feb. 4, 2011

Re: [Pharo-project] About FS: sad reality.

by Max Leske

I'll try to give it a shot in the next two or three months if that's any comfort. Max On 04.02.2011, at 17:36, StÃ©phane Ducasse wrote: > Hi guys > > I'm sorry but I stopped working on FS. I cannot guess what is private or not, what is the interface of this code. > I spent my time guessing and guessing wrong. So I stop. Simple. > In addition I will veto the integration of this code in this state to be added into pharo (sad I started to write an help but > it is probably full of mistakes). I HATE undocumented code that tell me eveyr minutes that I'm a fucking idiot. > Too bad I'm not smart enough. Now without decent comments (I mean more than a line in class comment when there is one) we cannot accept code. > Sad but true. Good luck if you want to use it and improve it. > > Stef

Feb. 4, 2011

[Pharo-project] About FS: sad reality.

by StÃ©phane Ducasse

Hi guys I'm sorry but I stopped working on FS. I cannot guess what is private or not, what is the interface of this code. I spent my time guessing and guessing wrong. So I stop. Simple. In addition I will veto the integration of this code in this state to be added into pharo (sad I started to write an help but it is probably full of mistakes). I HATE undocumented code that tell me eveyr minutes that I'm a fucking idiot. Too bad I'm not smart enough. Now without decent comments (I mean more than a line in class comment when there is one) we cannot accept code. Sad but true. Good luck if you want to use it and improve it. Stef

Feb. 4, 2011

Re: [Pharo-project] FS: how to create a file?

by Max Leske

There is no native rename. It's pretty much read the contents, delete the file, create a new file from contents. Max On 04.02.2011, at 17:31, StÃ©phane Ducasse wrote: > > On Feb 4, 2011, at 5:10 PM, Lukas Renggli wrote: > >> Stef, >> >> There is not much sense in creating a file without also putting >> something inside. There are various methods that give you a write >> straeam onto a new file. > > yes but consistent never hurts. > And I could create en empty file because an empty is an information. > > Do you know how to rename a file? Because I could not figure out. > >> Also note that FSFilesystem>>#createDirectory: is a private method, >> like about all other methods in there too. You are not supposed to >> call it directly. > > > Now I hate FS. I will stop working on it. > I prefer a worse system with doc that one better without. I'm spending hours on it and I'm crawling > just because colin never ever thought that one idiot could want to use it. > > I cannot work on something that aliens me that way, too bad. > > Tx for your answer for me this is the end of the story. Wonderful community that does not know how to write comments. > > We can always cry that the world does not recognize Smalltalk value, but when I see python docs, they got it right! > > Stef

Feb. 4, 2011

Re: [Pharo-project] FS: how to create a file?

by Max Leske

I've written tests with empty files like so: (aReference / 'emptyFile) writeStreamDo: [ :stream | ]. It's a bit lengthy but it's a pretty cool syntax for most write operations to files. Max On 04.02.2011, at 17:10, Lukas Renggli wrote: > Stef, > > There is not much sense in creating a file without also putting > something inside. There are various methods that give you a write > straeam onto a new file. > > Also note that FSFilesystem>>#createDirectory: is a private method, > like about all other methods in there too. You are not supposed to > call it directly. > > Lukas > > On Friday, 4 February 2011, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Hi >> >> I would like to write a test to see if children includes files >> >> | ref children alpha | >> filesystem createDirectory: '/alpha'. >> filesystem createDirectory: '/alpha/beta'. >> filesystem createDirectory: '/alpha/gamma/'. >> >> Now how do I create a file? There is createDirectory but not createFile. >> >> I think that there is a lot of work before FS can get into the image..... >> >> Stef >> >> >> >> >> testChildrenWithFilesAndDirectories >> "Children of a reference are all the files and directories contained in this reference" >> "self debug: #testChildrenWithFilesAndDirectories" >> | ref children alpha | >> filesystem createDirectory: '/alpha'. >> filesystem createDirectory: '/alpha/beta'. >> filesystem createDirectory: '/alpha/gamma/'. >> filesystem working / '/alpha/gamma/'. >> alpha := filesystem referenceTo: '/alpha'. >> alpha / 'zork.text'. >> self halt. >> ref := filesystem referenceTo: '/alpha'. >> children := ref children. >> self assert: children size = 2. >> >> children do: >> [:child | >> self assert: child class = FSReference. >> self assert: (child isChildOf: ref). >> self assert: (#('beta' 'gamma') includes: child basename)] >> > > -- > Lukas Renggli > www.lukas-renggli.ch >

Feb. 4, 2011

Re: [Pharo-project] FS: how to create a file?

by StÃ©phane Ducasse

On Feb 4, 2011, at 5:10 PM, Lukas Renggli wrote: > Stef, > > There is not much sense in creating a file without also putting > something inside. There are various methods that give you a write > straeam onto a new file. yes but consistent never hurts. And I could create en empty file because an empty is an information. Do you know how to rename a file? Because I could not figure out. > Also note that FSFilesystem>>#createDirectory: is a private method, > like about all other methods in there too. You are not supposed to > call it directly. Now I hate FS. I will stop working on it. I prefer a worse system with doc that one better without. I'm spending hours on it and I'm crawling just because colin never ever thought that one idiot could want to use it. I cannot work on something that aliens me that way, too bad. Tx for your answer for me this is the end of the story. Wonderful community that does not know how to write comments. We can always cry that the world does not recognize Smalltalk value, but when I see python docs, they got it right! Stef

Feb. 4, 2011

Re: [Pharo-project] FS: how to create a file?

by Lukas Renggli

Stef, There is not much sense in creating a file without also putting something inside. There are various methods that give you a write straeam onto a new file. Also note that FSFilesystem>>#createDirectory: is a private method, like about all other methods in there too. You are not supposed to call it directly. Lukas On Friday, 4 February 2011, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > I would like to write a test to see if children includes files > > | ref children alpha | > filesystem createDirectory: '/alpha'. > filesystem createDirectory: '/alpha/beta'. > filesystem createDirectory: '/alpha/gamma/'. > > Now how do I create a file? There is createDirectory but not createFile. > > I think that there is a lot of work before FS can get into the image..... > > Stef > > > > > testChildrenWithFilesAndDirectories > Â Â Â Â "Children of a reference are all the files and directories contained in this reference" > Â Â Â Â "self debug: #testChildrenWithFilesAndDirectories" > Â Â Â Â | ref children alpha | > Â Â Â Â filesystem createDirectory: '/alpha'. > Â Â Â Â filesystem createDirectory: '/alpha/beta'. > Â Â Â Â filesystem createDirectory: '/alpha/gamma/'. > Â Â Â Â filesystem working / '/alpha/gamma/'. > Â Â Â Â alpha := Â filesystem referenceTo: '/alpha'. > Â Â Â Â alpha / 'zork.text'. > Â Â Â Â self halt. > Â Â Â Â ref := filesystem referenceTo: '/alpha'. > Â Â Â Â children := ref children. > Â Â Â Â self assert: children size = 2. > > Â Â Â Â children do: > Â Â Â Â Â Â Â Â [:child | > Â Â Â Â Â Â Â Â self assert: child class = FSReference. > Â Â Â Â Â Â Â Â self assert: (child isChildOf: ref). > Â Â Â Â Â Â Â Â self assert: (#('beta' 'gamma') includes: child basename)] > -- Lukas Renggli www.lukas-renggli.ch

Feb. 4, 2011