September 2015 - Pharo-users

Pharo on rhel 6.5 and libasound.so.2

by Emilio Oca

Hi! I think I need some help here. I am trying to run a pharo seaside on a corporate RHEL 6.5 box. I downloaded this http://files.pharo.org/platform/Pharo4.0-centos.zip and deployed its contents on a directory. Gabe rights to execute and tried the first steps on this tutorial http://astares.blogspot.com.ar/search?q=headless but when running: ./pharo Pharo4.0.image save demo get this dependency error: pharo: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory ./pharo --vm-sound-null Pharo4.0.image save demo give the same error message ldd bin/pharo gives linux-gate.so.1 => (0x00c36000) libasound.so.2 => not found libm.so.6 => /lib/libm.so.6 (0x00628000) libdl.so.2 => /lib/libdl.so.2 (0x00a1e000) libpthread.so.0 => /lib/libpthread.so.0 (0x007f4000) libc.so.6 => /lib/libc.so.6 (0x0014f000) /lib/ld-linux.so.2 (0x007b1000) I am not going to have rights to install libasound.so.2 unless its part of a supported red hat enterprise package. What are my alternatives? Is libasound within a supported package? can I have a vm without this dependency? Thanks Emilio

Sept. 2, 2015

Re: [Pharo-users] Problems to serialise object when using FileSystem memory

by Juraj Kubelka

Hi, I think the main problem is in the StandardFileStream class>>#forceNewFileNamed:do: that converts aFileReference into a string and then it tests if the file exists. If this method is correct, then FLSerializer>>serialise:toFileNamed: should not use it. I have an impression that MemoryStore works well. I can write this: -=-=- | disk file | disk := FileSystem memory. file := disk workingDirectory / 'file.fuel'. file writeStreamDo: [ :aStream | aStream nextPutAll: 'hi' ]. [file contents = 'hi'] assert. -=-=- What do you think? Cheers, Juraj > On Sep 2, 2015, at 05:51, Stephan Eggermont <stephan(a)stack.nl> wrote: > > There is some code missing in the memory filesystem. > > MemoryFileSystemEntry has binaryReadStream and readStream, but only writeStreamDo: > > That means that MemoryStore openFileStream:writable doesn't work. > > Stephan > >

Sept. 2, 2015

Re: [Pharo-users] [Pharo-dev] Widget choice list

by Franck Warlouzet

Yes arrows up/down handling in fast table is not perfect. Esteban told me there is a way to have this kind of filtering direclty in the small rectangle but I did not take the time to see how. I like the search field but maybe someone prefers filtering directly in the list items area Franck > To: pharo-dev(a)lists.pharo.org > From: stephan(a)stack.nl > Date: Wed, 2 Sep 2015 16:35:39 +0200 > Subject: Re: [Pharo-dev] Widget choice list > CC: pharo-users(a)lists.pharo.org > > On 02-09-15 14:22, Franck Warlouzet wrote: > > Hi, > > > > Some of you showed interest in a widget as the one which pops up to add protocol in Nautilus, but using FastTable. We started to build such one, it allows to bind specific action on click on a item, to have icon for items, to filter items etc. Examples show how to use it. > > It is still a beginning so there is probably some strange points or improvements to do, but if it appears to be useful to replace some widgets we can enhance it. Or it can simply show you how easy it is to build a fast table with a more complex data source, which would already be a good point. > > > > You can find the code in this repo : > > > > MCHttpRepository > > location: 'http://www.smalltalkhub.com/mc/FranckW/WidgetChoiceList/main' > > user: '' > > password: '' > > > > Feel free to contact me if you have questions. > > Nice. I've fixed example4 > In the interaction between the search field and the table, you'll want > to change the focus behaviour. Starting to type should enter the text in > the search field while filtering the table and selecting the first > element that filters. Arrow up and down should move the selection of the > table. You'll also want a key combination to move up and down to the > next position where the strings start to differ again. > > I took a look at reacting to a keystroke in the text field, but there > is an announcement that is not exposed in the model. > > Stephan > > > >

