- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.1] #11210
by Marcus Denker Feb. 14, 2010

Feb. 14, 2010

11210 ----- Issue 1966: remove WordArray>>#bobsTest Issue 1965: remove squeakpages methods from ServerDirectory Issue 1958: refactor #definitionST80 Issue 1928: Remaining _ in comments Issue 669: Dependency between Morph-Kernel and FileList -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] issue 1499 in PharoDev 1.0 ???
by Mariano Martinez Peck Feb. 14, 2010

Feb. 14, 2010

Hi Frederic. I was looking for the packages to next PharoDev and I noticed to commited a new version of NewInspector (NewInspector-FredericPluquet.57) Do you know if this also work in 1.0 so that I can include the fix ? Thanks Mariano

1 0

[Pharo-project] [update 1.1] #11209
by Marcus Denker Feb. 14, 2010

Feb. 14, 2010

11209 ----- Issue 1953: Network: smtp should send helo first -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [update 1.0] #10510
by Marcus Denker Feb. 14, 2010

Feb. 14, 2010

10510 ----- Issue 1788: SMTPClient does not send HELO or EHLO, session is not initiated Issue 1953: Network: smtp should send helo first -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] GoferApiTest failing (WinXP)
by Ch Lamprecht Feb. 14, 2010

Feb. 14, 2010

Hello to everybody, running the tests in latest images PharoCore-1.1 and 1.0 on WinXP I see GoferApiTest>>#testSubDirectoryRepository failing. It could be fixed by changing MCSubDirectoryRepository>>#description + ^ directory pathName, FileDirectory slash , '*' - ^ directory pathName, '/*' The current implementation works because '/' and '\' both are valid path separators on windows. Assuming '/' as path delimiter would cause trouble with MacFileDirectory - but that might be obsolete anyway. So may be the test is too strict? I just started to follow this list and the Pharo project ('Recreational programmer' btw. - thanks for the kind welcome message ;) ). Should I report this? And if so: It is a MC issue, should it be reported using the Pharo tracker or somewere else? Cheers, Christoph

4 7

[Pharo-project] FileSystem
by StÃ©phane Ducasse Feb. 14, 2010

Feb. 14, 2010

hi Colin Is there a way not to have to specify the FileSystem to create a stream for a file on disk? str := FSUnixFilesystem new writeStreamOn: 'giffle'. str nextPutAll: 'zzzzzzzzzz'. str close -> str := 'giffle' asWriteStream str nextPutAll: 'zzzzzzzzzz'. str close is there a way to do currentFolder doWithAllFiles: [:each | Transcript show: each name ; show: each size ; cr] Do I have to use an FSPreOrderGuide? Are there some behavior like doWithAllFiles already defined? I have the impression that having some extensions could make the interfaces smoother. I liked some of the aspects of the rio ones, even if I did not like the chaining one. Stef

3 4

[Pharo-project] FileSystem question
by StÃ©phane Ducasse Feb. 14, 2010

Feb. 14, 2010

I'm trying to move some of the examples of Coral from rio to filesystem and I get some questions. Are there some examples (not tests)? What is the difference between FSReference and FSPath? For example how can I print in the Transcript all the files in my current dir? Stef

3 3

[Pharo-project] Pharo changing the game
by Torsten Bergmann Feb. 14, 2010

Feb. 14, 2010

Interesting read (read [2] then [1]), maybe Pharo can change the game ... bye T. [1] http://www.jarober.com/blog/blogView?showComments=true&printTitle=Balkaniza… [2] http://www.threeriversinstitute.org/blog/?p=466 -- NEU: Mit GMX DSL Ã¼ber 1000,- Â¿ sparen! http://portal.gmx.net/de/go/dsl02

17 39

[Pharo-project] About using toolbuilder
by stephane ducasse Feb. 14, 2010

Feb. 14, 2010

I tried to use toolbuilder to open tools like the changeSorter and I always got a rather small window. So I checked in Squeak and the buildPluggableWindow method is different Should we integrate this changes? http://code.google.com/p/pharo/issues/detail?id=1963 buildPluggableWindow: aSpec | widget children label | aSpec layout == #proportional ifFalse:[ "This needs to be implemented - probably by adding a single pane and then the rest" ^self error: 'Not implemented'. ]. widget := PluggableStandardWindow new. self register: widget id: aSpec name. widget model: aSpec model. (label := aSpec label) ifNotNil:[ label isSymbol ifTrue:[widget getLabelSelector: label] ifFalse:[widget setLabel: label]]. children := aSpec children. children isSymbol ifTrue:[ widget getChildrenSelector: children. widget update: children. children := #(). ]. widget closeWindowSelector: aSpec closeAction. panes := OrderedCollection new. self buildAll: children in: widget. - aSpec extent ifNotNil:[widget extent: aSpec extent]. + self buildHelpFor: widget spec: aSpec. + widget bounds: (RealEstateAgent + initialFrameFor: widget + initialExtent: (aSpec extent ifNil:[widget initialExtent]) + world: self currentWorld). widget setUpdatablePanesFrom: panes. ^widget A related question is do we get rid of the method creation that do not rely on toolbuilder? I think that it would make sense. Stef

1 0

[Pharo-project] [ANN 1.1] pre-built core 1.1 #11208
by Marcus Denker Feb. 13, 2010

Feb. 13, 2010

http://gforge.inria.fr/frs/download.php/26404/PharoCore-1.1-11208-UNSTABLE.… -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0