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

Floats problem with SIXX between Pharo and GemStone

by Mariano Martinez Peck

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

Feb. 26, 2014

Re: [Pharo-dev] How to upload some version from the package-cache to a StHub project

by Gabriel Cotelli

Thank you Max, works like a charm! On Wed, Feb 26, 2014 at 6:20 PM, Max Leske <maxleske(a)gmail.com> wrote: > On 26.02.2014, at 22:03, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > > Hi, > > I have a whole package history in my local package cache and I want to > upload it to a new SmalltalkHub project. I've tried using the Monticello > browser but it insists in creating a new version of the package when I do > the "Save" to the new repository. > > > > Is there some option to do something like this? Or some script? I don't > want to loose the history. > > There's a "Copy" button in Monticello. > 1. open your repository / package cache > 2. select the package version you want to copy > 3. click the "Copy" button > 4. select target repository > > > > > Regards, > > Gabriel > > >

Feb. 26, 2014

Re: [Pharo-dev] How to upload some version from the package-cache to a StHub project

by Max Leske

On 26.02.2014, at 22:03, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > Hi, > I have a whole package history in my local package cache and I want to upload it to a new SmalltalkHub project. I've tried using the Monticello browser but it insists in creating a new version of the package when I do the "Save" to the new repository. > > Is there some option to do something like this? Or some script? I don't want to loose the history. Thereâs a âCopyâ button in Monticello. 1. open your repository / package cache 2. select the package version you want to copy 3. click the âCopyâ button 4. select target repository > > Regards, > Gabriel

Feb. 26, 2014

Re: [Pharo-dev] Pharo is cool

by Norbert Hartl