Sept. 2, 2015

Widget choice list

by Franck Warlouzet

Hi, Some of you showed interest in a widget as the one which pops up to add protocol in Nautilus, but using FastTable. We started to build such one, it allows to bind specific action on click on a item, to have icon for items, to filter items etc. Examples show how to use it. It is still a beginning so there is probably some strange points or improvements to do, but if it appears to be useful to replace some widgets we can enhance it. Or it can simply show you how easy it is to build a fast table with a more complex data source, which would already be a good point. You can find the code in this repo : MCHttpRepository location: 'http://www.smalltalkhub.com/mc/FranckW/WidgetChoiceList/main' user: '' password: '' Feel free to contact me if you have questions. Cheers, Franck

Sept. 2, 2015

Re: [Pharo-users] Problems to serialise object when using FileSystem memory

by Stephan Eggermont

There is some code missing in the memory filesystem. MemoryFileSystemEntry has binaryReadStream and readStream, but only writeStreamDo: That means that MemoryStore openFileStream:writable doesn't work. Stephan

Sept. 2, 2015

Loops while inspecting data structures (Re: Pharo 4.0 -- Inspecting a recursive data structure is slow)

by H. Hirzel

On 8/30/15, Nicolai Hess <nicolaihess(a)web.de> wrote: > No this doesn't even fully work for the GTInspector (even not in Pharo > 5.0). > > It is the same issue Ben discovered when working with the pointer explorer. > (http://forum.world.st/Proposal-for-LiteralArray-class-tp4803015.html > and > http://forum.world.st/Fwd-14827-ProtoObject-pointersTo-failing-circular-ref… > ) > > The problem is that arrays printOn: > does not check for already visited objects > (squeak does this, but the implementation in pharo changed). > > For example, in Pharo 50 > > | myDict | > myDict := Dictionary new. > myDict at: #hello put: 'hello'. > myDict at: #recurHello put: myDict. > myDict inspect > > you can open the inspector, but selecting the first element in the "keys" > tab makes the image > unresponsive. The same happens if you select the #array instvar in the > "raw" tab. > > > > 2015-08-29 15:16 GMT+02:00 H. Hirzel <hannes.hirzel(a)gmail.com>: > >> As for me no need to hurry. I switch now to Pharo 5 build 50287 in the >> meantime. I will continue using that if I do not run into larger >> problems. >> >> --Hannes >> >> On 8/29/15, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> > >> >> On 29 Aug 2015, at 12:58, Andrei Chis <chisvasileandrei(a)gmail.com> >> wrote: >> >> >> >> Was there an issue/fix for this in Pharo 5? >> >> It might be worth backporting to Pharo 4. >> >> >> > Maybe one related to what is printed for the dictionary. >> > It used to be very slow for large collections >> > >> > >> https://pharo.fogbugz.com/f/cases/15311/The-display-string-for-collection-m… Below is a more illustrative and realistic example. The loop is indirect. Result: a) Pharo 4.0 image freezes b) Pharo 5-50287 it is fine (see screen shot) --Hannes | dict theEntry1 theEntry2 | dict := Dictionary new. theEntry1 := Dictionary new. dict at: 'house' put: theEntry1. theEntry1 at: 'fr' put: 'maison'. theEntry1 at: 'ge' put: 'Haus'. theEntry1 at: 'es' put: 'casa'. theEntry1 at: 'cf' put: 'building'. theEntry2 := Dictionary new. dict at: 'building' put: theEntry2. theEntry2 at: 'fr' put: 'bÃ¢timent'. theEntry2 at: 'de' put: 'GebÃ¤ude'. theEntry2 at: 'es' put: 'edificio'. "cross references" theEntry2 at: 'cf' put: theEntry1. theEntry1 at: 'cf' put: theEntry2. dict inspect

Sept. 2, 2015

Re: [Pharo-users] Problems to serialise object when using FileSystem memory

by Mariano Martinez Peck

