November 2013 - Pharo-dev - lists.pharo.org

FileSystem-Zip
by Nicolas Cellier Nov. 17, 2013

Nov. 17, 2013

FileSystem-Zip seems to be unused in Pharo3.0. What are the plans? Are there pitfall/known problems?

1 0

Annoying bug with TWM & Progress bars
by phil＠highoctane.be Nov. 17, 2013

Nov. 17, 2013

When one uses TWM (Tiling Window Manager), the progress bars are hidden behind it. How could one make those bars go a bit to the right so that we don't have this unfortunate effect? Phil

1 0

Nautilus issue with right click menus
by phil＠highoctane.be Nov. 17, 2013

Nov. 17, 2013

https://pharo.fogbugz.com/default.asp?12190 This bug is annoying since it requires to have a package selected. For newcomers, this is difficult to grasp. Maybe should we have a default package, like "Sandbox" or something present in the image and Nautilus starting in there. Phil

1 0

Spotlight discussion
by Juraj Kubelka Nov. 17, 2013

Nov. 17, 2013

Hi Esteban, StÃ©phane mentioned that you have some ideas how to improve Spotlight. I am interested to participate on it. Can we have a discussion about it? Thanks, Jura

7 13

New builder for Roassal: building geographical maps
by Alexandre Bergel Nov. 17, 2013

Nov. 17, 2013

Hi! During our pair coding session on Friday, we worked on a new builder for Roassal. Here is short example: | builder | builder := ROFranceMapBuilder new. builder shape circle size: 15; color: Color red; withLabel. builder showCities: #('Paris' 'Lyon' 'Marseille'). builder shape circle size: 25; color: Color blue; withLabel. builder show: 'Nice'. builder open It should produce: There is no reference to external files. It runs out of the box. In case you got a sudden need to press a like button or do some retweet, here a bit of material: https://www.facebook.com/media/set/?set=a.543459092407359.1073741830.340543… https://twitter.com/objectprofile/status/401433558684008448 On our facebook account we have many more screenshots. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 18

In-memory FileSystem write streams not being polymorphic
by NicolÃ¡s Papagna Maldonado Nov. 17, 2013

Nov. 17, 2013

Hi all! I've been working in a fix of PharoFilesOpener and decided to test the current behavior first before changing it, so I extracted the dependency to FileSystem and tried to use an instance created through FileSystem memory for testing. The code gets the write stream for a file and then sends the #isReadOnly message to do some stuff. The thing is that the streams returned form the in-memory file system are instances of WriteStream (see MemoryHandle >> writeStream) instead of StandardFileStream (see FileHandle >> writeStream) and so they don't respond the #isReadOnly message. Is this the expected way the in-memory file system should work? Shouldn't it return polymorphic file streams? If this is a bug, what change would you recommend to do? I was thinking about returning StandardFileStreams instances from MemoryHandle >> writeStream. Cheers! Nico PM

7 26

[pharo-project/pharo-core]
by GitHub Nov. 17, 2013

Nov. 17, 2013

Branch: refs/tags/30579 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] d6c0b5: 30579
by GitHub Nov. 17, 2013

Nov. 17, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: d6c0b575a99debda79114a992d2a5fe13ed44eea https://github.com/pharo-project/pharo-core/commit/d6c0b575a99debda79114a99… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-17 (Sun, 17 Nov 2013) Changed paths: R Collections-Strings.package/ByteString.class/instance/comparing/findSubstringViaPrimitive_in_startingAt_matchTable_.st M Collections-Strings.package/ByteString.class/instance/comparing/findSubstring_in_startingAt_matchTable_.st A Collections-Strings.package/String.class/instance/comparing/findIn_startingAt_matchTable_.st A Collections-Strings.package/String.class/instance/comparing/findSubstringViaPrimitive_in_startingAt_matchTable_.st M Collections-Strings.package/String.class/instance/converting/asWideString.st A Collections-Strings.package/WideString.class/instance/comparing/findIn_startingAt_matchTable_.st A Collections-Strings.package/WideString.class/instance/converting/asWideString.st A Collections-Strings.package/WideSymbol.class/instance/comparing/findIn_startingAt_matchTable_.st A Collections-Strings.package/WideSymbol.class/instance/converting/asWideString.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script234.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30579.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30579 3634 Clean up handling of WideStrings https://pharo.fogbugz.com/f/cases/3634 http://files.pharo.org/image/30/30579.zip

1 0

[issue tracker] Please review "fix review needed" issues
by Marcus Denker Nov. 17, 2013

Nov. 17, 2013

So we now have an automatic system to check that a change does not break tests and even passes Code Critique. Nevertheless, this does *not* mean that any change that passes is good. (e.g. a change that just deletes all tests is fine for the monkey). So we *need* people to look at proposed changes! Right now I feel that I decide far too many things. It would be very nice to have the input of more people. Marcus

3 5

Re: [Pharo-dev] A thought about backporting
by Stephan Eggermont Nov. 17, 2013

Nov. 17, 2013

btc wrote: >OMG! I only just noticed on the "RELEASE" page [1] the linked file "Pharo2.0-win.zip" [3] >has a last-modified-date of 2013-11-13. What crack [2] are you smoking? A "released" >file with a name like "Pharo2.0-win.zip" should NEVER change its contents. NEVER! It >SHOULD always remain the same - always - to the end of time! Backports are really >important but they should be labelled as a new version "release" or just as "latest" if >regularly uploaded from the CI. No. Releases on the website are for humans, not for automation. They should work and have all the latest backported bugfixes. Fixed versions for automation and sysadmins have build numbers. We have this covered with files.pharo.org Please read Van den Hamer & Lepoeter (1996) Managing Design Data: The Five Dimensions of CAD Frameworks, Configuration Management, and Product Data Management, Proceedings of the IEEE, Vol. 84, No 1, January 1996

8 9