- Pharo-dev - lists.pharo.org

[Pharo-project] Now you can use Fuel with FileSystem
by Mariano Martinez Peck Feb. 18, 2012

Feb. 18, 2012

Hi guys. Now you can use FileSystem streams for Fuel. Fuel only needs one small package 'FuelFileSystem' which has just 3 extension methods, and that's all ;) There is also 'FuelFileSystemTests' which let's you run all fuel tests using FS. If you want to do that, change FLSerializationTest >> setUp to send #useFileSystemFileStream rather than #useStandardFileStream and that's all. To install: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfFuel'; load. (ConfigurationOfFuel project version: #bleedingEdge) load: 'withFS'. An example: | sourceArray loadedArray serializer stream materializer | sourceArray := Array with: 'a string' with: Transcript with: [ Transcript show: 'a string' ]. "Create a file and serialize on it" stream := (FSLocator imageDirectory / 'example.fuel') writeStream. serializer := FLSerializer newDefault. serializer serialize: sourceArray on: stream. stream close. "Load from the file" stream := (FSLocator imageDirectory / 'example.fuel') readStream. materializer := FLMaterializer newDefault. loadedArray := (materializer materializeFrom: stream) root. Cheers -- Mariano http://marianopeck.wordpress.com

6 11

[Pharo-project] three PointerFinder failing tests fixed
by Pavel Krivanek Feb. 18, 2012

Feb. 18, 2012

Hi, I created a patch that fixes three of currenty failing tests: http://code.google.com/p/pharo/issues/detail?id=5329 Cheers, -- Pavel

1 0

[Pharo-project] pharo vision
by StÃ©phane Ducasse Feb. 18, 2012

Feb. 18, 2012

22 40

[Pharo-project] Nautilus with Refactorings
by Benjamin Feb. 18, 2012

Feb. 18, 2012

Hi guys, I am glad to announce that refactorings (RBEngine) are now integrated into Nautilus :) You can also found the latest image on Jenkins: https://ci.lille.inria.fr/pharo/job/Nautilus%20with%20Refactorings/ I hope you will enjoy it, and as usual, any feedback is welcome :) (the next step is to do a nice changes browser :) ) Ben

7 19

[Pharo-project] removing DataStreamTest?
by StÃ©phane Ducasse Feb. 18, 2012

Feb. 18, 2012

Hi I was planning to fix the two tests so that the file is deleted in the teardown but I really wonder if there are testing anything. New issue 5321 by renggli: DataStreamTest creates files that are not deleted http://code.google.com/p/pharo/issues/detail?id=5321 DataStreamTest>>#testFileNamedtest DataStreamTest>>#testReadOnlyFileNamedtest testFileNamed | testString file | testString := 'testString'. file := ReferenceStream fileNamed: (self name, 'test'). file nextPut: testString. file close. file := ReferenceStream fileNamed: (self name, 'test'). self assert: file next = testString. file close. testReadOnlyFileNamed | testString file | testString := 'testString'. file := ReferenceStream fileNamed: (self name, 'test'). file nextPut: testString. file close. file := ReferenceStream readOnlyFileNamed: (self name, 'test'). self assert: file next = testString. file close.

1 0

[Pharo-project] new Issue 5325: PackageInfo dependent on deprecated MethodReference
by Pavel Krivanek Feb. 18, 2012

Feb. 18, 2012

see http://code.google.com/p/pharo/issues/detail?id=5325 Cheers -- Pavel

1 0

[Pharo-project] Pharo sprint - summary
by Tudor Girba Feb. 18, 2012

Feb. 18, 2012

Hi, Here is a summary of what we discussed around Pharo issues. Topics: - The process to get to the mini image - Actionable tasks to improve the current situation - Current architecture - Future architecture Problems: - Building speed - Where do we work: Core or Dev - How to collaborate Actions: - Create the OnPharoHead group on Jenkins The goal is to provide a space in which curated projects (e.g., RB, Moose) are built against the head of Pharo. If the project-specific build gets red, the integrator of the project announces the Pharo core team about the origin of the problems. If the project-specific build gets green, the latest Pharo image is integrated in the official continuous integration - We need to speed up the creation of a dev image (core + decent tools) for core developers. To do this, we need to introduce an incremental job that loads the updates starting from the last https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/. This will make the load much faster (currently, the official build takes 20+ minutes), as the official one is based on an older seed image. - Grease does not load cleanly in Pharo 1.4 because some methods were integrated already. **Someone** has to create a ConfigurationOfGrease for Pharo 1.3, and a baseline for 1.4. - People seem to believe that Builder is not maintained. Lukas maintains it, but to integrate changes, he needs pull requests on Github. - The work on Filesystem should be synchronized. We need to establish the link with Colin. An email must be sent to him. Camillo can you send him an email? The squeaksource/fs repository contains renamings, that are not necessary. Camillo should get in the loop. - RB and AST are important pieces that should be integrated by one person. Lukas offers to play the integrator role. Note: An integrator is more than a maintainer in that he actively (and positively) works with contributors. To ensure an easier collaboration, RB and AST will get an official inbox repository. Lukas will ensure that the architecture of RB and AST remains clean, that the test coverage improves, as well as that new clients are satisfied. The AST extensions (new variable nodes for self, super, ...) leak semantics into the syntax AST. Furthermore they break rewrite rules, code critics and refactoring. Instead, the AST-Semantics package should be dispatched through (or a similar independent extension package). For the parametrization of the RB environment (related to the remote access), experiments with RB (and possibly other frameworks) should be conducted first. If these experiments prove RB to be the right tool for remote access, the changes can be submitted for inclusion. Doru, Lukas, Stef, Philippe, Fabrizio, Stefan and Jorge

1 0

[Pharo-project] [update 1.4] #14339
by Marcus Denker Feb. 18, 2012

Feb. 18, 2012

14339 ----- Issue 5323: PluggableListMorph problem when multiple selection and navigate with keyboard http://code.google.com/p/pharo/issues/detail?id=5323 Issue 5324: TestRunner red square of death http://code.google.com/p/pharo/issues/detail?id=5324 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 1.3] #13322
by Marcus Denker Feb. 18, 2012

Feb. 18, 2012

13322 ----- Issue 4753: Implementors browser doesnt show decompiled source http://code.google.com/p/pharo/issues/detail?id=4753 -- Marcus Denker -- http://marcusdenker.de

1 0

Feb. 18, 2012

14338 ----- - Issue 3547: Have a look at the new match: implementation. Thanks BernardoContreras. http://code.google.com/p/pharo/issues/detail?id=3547

1 0