I am quickly answering without testing (I can do that tomorrow otherwise). Did you see #serializeToByteArray: ? and FLInMemoryBasicSerializationTest? This is not filesytem, but still an in-memory stream. Also, did you make sure the in memory stream of FileStream is binary and not text? Try sending #binary or so... Let us know, On Tue, Sep 1, 2015 at 8:01 PM, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: > Hi, > > I am writing test case that uses following strategy: > > -=-=- > | memory file | > memory := FileSystem memory. > file := memory workingDirectory / 'file.fuel'. > FLSerializer serialize: {1. 2. 3} toFileNamed: file. > -=-=- > > But it does not work because in StandardFileStream class>> > #forceNewFileNamed: a "self fullName: fileName.â is called and it returns a > string. So it tries to create the file in the default real file system; not > in the memory file system. FLSerializer calls it in: > > -=-=- > serialize: anObject toFileNamed: aFilename > "Serialize the graph starting at the root object received and > answers the FLSerialization object" > StandardFileStream > forceNewFileNamed: aFilename > do: [ :aFileStream | > aFileStream binary. > self serialize: anObject on: aFileStream ] > -=-=- > > using a stream neither work: > > -=-=- > | disk file | > disk := FileSystem memory. > file := disk workingDirectory / 'file.fuel'. > file writeStreamDo: [ :aStream | > FLSerializer serialize: {1. 2. 3} on: aStream ]. > -=-=- > > It produces an improper indexable object. > > The only code that works is that one: > -=-=- > | file | > file := FileLocator workingDirectory / 'file.fuel'. > FLSerializer serialize: {1. 2. 3} toFileNamed: file. > -=-=- > > I think that using MemoryStore is a clean way to test code that stores > contents into a file. > How can I use FLSerializer and MemoryStore together? > > Thanks! > Juraj > -- Mariano http://marianopeck.wordpress.com

Sept. 2, 2015

Problems to serialise object when using FileSystem memory

by Juraj Kubelka

Hi, I am writing test case that uses following strategy: -=-=- | memory file | memory := FileSystem memory. file := memory workingDirectory / 'file.fuel'. FLSerializer serialize: {1. 2. 3} toFileNamed: file. -=-=- But it does not work because in StandardFileStream class>> #forceNewFileNamed: a "self fullName: fileName.â is called and it returns a string. So it tries to create the file in the default real file system; not in the memory file system. FLSerializer calls it in: -=-=- serialize: anObject toFileNamed: aFilename "Serialize the graph starting at the root object received and answers the FLSerialization object" StandardFileStream forceNewFileNamed: aFilename do: [ :aFileStream | aFileStream binary. self serialize: anObject on: aFileStream ] -=-=- using a stream neither work: -=-=- | disk file | disk := FileSystem memory. file := disk workingDirectory / 'file.fuel'. file writeStreamDo: [ :aStream | FLSerializer serialize: {1. 2. 3} on: aStream ]. -=-=- It produces an improper indexable object. The only code that works is that one: -=-=- | file | file := FileLocator workingDirectory / 'file.fuel'. FLSerializer serialize: {1. 2. 3} toFileNamed: file. -=-=- I think that using MemoryStore is a clean way to test code that stores contents into a file. How can I use FLSerializer and MemoryStore together? Thanks! Juraj

Sept. 1, 2015

Re: [Pharo-users] Becoming good at VM development

by stepharo

