- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [fun] Sparkline in Pharo

by Sebastian Sastre

On Feb 27, 2014, at 9:05 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> canât see applicability now but thatâs kind of cute :D > > That is where you are wrong, they are really useful as a simple, inline way to visualise some data. > > http://en.wikipedia.org/wiki/Sparkline Hey Sven, are you sure is a logic problem ("being wrongâ) and not a perception problem (âseeing applicability nowâ) that you fixed with your reference? ;)

Feb. 27, 2014

Re: [Pharo-dev] FLMaterializer Materialization error

by Max Leske

On 27.02.2014, at 14:54, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > > On Thu, Feb 27, 2014 at 10:48 AM, Lorenzo Baracchi <baracchi.lorenzo(a)gmail.com> wrote: > Hi > > I was using FLMaterializer materializationFromFileNamed: filename to read fuel files. > Until yesterday everything was fine, but today I updated Pharo and received the error "'Materialization error. Unexpected stream version 19 where it should be 193." > > I guess that a new version of fuel cannot (simply) read old versions files. > > This is the "default" exception. But maybe....between 1.9 and 1.9.2 the file format didn't change. Max? I think 1.9 to 1.9.3 should work without problems. I canât think of any changes to the file format. > > Is there a way to know in which version of fuel a file was written and use that version to read it? > > In the exception message itself. "'Materialization error. Unexpected stream version 19 where it should be 193." > It says that in the current stream the version is 19 but the code now expects 193. So you should load Fuel 1.9 to materialize those files. > > Best, > > > > thanks > Lorenzo > > > > > -- > Mariano > http://marianopeck.wordpress.com

Feb. 27, 2014

Re: [Pharo-dev] FLMaterializer Materialization error

by Lorenzo Baracchi

On 2/27/14 2:54 PM, Mariano Martinez Peck wrote: > > > > On Thu, Feb 27, 2014 at 10:48 AM, Lorenzo Baracchi > <baracchi.lorenzo(a)gmail.com <mailto:baracchi.lorenzo@gmail.com>> wrote: > > Hi > > I was using FLMaterializer materializationFromFileNamed: filename > to read fuel files. > Until yesterday everything was fine, but today I updated Pharo and > received the error "'Materialization error. Unexpected stream > version 19 where it should be 193." > > I guess that a new version of fuel cannot (simply) read old > versions files. > > > This is the "default" exception. But maybe....between 1.9 and 1.9.2 > the file format didn't change. Max? > > Is there a way to know in which version of fuel a file was > written and use that version to read it? > > > In the exception message itself. "'Materialization error. Unexpected > stream version 19 where it should be 193." > It says that in the current stream the version is 19 but the code now > expects 193. So you should load Fuel 1.9 to materialize those files. so far so good. My goal was more about trying to avoid that error. Like asking to the FLMaterializer (or other) which version does a file have and then load the correspondent version of fuel. For example: version := FLMaterializer getVersionOfFileNamed: filename. (ConfigurationOfFuel project version: version ) load. materializerClass := Smalltalk at: #FLMaterializer. ^materializerClass materializationFromFileNamed: filename. > > Best, > > > thanks > Lorenzo > > > > > -- > Mariano > http://marianopeck.wordpress.com

Feb. 27, 2014

Re: [Pharo-dev] Floats problem with SIXX between Pharo and GemStone

by Masashi UMEZAWA

Hi Mariano, How about just defining: SmallDouble >> sixxType ^'Float' SmallDouble >> sixxWriteValue ^self asFloat I'm not using GemStone right now, so maybe my assumption would be inaccurate. But just a quick answer. Regards, 2014-02-27 6:38 GMT+09:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi guys, > > When I export SmallDoubles with SIXX in GemStone it generates something like > this: > > <sixx.object sixx.id="15" sixx.name="close" sixx.type="SmallDouble" >>1.0000000000000000E-02</sixx.object> > > This is because "0.01 asString" -> '1.0000000000000000E-02' > > Then I want to load this in Pharo. So first problem is that of course > SmallDouble doesn't exist. So I did: > > aSixxShapeChangeStream shapeChangers at: #SmallDouble put: Float. > But then, SIXX use Float >> readFrom: aStream > "Answer a new Float as described on the stream, aStream." ^(super readFrom: > aStream) asFloat > > > So, of course " Float readFrom: '1.0000000000000000E-02' " -> 1.0 > > So my 0.01 in gemstone become 1.0 in Pharo.... > > Am I doing something wrong or this is expected? What is the best workaround? > > In GemStone I could print the SmallDouble in the XML with a method like > > Float >> xmlRepresentation > ^ String streamContents: > [:strm | self printOn: strm base: 10] > > Is this the correct approach? If true, I guess I should define: > > Float >> sixxContentOn: aStream indent: level context: dictionary aStream > nextPutAll: self xmlRepresentation > > > Thoughts? > > Thanks in advance, > > -- > Mariano > http://marianopeck.wordpress.com -- [:masashi | ^umezawa]

