March 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] What's wrong whith this code?

by Bernat Romagosa

ouch, I added a . in the middle, sorry! elements := #('eins' 'zwei' 'drei' 'vier'). elements do: [ :element | (Delay forSeconds: 2) wait ] displayingProgress: [ :element | 'Working on', element asString ]. 2014-03-18 9:55 GMT+01:00 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com>: > Without having tried it, I think you're missing a #wait message in there: > > elements := #('eins' 'zwei' 'drei' 'vier'). > elements do: [ :element | (Delay forSeconds: 2) wait ]. > displayingProgress: [ :element | 'Working on', element asString ]. > > Cheers, > Bernat. > > > 2014-03-18 9:52 GMT+01:00 Friedrich Dominicus < > frido(a)q-software-solutions.de>: > > elements := #('eins' 'zwei' 'drei' 'vier'). >> elements do: [ :element | Delay forSeconds: 2. ] >> displayingProgress: [ :element | 'Working on', element asString ]. >> >> Shouldn't it just open a progress bar and iterate through the elements >> printing 'Working on...? >> >> Regards >> Friedrich >> >> > > > -- > Bernat Romagosa. > -- Bernat Romagosa.

March 18, 2014

Re: [Pharo-users] What's wrong whith this code?

by Bernat Romagosa

Without having tried it, I think you're missing a #wait message in there: elements := #('eins' 'zwei' 'drei' 'vier'). elements do: [ :element | (Delay forSeconds: 2) wait ]. displayingProgress: [ :element | 'Working on', element asString ]. Cheers, Bernat. 2014-03-18 9:52 GMT+01:00 Friedrich Dominicus <frido(a)q-software-solutions.de >: > elements := #('eins' 'zwei' 'drei' 'vier'). > elements do: [ :element | Delay forSeconds: 2. ] > displayingProgress: [ :element | 'Working on', element asString ]. > > Shouldn't it just open a progress bar and iterate through the elements > printing 'Working on...? > > Regards > Friedrich > > -- Bernat Romagosa.

March 18, 2014

What's wrong whith this code?

by Friedrich Dominicus

elements := #('eins' 'zwei' 'drei' 'vier'). elements do: [ :element | Delay forSeconds: 2. ] displayingProgress: [ :element | 'Working on', element asString ]. Shouldn't it just open a progress bar and iterate through the elements printing 'Working on...? Regards Friedrich

March 18, 2014

Re: [Pharo-users] NeoJSON and inheritance

by phil＠highoctane.be

NeoJSONMapper>>newObjectMappingFor: smalltalkClass | mapping | mapping := self mappings at: smalltalkClass ifAbsent: [ mapping := NeoJSONObjectMapping new. mapping subjectClass: smalltalkClass. self mappings at: smalltalkClass put: mapping. ]. ^ mapping works better ... Phil On Mon, Mar 17, 2014 at 5:40 PM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > The "super" thing doesn't work. > > I have spent a while tracing what was occuring with the custom mappings. > > If in a subclass I do: > > neoJsonMapping: aMapper > super neoJsonMapping: aMapper. > aMapper for: self do: [ :mapping | > mapping > mapProperty: 'startDate' getter: [ :filter | filter startDate ] setter: [ > :filter :value | filter startDate: value ]; > mapProperty: 'endDate' getter: [ :filter | filter endDate ] setter: [ > :filter :value | filter endDate: value ]. > ] > > and in the superclass: > > neoJsonMapping: aMapper > aMapper for: self do: [ :mapping | > mapping mapInstVar: #id to: 'id'. > ] > > (do not pay attention to mapInstVar or mapProperty, I was figuring out how > things worked). > > Thing is that the mapping goes fine up to one point. > > super neoJsonMapping: aMapper > > indeed puts the right 'id' mapping but then > > aMapper for:: self do: [ ... > > does > > for: smalltalkClass do: block > "Create and add a new standard object mapping for smalltalkClass. > The code in block should further customize the mapping." > | mapping | > mapping := self newObjectMappingFor: smalltalkClass. > block value: mapping. > ^ mapping > > > which in turn: > > newObjectMappingFor: smalltalkClass > | mapping | > mapping := NeoJSONObjectMapping new. > mapping subjectClass: smalltalkClass. > self mappings at: smalltalkClass put: mapping. > ^ mapping > > > > Argh: self mappings at: smalltalkClass put: mapping. > > Overwrites the existing contents. > > So, only the entries of the subclass are left. > > I guess that's a bug. > > I'd do: > > newObjectMappingFor: smalltalkClass > | mapping | > > mapping := self mappings at: smalltalkClass. > > mapping ifNil: [ > mapping := NeoJSONObjectMapping new. > mapping subjectClass: smalltalkClass. > self mappings at: smalltalkClass put: mapping. > ]. > > ^ mapping > > instead. > > Does this look right? > > mapping := self newObjectMappingFor: smalltalkClass. > > isn't then really intention revealing. Shouldn't we rename that to > objectMappingFor: smalltalkClass > > > Phil > > > > > > > On Fri, Sep 27, 2013 at 7:07 PM, Sven Van Caekenberghe <sven(a)stfx.eu>wrote: > >> Norbert, >> >> On 26 Sep 2013, at 11:32, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> > How is inheritance supposed to work in NeoJSON? I only figured it out >> by doing that manually: >> > >> > neoJsonMapping: aMapper >> > super neoJsonMapping: aMapper. >> > (aMapper mappingFor: self) >> > mapInstVar: #longitude; >> > mapInstVar: #latitude. >> > >> > Is there a better way to do? >> > >> > Norbert >> >> What you figured out yourself is the only inheritance that is available. >> >> The thing is, schema names (which can be plain Symbols or Class objects) >> are meant to be used for things like #ArrayOfPoints, >> #DictionaryWithUserValues which tell something about subtypes. I hurts to >> think of an inheritance for that ;-) >> >> Sven >> >> >