thanks esteban! I love CI. Le 1/9/15 08:37, Esteban Lorenzano a Ã©crit : > >> On 31 Aug 2015, at 21:41, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> >> Hi >> After the effort made by igor stasenko building the VM is a lot >> simpler than it used to. >> Did you try to compile the Pharo VM on your platform? >> Did you experience some problems? >> We should probably add a resource page to get started. I do not have >> the information but >> we can ask esteban. > > yesâ¦ PharoVM is built as described here: > > https://github.com/pharo-project/pharo-vm/blob/master/README.md > > if you follow those instructions, you will have no problems. > The process is running everyday so it *is* working. > Windows guys can have problems if they change mingw version, etc. They > shouldnât, but since this is over our control, I cannot assure you > anything. > Others problems that have emerged with time (in linux) is people > forgetting they need 32bit library versions to be able to buildâ¦ > > anywayâ¦ that should be enoughâ¦ for most people, once fulfilled > requirements, build VM is as easy as: > > 1) clone > 2) cd image; sh ./newImage.sh ; ./pharo generator.image eval > âPharoVMBuilder build" > 3) cd ../build ; sh build.sh > > cheers, > Esteban > >> >> Stef >>> Thanks to all for your responses. >>> I am carefully reading the material presented by you. Ideally I will >>> like to >>> compile the VM into Chrome's NaCL to run an image under Chrome OS. >>> But first >>> things first, as they say. I have to understand the Squeak/Pharo VM. >>> One question, is Mariano's blog still relevant? It seems to me that >>> Pharo VM >>> is not build that way anymore? >>> >>> ãããã¨ãã >>> >>> >>> >>> -- >>> View this message in context: >>> http://forum.world.st/Becoming-good-at-VM-development-tp4846536p4847217.html >>> Sent from the Pharo Smalltalk Users mailing list archive at >>> Nabble.com <http://Nabble.com>. >>> >>> >> >> >

Sept. 1, 2015

Re: [Pharo-users] [ANN] Pillar 1.0.0.

by Tudor Girba

Sounds great. I am really looking forward to using the PetitPillar parser. Cheers, Doru On Tue, Sep 1, 2015 at 3:45 PM, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: > Hello guys! > > I finished 5 months of internship into the RMoD team. I worked on Pillar > and I am glad to announce the version 1.0.0! > You can find an updated documentation of this version here : > > https://ci.inria.fr/pharo-contribution/view/Books/job/EnterprisePharoBook/l… > . > > We decided with Damien Cassou to use Semetic Versioning from now (see: > http://semver.org/) > > I will now explain the main changes I did on Pillar during my internship. > > For each new feature I added tests and documentation. > > I will begin with the changes of Pillar's structure > > - The configuration system is now manage by Cocoon > (http://www.smalltalkhub.com/#!/~PharoExtras/Cocoon) > -- We now use Magritte in Cocoon > > - I added Annotations : A syntax extension point > > - I added Transformers : A way to transform a document model before an > export (to add a section structure in HTML for example) > > - Some small refactoring. > -- Improvement of the template management > -- Improvement of the Pillar model parameters > > - Improvement of the document model > -- Now the figures and links are two different entity > > - I begun a PetitPillar (with PetitParser) in order to replace the old > parser too complicated. > > Now I will talk about new features for the users > > - Improvement of the usability of Pillar under Windows > > - Beamer and Deck.js exporters > > - Annotations : > -- To include a Pillar file into an other (${inputFile:path}$) (Example: > > https://github.com/SquareBracketAssociates/EnterprisePharo/blob/master/Ente… > ) > -- To create new slides in Beamer and Deck.js (${slide:My > Title|label=optional}$) > -- To create columns into a Pillar document (currently works in Beamer, > Deck.js and HTML) > -- â¦ > > - Transformers > -- You can now add a parameter "lineNumber=true" to a script and Pillar > will transform them to add the line numbers > -- You can now import a script from an other file (see the documentation > of the scripts) > -- â¦ > > - Improvement of the errors raised by Pillar > > - Addition of the inter-files links > > - Improvement of the title configuration for numbering > > - No need to make scripts anymore to use Pillar ! > -- You can used "defaultExporters" in your configuration to do multiple > export (see documentation) > -- Pillar generate a script for LaTeX compilation (only for Unix for now) > > - Possibility to export everything into a different folder (simpler to > clean after) > -- And possibility to copy some support files > > For the two previous point you can take example on Enterprise Pharo > (https://github.com/SquareBracketAssociates/EnterprisePharo) and Pharo > Mooc (https://github.com/SquareBracketAssociates/PharoMooc) > > This was a really cool internship :) > > If you have some questions do not hesitate! > > -- > Cyril > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 1, 2015