- Pharo-dev - lists.pharo.org

lineConversion for WriteStream
by Peter UhnÃ¡k July 10, 2016

July 10, 2016

Is there a reason why only MultiByteFileStream provides lineEndConvention: and not WriteStream? The problem is that if I use MemoryStore in tests it breaks, because DiskStore and MemoryStore return different write streams. '/tmp/test.txt' asFileReference writeStream ==> "MultiByteFileStream: '/tmp/test.txt'". (FileSystem memory / 'test.txt') writeStream ==> "a WriteStream" Can we either: a) have `lineEndConvention:` directly in the WriteStream, or b) have MemoryStore return MultiByteFileStream, or c) both? Thanks, Peter

5 16

inconsistent FileReference
by Peter UhnÃ¡k July 9, 2016

July 9, 2016

Imagine that you have '/tmp/a/b' folder containing 'c' file '/tmp/a/b' asFileReference ensureCreateDirectory. '/tmp/a/b/c' asFileReference writeStreamDo: [ :s | s nextPutAll: 'contents' ]. now there are three ways how you can see the contents of the c file x := '/tmp/a/b/c.txt' asFileReference. y := '/tmp' asFileReference / 'a' / 'b' / 'c.txt'. z := '/tmp' asFileReference / 'a/b/c.txt'. They clearly all point to the same file: x contents = y contents "true" x contents = z contents "true" Yet the last option is different x = y "true" x = z "false" Why is that? Because the parent is different: x parent pathString "'/tmp/a/b'" y parent pathString "'/tmp/a/b'" z parent pathString "'/tmp'" So the parent is based on how the reference was constructed, not what it is actually pointing to, which is stupid. Is this a bug? Is this a (nasty) expected behavior? Peter

3 2

[pharo-project/pharo-core]
by GitHub July 9, 2016

July 9, 2016

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

1 0

[pharo-project/pharo-core] 0fe882: 60142
by GitHub July 9, 2016

July 9, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 0fe8828aed520e8c28699f857272389cd563a56f https://github.com/pharo-project/pharo-core/commit/0fe8828aed520e8c28699f85… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-09 (Sat, 09 Jul 2016) Changed paths: M Morphic-Widgets-Basic.package/PluggableButtonMorph.class/instance/initialization/initialize.st R Morphic-Widgets-FastTable.package/FTFilterFunctionWithAction.class/instance/accessing/beExplicite.st A Morphic-Widgets-FastTable.package/FTFilterFunctionWithAction.class/instance/accessing/showWidget.st R Morphic-Widgets-FastTable.package/FTFunction.class/instance/accessing/beExplicite.st A Morphic-Widgets-FastTable.package/FTFunction.class/instance/accessing/showWidget.st R Morphic-Widgets-FastTable.package/FTFunctionWithField.class/instance/accessing/beExplicite.st A Morphic-Widgets-FastTable.package/FTFunctionWithField.class/instance/accessing/showWidget.st R Morphic-Widgets-FastTable.package/FTNilFunction.class/instance/accessing/beExplicite.st A Morphic-Widgets-FastTable.package/FTNilFunction.class/instance/accessing/showWidget.st M Morphic-Widgets-FastTable.package/FTTableMorph.class/class/accessing/defaultBackgroundColor.st M Morphic-Widgets-FastTable.package/FTTableMorph.class/instance/accessing/explicitFunction.st A Polymorph-Widgets.package/ToolDockingBarMorph.class/instance/accessing/gradientRamp.st R Polymorph-Widgets.package/ToolDockingBarMorph.class/instance/as yet unclassified/gradientRamp.st R Polymorph-Widgets.package/ToolDockingBarMorph.class/instance/as yet unclassified/normalFillStyle.st R Polymorph-Widgets.package/ToolDockingBarMorph.class/instance/as yet unclassified/updateColor.st R Polymorph-Widgets.package/ToolDockingBarMorph.class/instance/as yet unclassified/wantsYellowButtonMenu.st A Polymorph-Widgets.package/ToolDockingBarMorph.class/instance/menu/wantsYellowButtonMenu.st A Polymorph-Widgets.package/ToolDockingBarMorph.class/instance/private - layout/updateColor.st A Polymorph-Widgets.package/ToolDockingBarMorph.class/instance/style/normalFillStyle.st A Polymorph-Widgets.package/UITheme.class/instance/accessing colors/listBackgroundColor.st A Polymorph-Widgets.package/UITheme.class/instance/border-styles/buttonBorderStyleFor_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60141.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60142.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60141.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60142.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60142 18704 button border should be themable https://pharo.fogbugz.com/f/cases/18704 http://files.pharo.org/image/60/60142.zip