March 17, 2014

Re: [Pharo-users] NeoJSON and inheritance

by phil＠highoctane.be

The "super" thing doesn't work. I have spent a while tracing what was occuring with the custom mappings. If in a subclass I do: neoJsonMapping: aMapper super neoJsonMapping: aMapper. aMapper for: self do: [ :mapping | mapping mapProperty: 'startDate' getter: [ :filter | filter startDate ] setter: [ :filter :value | filter startDate: value ]; mapProperty: 'endDate' getter: [ :filter | filter endDate ] setter: [ :filter :value | filter endDate: value ]. ] and in the superclass: neoJsonMapping: aMapper aMapper for: self do: [ :mapping | mapping mapInstVar: #id to: 'id'. ] (do not pay attention to mapInstVar or mapProperty, I was figuring out how things worked). Thing is that the mapping goes fine up to one point. super neoJsonMapping: aMapper indeed puts the right 'id' mapping but then aMapper for:: self do: [ ... does for: smalltalkClass do: block "Create and add a new standard object mapping for smalltalkClass. The code in block should further customize the mapping." | mapping | mapping := self newObjectMappingFor: smalltalkClass. block value: mapping. ^ mapping which in turn: newObjectMappingFor: smalltalkClass | mapping | mapping := NeoJSONObjectMapping new. mapping subjectClass: smalltalkClass. self mappings at: smalltalkClass put: mapping. ^ mapping Argh: self mappings at: smalltalkClass put: mapping. Overwrites the existing contents. So, only the entries of the subclass are left. I guess that's a bug. I'd do: newObjectMappingFor: smalltalkClass | mapping | mapping := self mappings at: smalltalkClass. mapping ifNil: [ mapping := NeoJSONObjectMapping new. mapping subjectClass: smalltalkClass. self mappings at: smalltalkClass put: mapping. ]. ^ mapping instead. Does this look right? mapping := self newObjectMappingFor: smalltalkClass. isn't then really intention revealing. Shouldn't we rename that to objectMappingFor: smalltalkClass Phil On Fri, Sep 27, 2013 at 7:07 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Norbert, > > On 26 Sep 2013, at 11:32, Norbert Hartl <norbert(a)hartl.name> wrote: > > > How is inheritance supposed to work in NeoJSON? I only figured it out by > doing that manually: > > > > neoJsonMapping: aMapper > > super neoJsonMapping: aMapper. > > (aMapper mappingFor: self) > > mapInstVar: #longitude; > > mapInstVar: #latitude. > > > > Is there a better way to do? > > > > Norbert > > What you figured out yourself is the only inheritance that is available. > > The thing is, schema names (which can be plain Symbols or Class objects) > are meant to be used for things like #ArrayOfPoints, > #DictionaryWithUserValues which tell something about subtypes. I hurts to > think of an inheritance for that ;-) > > Sven > >

March 17, 2014

FileLibraries (files as methods)

by Esteban A. Maringolo

Well... I accidentally clicked in the InfoVis method #jitJs of InfoVisDevelopmentLibrary and it hung the whole image/vm (latest pharo 2 build). Without any chance of halting it. I don't know if it is something related with the parsing/syntax highlighting, but there should be a way to flag such methods and treat them differently. Regards! Esteban A. Maringolo

March 17, 2014

Re: [Pharo-users] Calculate angle between two vectors (probably @Igor :)

by btc＠openinworld.com

March 17, 2014

Re: [Pharo-users] [ANN] BabyMock 2

by Martin Dias

cool! On Wed, Mar 12, 2014 at 8:48 PM, Attila Magyar <m.magyar3(a)gmail.com> wrote: > Thanks for the nice words to everyone. > > > > -- > View this message in context: > http://forum.world.st/ANN-BabyMock-2-tp4748530p4748878.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

March 17, 2014

Re: [Pharo-users] Calculate angle between two vectors (probably @Igor :)

by Nicolai Hess