Am 26.02.2014 um 22:00 schrieb Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > > On Wed, Feb 26, 2014 at 5:50 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 26.02.2014 um 21:37 schrieb Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> >> >> >> On Wed, Feb 26, 2014 at 5:30 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> Am 26.02.2014 um 21:21 schrieb Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >>> >>> >>> >>> On Wed, Feb 26, 2014 at 3:53 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> Am 26.02.2014 um 14:38 schrieb Mariano Martinez Peck <marianopeck(a)gmail.com>: >>> >>>> Just be careful 2: "I switched one of my servers to dump to stack with fuel to disk if an exception occurs. " >>>> Once it happened to me the stack I was taking for serializing an error was too big. Too big because it even reached the UI. The UI has lots of sensible objects that change quite frequently. So my graph to serialize was big and the graph changed quite frequently. Result: Fuel throwing error because the graph to serialize changed while being serialized. Oh...exception? Fuel out exception! exception. Oh exception? ... >>>> >>> Good point, thanks! >>> >>>> So yeah..the fact that Fuel was throwing an error causes a loop so be careful of that as well. >>>> >>> If the serialization fails I just consider it an unrecoverable error and proceed. I will add a logging message for that case so I can at least so when something does not working while fueling out the stack. >>> >>> >>> Forgot... "just be careful 3": it may happen that you cannot correctly materialize (not serialization) the graph: a method has changed, a class is missing..whatever... So what I did in the fuel out of failure tests is to add to the serializer header all the info (as plain strings) that we normally have in the PharoDebug.log. This "header" will always be able to be materialized.... this way, I don't have the risk of not being able to materialize and hence loose info, and yet I don't need PharoDebug.log as well. If you don't do what I did, then you likely need also pharoDebug.log just in case... >>> >> That is unlikely to happen. My workflow is that every deployed image goes through the CI server. If a problem arises I download that same image from the CI server and load the stacks back into this. Everything is else is IMHO asking for trouble because contexts wonât map properly. >> >> >> >> +9999. That's the safest thing to do: use an image with the same "code" as the one that failed. >> >>> I recommend everyone interested in this topic to take a look to: #serializeTestFailureContext:toFileNamed: >>> >> That is what I am using because it does what I want to happen. It is only the selector that doesnât fit that well :) >> >> thanks a lot for this information Mariano. This is highly appreciated to get infos from someone that knows the stuff. >> >> >> No problem. >> >> Just be careful 4: do not trust 100% of the ability to debug a post morten. It should be considered "just as another extra tool to the PharoDebug.log". But debugging a stack with Fuel could even be different than the scenario that caused the error. Imagine class variables that changed value, files/socktets or something that depended on external resources, etc etc etc. What I mean is...the debug of a materialized fuel stack may not be the same as debugging the error at the exact time it was produced in the very same image it happened. But it is a great addition to PharoDebug.log for several use cases where it helps anyway. >> > Mariano, I admire your ability to offer all the precautions someone can think of. > > Because I've been there in this case ;) > > Maybe it is because it involves a tool you did on your own. Thanks for that. But for me the choice is easy. Having a fueled out stack is soooo much better than textual log files so that I need to come up with a lot of drawbacks until it wouldnât be worth using that. > > +9999. That's why I recommend everybody to use this approach taking the necessary precautions. It does not harm at all and likely help a lot. > > The side effects of having shared state is nothing that fuel introduces. If you get a debugger in your image and go back a few frames/contexts/time you cannot see the content of the objects at that time because they could have changed. > > indeed...that's why I said "in the exact time it was produced.." > > I would wish, too, we would have a debugger that snapshots all state and is able to âreallyâ go back. But at the moment we donât have it. So it is nothing fuel can solve. Fuel is just a wonderful tool that is capable of making stupid tasks less stupid to handle. > > > Completrly agree!!! nice quote btw! > > thanks again :) > > > No problem. You know that serializing/materializing a debugger was one of the coolest things I ever did. I was on my table, at Douai, thinking about examples to present Fuel in the ESUG Awards 2011. I remember my wife was sit in the couch and I said "Flor...what if I serialize the debugger!!!" . It took me 5 minutes to try it. I was sure it was going to fail...couldn't be so good for the first time. And surprisly....it worked out of the box. I couldn't believe it. I said...."ok...I have everything I need for ESUG" :) So yes, I very much like this feature! > > Also...it was the topic people outside the Smalltalk community commented the most about Fuel... of course...this is not just Fuel...it is Smalltalk that has contexts reified as objects and all it meta capabilities! > Just take the credit! Seaside was commented mostly about having continuations and not about building on top of smalltalk. Sure there is a powerful platform beneath. But building cool tools using that power is _really_ important, too. Norbert > Norbert > > >> Best, >> >> Norbert >> >>> Cheers, >>> >>> >>> thanks, >>> >>> Norbert >>> >>>> >>>> >>>> On Wed, Feb 26, 2014 at 10:28 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> >>>> Am 26.02.2014 um 14:19 schrieb Max Leske <maxleske(a)gmail.com>: >>>> >>>> > Cool! :) >>>> > >>>> > Just be careful: if youâre using a large model the stack can blow up your image with a low space warning / make it inresponsive (because the stack referenes your model and boom, pretty much all of your instances will becom serialized). >>>> > >>>> Yes, I know. But that would be a problem anyway. I think I have time. In the fuel files are 8 (!) contexts. :) >>>> >>>> Norbert >>>> >>>> > FYI weâre actively working on pruning of the serialization graph to solve this. >>>> > >>>> > Max >>>> > >>>> > >>>> > On 26.02.2014, at 14:01, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> > >>>> >> The best smalltalk/pharo moments you get if you try things you want to have just in order to see they are already there. >>>> >> >>>> >> Today FileBrowser. >>>> >> I switched one of my servers to dump to stack with fuel to disk if an exception occurs. Today I copied the files from the server to my local machine and opened a workspace starting to write an expression to open them. Then I thought it would be cool if I could use the file browser for it. So I opened it and navigated to the directory with the fuel filesâ¦et voilÃ â¦as soon as I clicked on a fuel file a button âmaterializeâ appeared which showed the stack from the server right away. >>>> >> >>>> >> Just brilliant! Well done! >>>> >> >>>> >> Norbert >>>> > >>>> > >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>> >>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com > > > > > -- > Mariano > http://marianopeck.wordpress.com

Feb. 26, 2014

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

by Max Leske

