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

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

[Pharo-project] Comparing collections, default behavior?

by Igor Stasenko

Since Collection includes #difference: protocol, i just thought that the default equality could be expressed like following: Collection>>= otherCollection ^ (self difference: otherCollection) isEmpty In other words, if two things having no differences, then they are equal. No? :) -- Best regards, Igor Stasenko AKA sig.

Feb. 4, 2011

Re: [Pharo-project] Export Pier to Latex

by Lukas Renggli

The pdf of book.seaside.st is done using the Pier-Book plugin. If you need to create something else than a book you might want to adapt the code, but otherwise it should work out of the box. Moose and Pharo use the same infrastructure for their books too. Lukas On Friday, 4 February 2011, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Does Pier support that?Â Do I need a plugin?Â Has someone tried to do something like that? :) > > Thanks! > Guille > -- Lukas Renggli www.lukas-renggli.ch

Feb. 4, 2011

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

by StÃ©phane Ducasse

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)]

Feb. 4, 2011

Re: [Pharo-project] [Hudson] News

by Marcus Denker

On Feb 4, 2011, at 3:58 PM, Miguel CobÃ¡ wrote: >> >> https://pharo-ic.lille.inria.fr/hudson/view/Pharo-Clients/ > > Why not Pharo-Distributions? Hmm... that would be something else... a client can let his distribution be build by the hudson, but you don't need to... I do not want to be the Distribution for Seaside, for example. The Seaside community should do that. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 4, 2011

Re: [Pharo-project] Hudson build for Seaside too?

by Dale Henrichs

Marcus, Since I seem to be on a symbolic version kick today, may I suggest that you use symbolic versions for Hudson: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. ((Smalltalk at: #ConfigurationOfSeaside30) project version: #stable) load. when you get a chance ... the above expression can be used for all of your Hudson builds regardless of pharo version. Dale On Feb 4, 2011, at 6:36 AM, Marcus Denker wrote: > >> On Feb 3, 2011, at 5:05 PM, Torsten Bergmann wrote: >> >>> OK - we have the hudson build for Pharo Core, Pharo, Moose, ... >>> >>> Since Pharo is the reference platform for Seaside >>> wouldnt it make sense to run a hudson build for >>> Seaside too: >>> >>> >>> Gofer new >>> squeaksource: 'MetacelloRepository'; >>> package: 'ConfigurationOfSeaside30'; >>> load. >>> >>> ((Smalltalk at: #ConfigurationOfSeaside30) project latestVersion) load. >>> > > Hudson now build a Seaside image and runs all tests after the Full image 1.2 build: > > https://pharo-ic.lille.inria.fr/hudson/job/Seaside%20on%20Pharo%201.2/ > > TODO: 1.3, after fixing the Full 1.3 build. > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

Feb. 4, 2011

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

by Dale Henrichs

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.

Feb. 4, 2011

Re: [Pharo-project] love CI

by Marcus Denker

On Feb 4, 2011, at 3:49 PM, laurent laffont wrote: > ci.pharo-project.org is really impressive. > > It's great for Pharo. > > But the really cool side is that you can show students what is software quality with the tool they use to develop. That's not slides. That's not theory. It's here. Real. > > One of the things I hated when giving Lectures about OO with Squeak was the "Intelligent Student Incident", which always happens: Exactly that students that you would want to attract (e.g. for doing a masters thesis) will just after 3 weeks realize that we do not do what we teach. We tell them how to program, but they look at the code in front of them and see something completely different. So there is some clash with only two possible solutions: Change what you Teach or Change what you Do. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 4, 2011

Re: [Pharo-project] [Hudson] News

by Miguel CobÃ¡

Very good! El vie, 04-02-2011 a las 12:42 +0100, Marcus Denker escribiÃ³: > -> Image after tests have run is now saved as a zip with a better name. e.g: > https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.2/lastSucce… > > -> Now we have a scheme in place for re-using generated images further "down" in the build stream > This means: Core is updated, then saved. Then a build of Full is triggered automatically, re-using the updated Core. > Full then is saved, usable for other projects (ie clients like Seaside or experimental things ike RPackacke or Opal) > > For one, this saves some build time and it makes builds on top of Full actually practical. > (this means my Opal image is always up-to date and I can start just with fresh image in the morning) > > -> Therefore, we have now a "Pharo-Clients" tab: > > https://pharo-ic.lille.inria.fr/hudson/view/Pharo-Clients/ Why not Pharo-Distributions? > > I am adding Seaside now, but we can add whatever we want to have knowledge on how changes influence clients. > (So if you want your project here, just send a mail with build instructions!) > > -> For Coral I am experimenting with dedicated regression test projects. This will be good for many things in the image, > too. (e.g. writing new sources, condensing changes, recompiling, decompiling...) > Cheers -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Feb. 4, 2011

[Pharo-project] love CI

by laurent laffont

ci.pharo-project.org is really impressive. It's great for Pharo. But the really cool side is that you can show students what is software quality with the tool they use to develop. That's not slides. That's not theory. It's here. Real. Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

Feb. 4, 2011