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

Re: [Pharo-dev] how does zip filesystem work?

by Goubier Thierry

Le 07/02/2014 09:30, Max Leske a Ã©crit : > > On 07.02.2014, at 06:38, Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>> wrote: > >> One more question: How do I read the contents of a file from within a zip? >> >> I try this on regular zip files created both on Mac and on Windows: >> zipFile := FileSystem disk workingDirectory / 'tmp.zip'. >> zip := (FileSystem zip: zipFile) open. >> (zip / 'sample.txt') >> readStreamDo: [ :s | s contents ] >> >> The problem is that I get an encoded stream. How do I decode it? > > No idea. I donât think that anybody used it after Lukas wrote it. So > itâs quite possible that itâs not even fully functional. But if it > isnât, then there are a lot of test cases missing (if there are any at > all) and we should start writing some right now. I use it in gitfiletree to load packages from a git repository. I access ZipArchive directly. It works. Never noticed it had a FileSystem interface. I use convertFromSystemString on the contents to correctly read UTF8 data. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 7, 2014

Re: [Pharo-dev] how does zip filesystem work?

by Max Leske

On 07.02.2014, at 06:38, Tudor Girba <tudor(a)tudorgirba.com> wrote: > One more question: How do I read the contents of a file from within a zip? > > I try this on regular zip files created both on Mac and on Windows: > zipFile := FileSystem disk workingDirectory / 'tmp.zip'. > zip := (FileSystem zip: zipFile) open. > (zip / 'sample.txt') > readStreamDo: [ :s | s contents ] > > The problem is that I get an encoded stream. How do I decode it? No idea. I donât think that anybody used it after Lukas wrote it. So itâs quite possible that itâs not even fully functional. But if it isnât, then there are a lot of test cases missing (if there are any at all) and we should start writing some right now. I can take a closer look on the weekend if youâre not already finished by then. > > Doru > > > > On Fri, Feb 7, 2014 at 6:34 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > And I found another problem. Even with the fix, it seems you cannot close the zip file. For example: > > zipFile := FileSystem disk workingDirectory / 'test.zip'. > zip := (FileSystem zip: zipFile) open. > zip / 'sample.txt' > writeStreamDo: [ :stream | stream nextPutAll: 'xyz' ]. > zip close > > I think the code should be correct. > > Cheers, > Doru > > > > > On Fri, Feb 7, 2014 at 5:49 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Ok. > > I added an initial slice with the quick fix solution: > https://pharo.fogbugz.com/f/cases/12826/Zip-FileSystem-does-not-work > > Could someone double check? > > Do we want to work more on it for Pharo 3.0? > > Cheers, > Doru > > > > > On Thu, Feb 6, 2014 at 4:37 PM, Max Leske <maxleske(a)gmail.com> wrote: > Yeah I knowâ¦ Itâs all just one big hack at the moment (Iâm not particularly proud of #binaryReadStream eitherâ¦). Again: letâs hope that XStreams will solve all our problems :) > > > On 06.02.2014, at 15:33, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > On 06 Feb 2014, at 15:30, Max Leske <maxleske(a)gmail.com> wrote: > > > >> No, not my bug :) > >> > >> The problem seems to be that WriteStream expects #size to be implemented but MemoryFileSystemFile only knows #fileSize. Apart from that I think it would work. > > > > But again, this is a problem (of the (G)Zip implementation) regarding the stream API. Certain stream, like network or serial streams, cannot respond to size in all conditions. > > > >> Add this to MemoryFileSystemFile (not as a final solution!): > >> > >> size > >> ^ bytes size > >> > >> Cheers, > >> Max > >> > >> On 06.02.2014, at 15:22, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> > >>> Thanks, Max. > >>> > >>> Doru > >>> > >>> > >>> On Thu, Feb 6, 2014 at 3:11 PM, Max Leske <maxleske(a)gmail.com> wrote: > >>> On 06.02.2014, at 15:07, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >>> > >>>> I am trying to get the ZipFileSystem to work, but I cannot quite manage it. > >>>> > >>>> I am doing this: > >>>> (FileSystem zip: > >>>> (FileSystem disk workingDirectory / 'sample.zip')) > >>>> open > >>>> > >>>> and I get an error. > >>>> > >>>> The error comes from the fact that the code uses readStreamDo: which does not work anymore with binary streams. I tried to use binaryReadStreamDo:, but that crashes in another place. > >>>> > >>>> I think this is a bug. Or am I doing something wrong? > >>> > >>> You shouldnât beâ¦ Iâll take a look later since that would be me who introduced the bug (probably). > >>> > >>>> > >>>> Cheers, > >>>> Doru > >>>> > >>>> -- > >>>> www.tudorgirba.com > >>>> > >>>> "Every thing has its own flow" > >>> > >>> > >>> > >>> > >>> -- > >>> www.tudorgirba.com > >>> > >>> "Every thing has its own flow" > >> > > > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Feb. 7, 2014