Another observation in Boids>>isInFieldOfVision: aBoid ... ownDirection := self velocity - self position. the own direction should be the same as the velocity. Consider a Boid at position 100@0 with velocity 100@0 would give ownDirection = 0@0. But of course, the steering direction is still 1@0. 2014-03-17 10:07 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de>: > This was of course wrong, I don't know what the > other method computes, but not the angle between two vectors. > > Now the question is, why do you think your method is wrong / the boids > behave wrong? > > > > > 2014-03-16 18:41 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de>: > > Rounding error? >> >> This may be the reason, igor's version is working with >> cos = (a dot b)^2 / (|ab|^2) >> while you are using >> cos = (a dot b) / |ab| >> >> >> >> >> >> 2014-03-16 17:01 GMT+01:00 MartinW <wm(a)fastmail.fm>: >> >> Hello, >>> i probably made some embarassing mistake, but as i cannot find it, i ask >>> you >>> to have a look at this method. >>> It should calculate the angle between two vectors. And vectors are >>> instances >>> of Point (perhaps here is already a misconception?). >>> It is used in my flocking simulation PharoBoids >>> (http://smalltalkhub.com/#!/~MartinWalk/Boids) >>> >>> Here is my version of the method: >>> >>> angleBetween: vector1 and: vector2 onError: aBlock >>> | cosinusOfAngle innerProductOfVectors productOfVectorsLengths| >>> innerProductOfVectors := (vector1 dotProduct: vector2). >>> productOfVectorsLengths := (vector1 r) * (vector2 r). >>> productOfVectorsLengths = 0 ifTrue: [ ^ aBlock value ]. >>> cosinusOfAngle := innerProductOfVectors / >>> productOfVectorsLengths. >>> ^ cosinusOfAngle arcCos >>> >>> But my Boids behave wrong when i use it. I found another implementation >>> of >>> the same problem by Igor Stasenko which works and looks like this: >>> >>> angleBetween: p1 and: p2 ifDegenerate: aBlock >>> " Calculate an angle (in radians) between two vectors. >>> Evaluate a block, in case if calculation not possible because one of the >>> vectors has zero length " >>> >>> | x1 y1 x2 y2 dot2 n2 | >>> x1 := p1 x. >>> y1 := p1 y. >>> x2 := p2 x. >>> y2 := p2 y. >>> >>> dot2 := x1 * x2 + (y1 * y2). >>> dot2 := dot2 * dot2. >>> >>> n2 := (x1*x1 + (y1*y1)) * (x2*x2 + (y2*y2)). >>> >>> n2 = 0 ifTrue: [ ^ aBlock value ]. >>> >>> ^ (dot2 / n2) arcCos >>> >>> Can anybody explain the problem of my method? M. >>> >>> >>> >>> -- >>> View this message in context: >>> http://forum.world.st/Calculate-angle-between-two-vectors-probably-Igor-tp4… >>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> >>> >> >

March 17, 2014

Re: [Pharo-users] Calculate angle between two vectors (probably @Igor :)

by Nicolai Hess

This was of course wrong, I don't know what the other method computes, but not the angle between two vectors. Now the question is, why do you think your method is wrong / the boids behave wrong? 2014-03-16 18:41 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de>: > Rounding error? > > This may be the reason, igor's version is working with > cos = (a dot b)^2 / (|ab|^2) > while you are using > cos = (a dot b) / |ab| > > > > > > 2014-03-16 17:01 GMT+01:00 MartinW <wm(a)fastmail.fm>: > > Hello, >> i probably made some embarassing mistake, but as i cannot find it, i ask >> you >> to have a look at this method. >> It should calculate the angle between two vectors. And vectors are >> instances >> of Point (perhaps here is already a misconception?). >> It is used in my flocking simulation PharoBoids >> (http://smalltalkhub.com/#!/~MartinWalk/Boids) >> >> Here is my version of the method: >> >> angleBetween: vector1 and: vector2 onError: aBlock >> | cosinusOfAngle innerProductOfVectors productOfVectorsLengths| >> innerProductOfVectors := (vector1 dotProduct: vector2). >> productOfVectorsLengths := (vector1 r) * (vector2 r). >> productOfVectorsLengths = 0 ifTrue: [ ^ aBlock value ]. >> cosinusOfAngle := innerProductOfVectors / productOfVectorsLengths. >> ^ cosinusOfAngle arcCos >> >> But my Boids behave wrong when i use it. I found another implementation of >> the same problem by Igor Stasenko which works and looks like this: >> >> angleBetween: p1 and: p2 ifDegenerate: aBlock >> " Calculate an angle (in radians) between two vectors. >> Evaluate a block, in case if calculation not possible because one of the >> vectors has zero length " >> >> | x1 y1 x2 y2 dot2 n2 | >> x1 := p1 x. >> y1 := p1 y. >> x2 := p2 x. >> y2 := p2 y. >> >> dot2 := x1 * x2 + (y1 * y2). >> dot2 := dot2 * dot2. >> >> n2 := (x1*x1 + (y1*y1)) * (x2*x2 + (y2*y2)). >> >> n2 = 0 ifTrue: [ ^ aBlock value ]. >> >> ^ (dot2 / n2) arcCos >> >> Can anybody explain the problem of my method? M. >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Calculate-angle-between-two-vectors-probably-Igor-tp4… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >

March 17, 2014