1 0

Time now print24
by Eliot Miranda July 9, 2016

July 9, 2016

Hi All, how does one produce a nice timestamp, simply date and time as in 7/7/2016 09:19:38 Trivial, right? So Date today mmddyyyy, ' ', Time now print24 '7/7/2016 09:22:40.914' .914, ah, nanos. How useful. Let's get rid of them. No nanos: accessor so Date today mmddyyyy, ' ', (Time now nanos: 0) print24 => MNU but there's a seconds accessor, so Date today mmddyyyy, ' ', (Time now seconds: Time now seconds; print24) '7/7/2016 00:00:41 ?? So seconds: is private, and isn't the dual of Time seconds: Time seconds ^ self second Time second ^ self asDuration seconds Duration seconds "Answer the number of seconds the receiver represents." ^seconds rem: SecondsInMinute Looks broken to me. Personally I think print24 should not print sub seconds. cc'ing to Pharo because I want this timestamp to be the same in both dialects for a profiling tool we want to use in both dialects. _,,,^..^,,,_ best, Eliot

9 15

Spec Tutorial First chapter
by stepharo July 9, 2016

July 9, 2016

Hi Johan Fabry is writing a great tutorial (and this is cool to see all the material I gathered or wrote with him in the past) to take such great form. I attached the first chapter. I will post the chapter one by one once I review them (so far I have nothing to do - great feeling). Well done Johan! Stef

2 1

AthensCairoSurface not getting garbage collected
by J.F. Rick July 9, 2016

July 9, 2016

I'm using Athens rendering for my multi-touch applications on Pharo5. As part of that, I create a surface: surface := AthensCairoSurface extent: bounds extent asIntegerPoint. Though the object creating that surface is deleted, the surface sticks around. So, each time I run the app, I get another instance of AthensCairoSurface hanging around. That means all the forms stick around as well. So my image can quickly grow towards the 1GB size. Is there anything I can do about that? Can I manually get the surface to delete itself? Cheers, Jeff

4 11

Sound on Debian
by jannik laval July 8, 2016

July 8, 2016

Hi pharoers, I just tried sounds on phratch on Debian 8. It returns this message: sound_Start(default) soundStart: snd_add_pcm_handler: Fonction non implantÃ©e Is it a problem known ? Here is my configuration: Image ----- /usr/lib/Phratch/shared/Pharo4.0.image Pharo4.0 Latest update: #40626 Unnamed Virtual Machine --------------- /usr/lib/Phratch/bin/pharo NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 15 2014 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 15 2014 https://github.com/pharo-project/pharo-vm.git Commit: ed4a4f59208968a21d82fd2406f75c2c4de558b2 Date: 2014-05-15 18:23:04 +0200 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14826 Unix built on May 15 2014 18:29:39 Compiler: 4.6.3 VMMaker versionString https://github.com/pharo-project/pharo-vm.git Commit: ed4a4f59208968a21d82fd2406f75c2c4de558b2 Date: 2014-05-15 18:23:04 +0200 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14826 NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 15 2014 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 15 2014 Cheers, -- ~~Jannik Laval~~ Enseignant-chercheur Responsable PÃ©dagogique Licence Coordonnateur de Projet en SystÃ¨me d'Information IUT LumiÃ¨re, UniversitÃ© Lyon LumiÃ¨re laboratoire DISP http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

3 2

[Holidays] 14 days no updates: 14th to end of July
by Marcus Denker July 8, 2016

July 8, 2016

Hi, We just saw that everyone who can press the button for a final integration will be on Holidays from July 14 to the end of the month. This means there will be no update, but the issue tracker will stay open of course, so issues can be submitted, fixed and reviewedâ¦ they will just not end up the downloadable image for that 2 weeks. Marcus

5 4

Having comments for pragma?
by Alexandre Bergel July 8, 2016

July 8, 2016

Hi! A pragma may be very obscure. For example, I do: Pragma allInstances anyOne => <debuggerCompleteToSender> If I want to know more about this <debuggerCompleteToSender> is actually quite challenging. I see many methods having that pragma, but not idea what it is for. I see that Halt>>signalerContext and Process>>complete: that use that pragma somehow. But still, I have no idea when I should use that pragma in my method. What about having a way to comment pragma? Maybe something like -=-=-=-=-=-= Object subclass: #Pragma instanceVariableNames: 'method keyword arguments comment' -=-=-=-=-=-= And a simple way to annotate pragmas? Just an idea. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

11 41