[Issues][Pharo3] Down to 25 issues!

by Marcus Denker

We are down to 25 issues tagged for Pharo3 that are âmust fixâ or higher!! https://pharo.fogbugz.com/f/filters/64/3-0-TODO

Feb. 7, 2014

[ann] presenter notes support for demos

by Tudor Girba

(repost to the correct mailing lists) Pharo workflow is best seen in action. However, I noticed that we do not have much support for demoing what we do. For example, if you do not record with sound, you want to add notes. I saw several videos with notes being added to the workspace. This looks clumsy. So, I gave it a short try, and built a little goodie that lets you simply type notes in the middle of the screen the audience in big fonts. Take a look below at a video describing a specific session with GTInspector: http://www.youtube.com/watch?v=XT081uQlqI4&list=UU5uZoiH-YS7CIQ-e-DCwMwA (from http://www.humane-assessment.com/blog/discover-contracts-by-visualizing-obj… ) To get it: Gofer new smalltalkhubUser: 'AlainPlantec' project: 'Rubric'; package: 'Rubric'; smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'GT-PresenterNote'; load. It's still at the beginning. Right now, it is mapped on Cmd+/. Actually, it really is tiny. You can obtain the equivalent by doing this in the workspace: KMRepository reset. KMRepository default setAsGlobalCategory: ( (KMCategory named: 'Presentation') addKeymapEntry: ( KMKeymap shortcut: $/ command action: [ RubEditingArea new beWrapped; width: World width / 3; updateTextWith: ''; takeKeyboardFocus; backgroundColor: Color paleYellow; cellInset: 50; onAnnouncement: MorphLostFocus do: [ :ann | ann morph delete ]; font: (LogicalFont familyName: 'Source Sans Pro' pointSize: 20); openCenteredInWorld. ]) ) We need to advertise Pharo, and our videos should look good. Let me know about what other similar needs you would like to have supported. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Feb. 7, 2014

[pharo-project/pharo-core]

by GitHub

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

Feb. 7, 2014