On 26.02.2014, at 21:40, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > I am playing with unicode characters: > > -=-=-=-=-=-=-=-=-=-=-=-= > Gofer new > url: 'http://smalltalkhub.com/mc/abergel/Sparkline/main'; > addPackage: 'Sparkline'; > load. > -=-=-=-=-=-=-=-=-=-=-=-= > > #( 1 2 3 4) spark => 'âââââ > #(-5 10 0) spark => 'âââ' > RxsNode withAllSubclasses spark: #numberOfMethods => 'âââââââââââââ > > <Screen Shot 2014-02-26 at 5.18.30 PM.png> > > I got the inspiration from https://github.com/holman/spark > > By the way, I would love to have a short tutorial about unicode characters at esug. +100 > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

Feb. 26, 2014

[ANN] Fuel 1.9.3

by Max Leske

Dear fellow Smalltalkers Mariano, Martin and myself are happy to announce Fuel version 1.9.3 which includes the follwing changes to 1.9 (1.9.1 and 1.9.2 were never officially announced): - (feature) the #fuelReplacement selector offers the ability to statically replace an object (e.g. with nil) during analysis. This can lead to significantly smaller graphs and improved speed when serializing large graphs - (feature) serialize the same graph that was analyzed instead of retrazing the graph during serialization. This prevents changes in the graph from happening between analysis and serialization - (change) store source when serializing CompiledMethod objects. Needed because Opal does not allow decompilation - (fix) migrate variables across hierarchy - (feature) Object>>serializeToFileNamed: shortcut for serializing arbitrary objects - (fix) better compression for LargeNegativeIntegers (https://pharo.fogbugz.com/f/cases/12052/Fuel-could-store-LargeNegativeInteg…) Pharo30 already includes most of these changes (integration request: https://pharo.fogbugz.com/f/cases/13000/Integrate-Fuel-1-9-3) This release runs with: - Pharo: 1.1.1, 1.1.2, 1.2, 1.2.2, 1.3, 1.4, 2.0, 3.0 - Squeak: 4.1, 4.2, 4.3, 4.4, 4.5 The documentation is not up to date yet but we will remedy that situatoin within the next couple of days (http://rmod.lille.inria.fr/web/pier/software/Fuel) If you encounter any bugs or have suggestions, please contact us on the Fuel mailing list (http://lists.gforge.inria.fr/cgi-bin/mailman/roster/pharo-fuel) or create a new issue in our bug tracker (https://code.google.com/p/fuel/) We want to thank everyone who contributed to this release (by keyboard or opinion) and also all of those people who actively use Fuel. Cheers, Max

Feb. 26, 2014

Re: [Pharo-dev] Pharo-Business: a new mailing-list

by Esteban A. Maringolo

I don't see the point of having another list, I don't see many business related topics going on in the dev or users lists. In fact they have moderate traffic (and could even converge). However, if the idea is to foster business talk, maybe a separate list is okay. I'm in. Esteban A. Maringolo 2014-02-26 17:45 GMT-03:00 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com>: > Make a list where the main point is about industry issues, share knowledge > and experience about general implications of pharo in a full project. > Recommend frameworks for specific domains. And then also soft knowledge, > know who is working with pharo in business to know to who ask for help in > case of over. > > What we will gain is as beginning, order in our knowledge database. Then > knowledge related with pharo but not from technical point, but business. > > Finally, the Pharo powered is about 'branding'. In both cases we are getting > knowledge scoped and ordered and almost free, more visible movement related. > > > > > > > 2014-02-26 21:27 GMT+01:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > >> Hi Stef, >> >> Can you explain what's the purpose of this list? >> >> I don't fully get it. What is to be discussed there? Market for Pharo? >> Derived businesses from pharo? (like pharocloud?). >> >> Thank you! >> >> >> Regards! >> Esteban A. Maringolo >> >> >> 2014-02-26 16:05 GMT-03:00 Pharo4Stef <pharo4Stef(a)free.fr>: >> > Dear Pharoers and Smalltalkers from all over the world >> > >> > We would really like to push business in our community and we believe >> > that it is important to create a community around business questions. >> > We created a new mailing-list >> > >> > >> > http://lists.pharo.org/mailman/listinfo/pharo-business_lists.pharo.org >> > >> > The idea is to identify >> > - potential market >> > - missing technical solutions that we could build together >> > - share technical assets from a business perspective (which >> > frameworks for what). >> > >> > We hope that you will like the idea and that more business can emerge! >> > >> >