Feb. 27, 2014

Pharo tutorials

by Goubier Thierry

Is that just me, or... The pharo tutorials are read-only in 30782, and therefore I can't open a menu and 'do it (d)' ? 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. 27, 2014

Re: [Pharo-dev] FLMaterializer Materialization error

by Mariano Martinez Peck

On Thu, Feb 27, 2014 at 10:48 AM, Lorenzo Baracchi < baracchi.lorenzo(a)gmail.com> wrote: > Hi > > I was using FLMaterializer materializationFromFileNamed: filename to read > fuel files. > Until yesterday everything was fine, but today I updated Pharo and > received the error "'Materialization error. Unexpected stream version 19 > where it should be 193." > > I guess that a new version of fuel cannot (simply) read old versions files. > This is the "default" exception. But maybe....between 1.9 and 1.9.2 the file format didn't change. Max? > Is there a way to know in which version of fuel a file was written and > use that version to read it? > In the exception message itself. "'Materialization error. Unexpected stream version 19 where it should be 193." It says that in the current stream the version is 19 but the code now expects 193. So you should load Fuel 1.9 to materialize those files. Best, > > thanks > Lorenzo > > -- Mariano http://marianopeck.wordpress.com

Feb. 27, 2014

FLMaterializer Materialization error

by Lorenzo Baracchi

Hi I was using FLMaterializer materializationFromFileNamed: filename to read fuel files. Until yesterday everything was fine, but today I updated Pharo and received the error "'Materialization error. Unexpected stream version 19 where it should be 193." I guess that a new version of fuel cannot (simply) read old versions files. Is there a way to know in which version of fuel a file was written and use that version to read it? thanks Lorenzo

Feb. 27, 2014

#new version #basicNew when materializing (SIXX/Fuel difference)

by Mariano Martinez Peck

Hi guys, I found this a bit strange and arguable. Upon materialization, for normal classes, Fuel uses #basicNew to instantiate objects and then sets its instances variables values getting them from the stream.... Today I found that SIXX sends #new first (*and hence #initialize is sent*) and after, if fails, it tries, #basicNew. This 2 approaches have different results. Which one would you expect? -- Mariano http://marianopeck.wordpress.com

Feb. 27, 2014

Re: [Pharo-dev] Authorize upArrow in binary symbols

by Jan Vrany

On 24/02/14 19:06, Marcus Denker wrote: > > Pharo uses (right now) RBParser as the main Parserâ¦ in Pharo4 we will remove the old Parser (subclass of Scanner ;-), > on the TODO is to check if PetitParser can be used instead (but there are many open questions related to e.g. error handling, > speedâ¦) This is interesting for me. I would not go for petitparser personally. My experience, speaking of performance and error reporting, not so great. I have one question: If you replace RBParser with green-field implementation, how would you deal with the rest of RB stuff? Refactorings, lint etc, which are all based of RBParser API? Best, Jan

Feb. 27, 2014

Re: [Pharo-dev] git and metacello

by Goubier Thierry

Hi Uko, It's at http://forum.world.st/ANN-GitFileTree-with-no-git-command-line-at-all-td474… In short, have a look at either ConfigurationOfAltBrowser or ConfigurationOfSmaCC (baseline20). Thierry Le 27/02/2014 13:25, Damien Cassou a Ã©crit : > On Thu, Feb 27, 2014 at 1:22 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> Sorry if I'm bothering you, but I wasn't able to find any workflow or so on with git. I've started to use file-tree, but for now on I don't understand how to make it work with metacello. Also is there some project like that built on jenkins, so I can set up similar job. > > > search for gitfiletree and Thierry Goubier on this mailing list. I > never used it though. > -- 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. 27, 2014