[pharo-project/pharo-core] 9eb242: 30748

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 9eb242f4996177388d26b4b3abfc9df9396818dc https://github.com/pharo-project/pharo-core/commit/9eb242f4996177388d26b4b3… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-02-06 (Thu, 06 Feb 2014) Changed paths: M Morphic-Base.package/MorphTreeListManager.class/instance/selection change/addAllToSelection_.st M Morphic-Base.package/MorphTreeListManager.class/instance/selection change/selectAll.st M Nautilus.package/PackageTreeNautilusUI.class/instance/displaying/buildFirstColumn_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/package filter/buildPackageSearch.st A RPackage-Core.package/RPackage.class/instance/private/importClass_inTag_.st M RPackage-Core.package/RPackage.class/instance/private/moveClass_fromPackage_toTag_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script401.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30748.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tests.package/ButtonModelTest.class/README.md M Spec-Tools.package/AbstractApiSetter.class/README.md R Spec-Tools.package/BlocEditor.class/README.md R Spec-Tools.package/BlocEditor.class/definition.st R Spec-Tools.package/BlocEditor.class/instance/accessing/block.st R Spec-Tools.package/BlocEditor.class/instance/accessing/block_.st R Spec-Tools.package/BlocEditor.class/instance/accessing/ok.st R Spec-Tools.package/BlocEditor.class/instance/accessing/post.st R Spec-Tools.package/BlocEditor.class/instance/accessing/pre.st R Spec-Tools.package/BlocEditor.class/instance/accessing/text.st R Spec-Tools.package/BlocEditor.class/instance/initialization/initialize.st R Spec-Tools.package/BlocEditor.class/instance/initialization/initializeWidgets.st R Spec-Tools.package/BlocEditor.class/instance/initialization/okAction.st R Spec-Tools.package/BlocEditor.class/instance/private/layout.st R Spec-Tools.package/BlocEditor.class/instance/protocol-events/whenBlockChangedDo_.st R Spec-Tools.package/BlocEditor.class/instance/protocol/buildWithSpec.st R Spec-Tools.package/BlocEditor.class/instance/protocol/buildWithSpec_.st R Spec-Tools.package/BlocEditor.class/instance/protocol/help_.st M Spec-Tools.package/BlockApiSetter.class/README.md M Spec-Tools.package/BlockApiSetter.class/instance/initialize/initializeWidgets.st A Spec-Tools.package/BlockEditor.class/README.md A Spec-Tools.package/BlockEditor.class/definition.st A Spec-Tools.package/BlockEditor.class/instance/accessing/block.st A Spec-Tools.package/BlockEditor.class/instance/accessing/block_.st A Spec-Tools.package/BlockEditor.class/instance/accessing/ok.st A Spec-Tools.package/BlockEditor.class/instance/accessing/post.st A Spec-Tools.package/BlockEditor.class/instance/accessing/pre.st A Spec-Tools.package/BlockEditor.class/instance/accessing/text.st A Spec-Tools.package/BlockEditor.class/instance/initialization/initialize.st A Spec-Tools.package/BlockEditor.class/instance/initialization/initializeWidgets.st A Spec-Tools.package/BlockEditor.class/instance/initialization/okAction.st A Spec-Tools.package/BlockEditor.class/instance/private/layout.st A Spec-Tools.package/BlockEditor.class/instance/protocol-events/whenBlockChangedDo_.st A Spec-Tools.package/BlockEditor.class/instance/protocol/buildWithSpec.st A Spec-Tools.package/BlockEditor.class/instance/protocol/buildWithSpec_.st A Spec-Tools.package/BlockEditor.class/instance/protocol/help_.st M Spec-Tools.package/BooleanApiSetter.class/README.md M Spec-Tools.package/ColorApiSetter.class/README.md M Spec-Tools.package/ColorEditor.class/README.md M Spec-Tools.package/IntegerApiSetter.class/README.md M Spec-Tools.package/IntegerEditor.class/README.md M Spec-Tools.package/STEditor.class/README.md M Spec-Tools.package/StApiSetter.class/README.md M Spec-Tools.package/StringApiSetter.class/README.md M Spec-Tools.package/SubwidgetItem.class/README.md M Spec-Tools.package/WidgetEditor.class/README.md M Spec-Tools.package/WidgetSetter.class/README.md Log Message: ----------- 30748 12789 RPackage>>#moveClass:fromPackage:toTag: Ignores Tag https://pharo.fogbugz.com/f/cases/12789 12827 Part II : Compiling a method often makes nautilus deselect the package https://pharo.fogbugz.com/f/cases/12827 12522 Package filter input capture all keyboard shortcuts https://pharo.fogbugz.com/f/cases/12522 12812 Class comments missing in package Spec-Tools and Spec-Tests and BlocEditor should be renamed to BlockEditor https://pharo.fogbugz.com/f/cases/12812 http://files.pharo.org/image/30/30748.zip

Feb. 7, 2014

Re: [Pharo-dev] What will change in Pharo with Spur the new Cog memory manager ...

by Tudor Girba

Hi, The post is important for advertisement. Thanks ClÃ©ment! The work is important for our future. Thanks Eliot! Doru On Fri, Feb 7, 2014 at 7:58 AM, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > Thanks Clement for the post and a big thank you to Eliot for Spur! > Can't wait for pharo 4 running on Spur-based Cog ;-) > > Luc > > 2014-02-07 ClÃ©ment Bera <bera.clement(a)gmail.com>: > > 2014-02-06 20:34 GMT+01:00 Sebastian Sastre <sebastian(a)flowingconcept.com> >> : >> >> Thanks for this information. >>> >>> Great post. >>> >>> So larger images would be no problem? let's say growing to 900MB? >>> >> >> I wouldn't say no problem, I would say that images up to 1 Gb should be >> usable and should behave much better than they used to due to the lack of >> full GC pauses. Now that's the theory we need to make it real and this >> summer we will see... >> >> >>> >>> >>> >>> >>> On Feb 6, 2014, at 12:48 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> >>> wrote: >>> >>> Hello pharoers, >>> >>> The new Cog memory manager, Spur, is simply *amazing*. I saw at FOSDEM >>> that some of you were interested in it, but unfortunately you were lacking >>> information about it. >>> >>> I wrote a one page article that sums up Spur's new features so every one >>> can know what will be better. There's no VM technical details here, it's >>> just about what will change for a regular pharo user. >>> >>> >>> http://clementbera.wordpress.com/2014/02/06/7-points-summary-of-the-spur-me… >>> >>> Let me know if you think I forgot yet another feature. >>> >>> If you have questions, I'll try to answer, but ask Eliot, he implemented >>> Spur so he can answer your questions much better than I can :-). >>> >>> Regards, >>> >>> ClÃ©ment >>> >>> >>> >> > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 7, 2014