Feb. 26, 2014

How to upload some version from the package-cache to a StHub project

by Gabriel Cotelli

Hi, I have a whole package history in my local package cache and I want to upload it to a new SmalltalkHub project. I've tried using the Monticello browser but it insists in creating a new version of the package when I do the "Save" to the new repository. Is there some option to do something like this? Or some script? I don't want to loose the history. Regards, Gabriel

Feb. 26, 2014

Re: [Pharo-dev] Pharo is cool

by Mariano Martinez Peck

On Wed, Feb 26, 2014 at 5:50 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 26.02.2014 um 21:37 schrieb Mariano Martinez Peck < > marianopeck(a)gmail.com>: > > > > > On Wed, Feb 26, 2014 at 5:30 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> Am 26.02.2014 um 21:21 schrieb Mariano Martinez Peck < >> marianopeck(a)gmail.com>: >> >> >> >> >> On Wed, Feb 26, 2014 at 3:53 PM, Norbert Hartl <norbert(a)hartl.name>wrote: >> >>> >>> Am 26.02.2014 um 14:38 schrieb Mariano Martinez Peck < >>> marianopeck(a)gmail.com>: >>> >>> Just be careful 2: "I switched one of my servers to dump to stack with >>> fuel to disk if an exception occurs. " >>> Once it happened to me the stack I was taking for serializing an error >>> was too big. Too big because it even reached the UI. The UI has lots of >>> sensible objects that change quite frequently. So my graph to serialize was >>> big and the graph changed quite frequently. Result: Fuel throwing error >>> because the graph to serialize changed while being serialized. >>> Oh...exception? Fuel out exception! exception. Oh exception? ... >>> >>> Good point, thanks! >>> >>> So yeah..the fact that Fuel was throwing an error causes a loop so be >>> careful of that as well. >>> >>> If the serialization fails I just consider it an unrecoverable error and >>> proceed. I will add a logging message for that case so I can at least so >>> when something does not working while fueling out the stack. >>> >>> >> Forgot... "just be careful 3": it may happen that you cannot correctly *materialize >> (not serialization)* the graph: a method has changed, a class is >> missing..whatever... So what I did in the fuel out of failure tests is to >> add to the serializer header all the info (as plain strings) that we >> normally have in the PharoDebug.log. This "header" will always be able to >> be materialized.... this way, I don't have the risk of not being able to >> materialize and hence loose info, and yet I don't need PharoDebug.log as >> well. If you don't do what I did, then you likely need also pharoDebug.log >> just in case... >> >> That is unlikely to happen. My workflow is that every deployed image goes >> through the CI server. If a problem arises I download that same image from >> the CI server and load the stacks back into this. Everything is else is >> IMHO asking for trouble because contexts won't map properly. >> >> > > +9999. That's the safest thing to do: use an image with the same "code" as > the one that failed. > > >> I recommend everyone interested in this topic to take a look to: >> #serializeTestFailureContext:toFileNamed: >> >> That is what I am using because it does what I want to happen. It is only >> the selector that doesn't fit that well :) >> >> thanks a lot for this information Mariano. This is highly appreciated to >> get infos from someone that knows the stuff. >> >> > No problem. > > Just be careful 4: do not trust 100% of the ability to debug a post > morten. It should be considered "just as another extra tool to the > PharoDebug.log". But debugging a stack with Fuel could even be different > than the scenario that caused the error. Imagine class variables that > changed value, files/socktets or something that depended on external > resources, etc etc etc. What I mean is...the debug of a materialized fuel > stack may not be the same as debugging the error at the exact time it was > produced in the very same image it happened. But it is a great addition to > PharoDebug.log for several use cases where it helps anyway. > > Mariano, I admire your ability to offer all the precautions someone can > think of. > Because I've been there in this case ;) > Maybe it is because it involves a tool you did on your own. Thanks for > that. But for me the choice is easy. Having a fueled out stack is soooo > much better than textual log files so that I need to come up with a lot of > drawbacks until it wouldn't be worth using that. > +9999. That's why I recommend everybody to use this approach taking the necessary precautions. It does not harm at all and likely help a lot. > The side effects of having shared state is nothing that fuel introduces. > If you get a debugger in your image and go back a few frames/contexts/time > you cannot see the content of the objects at that time because they could > have changed. > indeed...that's why I said "in the exact time it was produced.." > I would wish, too, we would have a debugger that snapshots all state and > is able to "really" go back. But at the moment we don't have it. So it is > nothing fuel can solve. Fuel is just a wonderful tool that is capable of > making stupid tasks less stupid to handle. > > Completrly agree!!! nice quote btw! > thanks again :) > > No problem. You know that serializing/materializing a debugger was one of the coolest things I ever did. I was on my table, at Douai, thinking about examples to present Fuel in the ESUG Awards 2011. I remember my wife was sit in the couch and I said "Flor...what if I serialize the debugger!!!" . It took me 5 minutes to try it. I was sure it was going to fail...couldn't be so good for the first time. And surprisly....it worked out of the box. I couldn't believe it. I said...."ok...I have everything I need for ESUG" :) So yes, I very much like this feature! Also...it was the topic people outside the Smalltalk community commented the most about Fuel... of course...this is not just Fuel...it is Smalltalk that has contexts reified as objects and all it meta capabilities! Norbert > > > > Best, > > >> Norbert >> >> Cheers, >> >> >> >>> thanks, >>> >>> Norbert >>> >>> >>> >>> On Wed, Feb 26, 2014 at 10:28 AM, Norbert Hartl <norbert(a)hartl.name>wrote: >>> >>>> >>>> Am 26.02.2014 um 14:19 schrieb Max Leske <maxleske(a)gmail.com>: >>>> >>>> > Cool! :) >>>> > >>>> > Just be careful: if you're using a large model the stack can blow up >>>> your image with a low space warning / make it inresponsive (because the >>>> stack referenes your model and boom, pretty much all of your instances will >>>> becom serialized). >>>> > >>>> Yes, I know. But that would be a problem anyway. I think I have time. >>>> In the fuel files are 8 (!) contexts. :) >>>> >>>> Norbert >>>> >>>> > FYI we're actively working on pruning of the serialization graph to >>>> solve this. >>>> > >>>> > Max >>>> > >>>> > >>>> > On 26.02.2014, at 14:01, Norbert Hartl <norbert(a)hartl.name> wrote: >>>> > >>>> >> The best smalltalk/pharo moments you get if you try things you want >>>> to have just in order to see they are already there. >>>> >> >>>> >> Today FileBrowser. >>>> >> I switched one of my servers to dump to stack with fuel to disk if >>>> an exception occurs. Today I copied the files from the server to my local >>>> machine and opened a workspace starting to write an expression to open >>>> them. Then I thought it would be cool if I could use the file browser for >>>> it. So I opened it and navigated to the directory with the fuel files...et >>>> voilÃ ...as soon as I clicked on a fuel file a button "materialize" appeared >>>> which showed the stack from the server right away. >>>> >> >>>> >> Just brilliant! Well done! >>>> >> >>>> >> Norbert >>>> > >>>> > >>>> >>>> >>>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > > -- Mariano http://marianopeck.wordpress.com

Feb. 26, 2014

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

by Norbert Hartl

Can you tell what these sparklines have to do with unicode? Btw. I would like to attend this unicode workshop :) Norbert Am 26.02.2014 um 21:40 schrieb Alexandre Bergel <alexandre.bergel(a)me.com>: > Hi! > > I am playing with unicode characters: > > -=-=-=-=-=-=-=-=-=-=-=-= > Gofer new > url: 'http://smalltalkhub.com/mc/abergel/Sparkline/main'; > addPackage: 'Sparkline'; > load. > -=-=-=-=-=-=-=-=-=-=-=-= > > #( 1 2 3 4) spark => 'âââââ > #(-5 10 0) spark => 'âââ' > RxsNode withAllSubclasses spark: #numberOfMethods => 'âââââââââââââ > > <Screen Shot 2014-02-26 at 5.18.30 PM.png> > > I got the inspiration from https://github.com/holman/spark > > By the way, I would love to have a short tutorial about unicode characters at esug. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

Feb. 26, 2014