Re: [Pharo-dev] What will change in Pharo with Spur the new Cog memory manager ...

by Luc Fabresse

Thanks Clement for the post and a big thank you to Eliot for Spur! Can't wait for pharo 4 running on Spur-based Cog ;-) Luc 2014-02-07 ClÃ©ment Bera <bera.clement(a)gmail.com>: > 2014-02-06 20:34 GMT+01:00 Sebastian Sastre <sebastian(a)flowingconcept.com> > : > > Thanks for this information. >> >> Great post. >> >> So larger images would be no problem? let's say growing to 900MB? >> > > I wouldn't say no problem, I would say that images up to 1 Gb should be > usable and should behave much better than they used to due to the lack of > full GC pauses. Now that's the theory we need to make it real and this > summer we will see... > > >> >> >> >> >> On Feb 6, 2014, at 12:48 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> >> Hello pharoers, >> >> The new Cog memory manager, Spur, is simply *amazing*. I saw at FOSDEM >> that some of you were interested in it, but unfortunately you were lacking >> information about it. >> >> I wrote a one page article that sums up Spur's new features so every one >> can know what will be better. There's no VM technical details here, it's >> just about what will change for a regular pharo user. >> >> >> http://clementbera.wordpress.com/2014/02/06/7-points-summary-of-the-spur-me… >> >> Let me know if you think I forgot yet another feature. >> >> If you have questions, I'll try to answer, but ask Eliot, he implemented >> Spur so he can answer your questions much better than I can :-). >> >> Regards, >> >> ClÃ©ment >> >> >> >

Feb. 7, 2014

Re: [Pharo-dev] how does zip filesystem work?

by Tudor Girba

One more question: How do I read the contents of a file from within a zip? I try this on regular zip files created both on Mac and on Windows: zipFile := FileSystem disk workingDirectory / 'tmp.zip'. zip := (FileSystem zip: zipFile) open. (zip / 'sample.txt') readStreamDo: [ :s | s contents ] The problem is that I get an encoded stream. How do I decode it? Doru On Fri, Feb 7, 2014 at 6:34 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > And I found another problem. Even with the fix, it seems you cannot close > the zip file. For example: > > zipFile := FileSystem disk workingDirectory / 'test.zip'. > zip := (FileSystem zip: zipFile) open. > zip / 'sample.txt' > writeStreamDo: [ :stream | stream nextPutAll: 'xyz' ]. > zip close > > I think the code should be correct. > > Cheers, > Doru > > > > > On Fri, Feb 7, 2014 at 5:49 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Ok. >> >> I added an initial slice with the quick fix solution: >> https://pharo.fogbugz.com/f/cases/12826/Zip-FileSystem-does-not-work >> >> Could someone double check? >> >> Do we want to work more on it for Pharo 3.0? >> >> Cheers, >> Doru >> >> >> >> >> On Thu, Feb 6, 2014 at 4:37 PM, Max Leske <maxleske(a)gmail.com> wrote: >> >>> Yeah I know... It's all just one big hack at the moment (I'm not >>> particularly proud of #binaryReadStream either...). Again: let's hope that >>> XStreams will solve all our problems :) >>> >>> >>> On 06.02.2014, at 15:33, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> > >>> > On 06 Feb 2014, at 15:30, Max Leske <maxleske(a)gmail.com> wrote: >>> > >>> >> No, not my bug :) >>> >> >>> >> The problem seems to be that WriteStream expects #size to be >>> implemented but MemoryFileSystemFile only knows #fileSize. Apart from that >>> I think it would work. >>> > >>> > But again, this is a problem (of the (G)Zip implementation) regarding >>> the stream API. Certain stream, like network or serial streams, cannot >>> respond to size in all conditions. >>> > >>> >> Add this to MemoryFileSystemFile (not as a final solution!): >>> >> >>> >> size >>> >> ^ bytes size >>> >> >>> >> Cheers, >>> >> Max >>> >> >>> >> On 06.02.2014, at 15:22, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >> >>> >>> Thanks, Max. >>> >>> >>> >>> Doru >>> >>> >>> >>> >>> >>> On Thu, Feb 6, 2014 at 3:11 PM, Max Leske <maxleske(a)gmail.com> >>> wrote: >>> >>> On 06.02.2014, at 15:07, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> >>> >>>> I am trying to get the ZipFileSystem to work, but I cannot quite >>> manage it. >>> >>>> >>> >>>> I am doing this: >>> >>>> (FileSystem zip: >>> >>>> (FileSystem disk workingDirectory / 'sample.zip')) >>> >>>> open >>> >>>> >>> >>>> and I get an error. >>> >>>> >>> >>>> The error comes from the fact that the code uses readStreamDo: >>> which does not work anymore with binary streams. I tried to use >>> binaryReadStreamDo:, but that crashes in another place. >>> >>>> >>> >>>> I think this is a bug. Or am I doing something wrong? >>> >>> >>> >>> You shouldn't be... I'll take a look later since that would be me who >>> introduced the bug (probably). >>> >>> >>> >>>> >>> >>>> Cheers, >>> >>>> Doru >>> >>>> >>> >>>> -- >>> >>>> www.tudorgirba.com >>> >>>> >>> >>>> "Every thing has its own flow" >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> www.tudorgirba.com >>> >>> >>> >>> "Every thing has its own flow" >>> >> >>> > >>> > >>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 7, 2014

Re: [Pharo-dev] how does zip filesystem work?

by Tudor Girba

And I found another problem. Even with the fix, it seems you cannot close the zip file. For example: zipFile := FileSystem disk workingDirectory / 'test.zip'. zip := (FileSystem zip: zipFile) open. zip / 'sample.txt' writeStreamDo: [ :stream | stream nextPutAll: 'xyz' ]. zip close I think the code should be correct. Cheers, Doru On Fri, Feb 7, 2014 at 5:49 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Ok. > > I added an initial slice with the quick fix solution: > https://pharo.fogbugz.com/f/cases/12826/Zip-FileSystem-does-not-work > > Could someone double check? > > Do we want to work more on it for Pharo 3.0? > > Cheers, > Doru > > > > > On Thu, Feb 6, 2014 at 4:37 PM, Max Leske <maxleske(a)gmail.com> wrote: > >> Yeah I know... It's all just one big hack at the moment (I'm not >> particularly proud of #binaryReadStream either...). Again: let's hope that >> XStreams will solve all our problems :) >> >> >> On 06.02.2014, at 15:33, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> > >> > On 06 Feb 2014, at 15:30, Max Leske <maxleske(a)gmail.com> wrote: >> > >> >> No, not my bug :) >> >> >> >> The problem seems to be that WriteStream expects #size to be >> implemented but MemoryFileSystemFile only knows #fileSize. Apart from that >> I think it would work. >> > >> > But again, this is a problem (of the (G)Zip implementation) regarding >> the stream API. Certain stream, like network or serial streams, cannot >> respond to size in all conditions. >> > >> >> Add this to MemoryFileSystemFile (not as a final solution!): >> >> >> >> size >> >> ^ bytes size >> >> >> >> Cheers, >> >> Max >> >> >> >> On 06.02.2014, at 15:22, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> >> >>> Thanks, Max. >> >>> >> >>> Doru >> >>> >> >>> >> >>> On Thu, Feb 6, 2014 at 3:11 PM, Max Leske <maxleske(a)gmail.com> wrote: >> >>> On 06.02.2014, at 15:07, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> >> >>>> I am trying to get the ZipFileSystem to work, but I cannot quite >> manage it. >> >>>> >> >>>> I am doing this: >> >>>> (FileSystem zip: >> >>>> (FileSystem disk workingDirectory / 'sample.zip')) >> >>>> open >> >>>> >> >>>> and I get an error. >> >>>> >> >>>> The error comes from the fact that the code uses readStreamDo: which >> does not work anymore with binary streams. I tried to use >> binaryReadStreamDo:, but that crashes in another place. >> >>>> >> >>>> I think this is a bug. Or am I doing something wrong? >> >>> >> >>> You shouldn't be... I'll take a look later since that would be me who >> introduced the bug (probably). >> >>> >> >>>> >> >>>> Cheers, >> >>>> Doru >> >>>> >> >>>> -- >> >>>> www.tudorgirba.com >> >>>> >> >>>> "Every thing has its own flow" >> >>> >> >>> >> >>> >> >>> >> >>> -- >> >>> www.tudorgirba.com >> >>> >> >>> "Every thing has its own flow" >> >> >> > >> > >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 7, 2014