- Pharo-users - lists.pharo.org

Re: [Pharo-users] Roassal question

by Werner Kassens

On 02/24/2015 01:51 AM, Pierre Chanson wrote: > by the way I am interested in how you did this Werner, > actually if it would be an easy and simple algorithm to fill a defined circle for example like a mesher. Hi Pierre, it is just a not-yet-ready half-baked implementation of interval-arithmetic, i intend to use for some constrained optimization problems; essentially only a proof of concept thing as it does not take floating point errors into account, iow it does not guarantee that the true result is included in the interval. i dont know what a mesher is, but if you want to fill a circle or so with something like eg pixels, there exist far more efficient solutions than using such an extremely stupid general algo. while i need multidimensional algos - the two-dimensional case is just a simple test-example -, for two-dimensional geometric problems of any kind there practically always exist simpler faster solutions than for the multidimensional version. werner

Feb. 24, 2015

Re: [Pharo-users] i feel dumb / Pharo3 > OrderedCollection >> do:

by Marcus Denker

> On 23 Feb 2015, at 21:15, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > > On Fri, Feb 20, 2015 at 5:48 AM, ClÃ©ment Bera <bera.clement(a)gmail.com <mailto:bera.clement@gmail.com>> wrote: > It depends on your OrderedCollection implementation. > > OrderedCollection has a variable size in memory. When instantiated, it has for example 10 slots, and if you have more than 10 objects, it needs to change its size to hold more slots. > > > I thought that was the case too, but I cannot find in code what you say. What Clement says is that *conceptionally* it has a variyng size. The current implementation uses an internal Array, as he describes: > > The current implementation relies on an indirection to an array, when the array overflows, the orderedCollection allocates a new bigger array and copy the slots from the existing array. There are some heuristics on array size to avoid having to grow the array too often. > > If you want the shallowCopy to work, you have to use the old implementation of OrderedCollection, which encodes in its field directly the values it holds. In this case however when the collection overflows you create a new orderedCollection so you need to use #become: to migrate references to the old orderedCollection to the new one. This used to be a bad idea because the become primitive was slow, but since we have Spur, it may be relevant to look at it again. This old implementation is more memory efficient too. And then, with the new fast #become:, we can go back the the old implementation and grow OrderedCollection using #become:, which would mean that we would not need two objects anymoreâ¦ Marcus

Feb. 24, 2015

Fwd: [ANN] PhyloclassTalk video presentations

by HernÃ¡n Morales Durand

Hello, Here I have new videos to show some of the features of PhyloclassTalk, developed in Pharo 3.0. PhyloclassTalk is a phylogenetics analysis platform which includes several modules to perform different workflows related with bioinformatics analysis. Video 1: GenBank Browser & PhyloclassTalk Classifier https://vimeo.com/120312074 Video 2: Blast Query Builder http://youtu.be/RCnnjRRRtM8 Greetings, HernÃ¡n

Feb. 24, 2015

Re: [Pharo-users] Roassal question

by Pierre Chanson

Ah yes exactly, I was not explaining it correctly as I am so used to it, sorry But it is good now, by the way I am interested in how you did this Werner, actually if it would be an easy and simple algorithm to fill a defined circle for example like a mesher. Cheers, Pierre > On 23 fÃ©vr. 2015, at 7:35 PM, Werner Kassens <wkassens(a)libello.com> wrote: > > ahh, yes understood, now things work as i want them to work! > thank you, > werner > >> On 02/23/2015 11:02 PM, Peter UhnÃ¡k wrote: >> >> that is exactly the problem i have <embarrassed grin>, RTBox does >> not understand #translateTo: or #translateBy: >> a:=RTBox new . >> a translateTo: 1(a)2.-->Error:__MessageNotUnderstood >> iow at which point exactly do i apply #translateTo: ? >> >> That's because RTBox is just a shape, and shape doesn't have position. >> You need to apply it to an element (RTElement). >

Feb. 24, 2015

Re: [Pharo-users] Roassal question

by Werner Kassens

ahh, yes understood, now things work as i want them to work! thank you, werner On 02/23/2015 11:02 PM, Peter UhnÃ¡k wrote: > > that is exactly the problem i have <embarrassed grin>, RTBox does > not understand #translateTo: or #translateBy: > a:=RTBox new . > a translateTo: 1(a)2.-->Error:__MessageNotUnderstood > iow at which point exactly do i apply #translateTo: ? > > That's because RTBox is just a shape, and shape doesn't have position. > You need to apply it to an element (RTElement). >

Feb. 23, 2015

Re: [Pharo-users] Roassal question

by Peter UhnÃ¡k

> > > that is exactly the problem i have <embarrassed grin>, RTBox does not > understand #translateTo: or #translateBy: > a:=RTBox new . > a translateTo: 1(a)2.-->Error:MessageNotUnderstood > iow at which point exactly do i apply #translateTo: ? That's because RTBox is just a shape, and shape doesn't have position. You need to apply it to an element (RTElement).

Feb. 23, 2015

Re: [Pharo-users] Roassal question

by Werner Kassens

On 02/23/2015 09:01 PM, Pierre CHANSON wrote: > Why don't you use an RTView and RTBox ? so you can use directly the > builder with view elements as objects ? > > I am not sure to understand your problem because to me you can always > create any desired boxes using RTBox new width:y; height:x then place > them with #translateTo: or #translateBy: Hi Pierre, that is exactly the problem i have <embarrassed grin>, RTBox does not understand #translateTo: or #translateBy: a:=RTBox new . a translateTo: 1(a)2.-->Error:MessageNotUnderstood iow at which point exactly do i apply #translateTo: ? werner

Feb. 23, 2015

Re: [Pharo-users] i feel dumb / Pharo3 > OrderedCollection >> do:

by Sven Van Caekenberghe

(class side) #new: (instance side) #growAtFirst #growAtLast #makeRoomAtFirst #makeRoomAtLast > On 23 Feb 2015, at 21:15, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > > On Fri, Feb 20, 2015 at 5:48 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > It depends on your OrderedCollection implementation. > > OrderedCollection has a variable size in memory. When instantiated, it has for example 10 slots, and if you have more than 10 objects, it needs to change its size to hold more slots. > > > I thought that was the case too, but I cannot find in code what you say. OrderedCollection nor it's parents are created with #variableSubclass... As you can see, "OrderedCollection isVariable" answers false. So where is that "variable size in memory" ? > > Thanks, > > The current implementation relies on an indirection to an array, when the array overflows, the orderedCollection allocates a new bigger array and copy the slots from the existing array. There are some heuristics on array size to avoid having to grow the array too often. > > If you want the shallowCopy to work, you have to use the old implementation of OrderedCollection, which encodes in its field directly the values it holds. In this case however when the collection overflows you create a new orderedCollection so you need to use #become: to migrate references to the old orderedCollection to the new one. This used to be a bad idea because the become primitive was slow, but since we have Spur, it may be relevant to look at it again. This old implementation is more memory efficient too. > > 2015-02-20 8:05 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > >> On 20 Feb 2015, at 06:23, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: >> >> >> I presumed shallowCopy for literal arrays / OrderedCollection should have been a true copy. Perhaps need to understand this.. >> > > OrderdCollection is not just one object, but it holds on to an Array that has itâs content. You copy the outside collection object, but share > the Array. > >> shallowCopy >> "Answer a copy of the receiver which shares the receiver's instance variables. It should never be overridden. I'm invoked from the copy template method. Subclasses that need to specialize the copy should specialize the postCopy hook method." >> ... >> <primitive: 148> >> class := self class. >> class isVariable >> ifTrue: >> [... newObject := class basicNew: index. ....] >> ifFalse: [newObject := class basicNew]. >> .. >> whileTrue: >> [newObject instVarAt: index put: (self instVarAt: index). >> ... >> ^ newObject >> >> On Wed, Feb 18, 2015 at 10:52 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >>> On 18 Feb 2015, at 18:13, Cameron Sanders via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >>> >>> >>> Date: 18 Feb 2015 18:12:33 CET >>> Subject: i feel dumb / Pharo3 > OrderedCollection >> do: >>> From: Cameron Sanders <camsanders(a)aol.com> >>> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >>> >>> >>> I must be making some silly error here that i cannot see clearly. Why does the following leave anything in the list 'a'? Run it in a workspace. With or without the shallowCopy, i am left with a list with half of the elements in it. Always half. >>> >>> This version of Pharo3 (21.0) was downloaded last week. I am running on a Mac. >>> >>> Thanks in advance. ... Maybe I just need more coffee. >>> -Cam >>> >>> | a | >>> a := { #a. #b. #c. #d. } asOrderedCollection. >>> a shallowCopy do: [ :item | (a includes: item) ifTrue: [ a remove: item ]]. >>> a size >>> >> >> shallowCopy is not enoughâ¦ OrderedCollection is made up of an internal array. >> >> #copy does the right thing, just copies the array: >> >> postCopy >> array := array copy >> >> and for Array, copy is a shallowCopy. >> >> Marcus >> >> >> >> > > > > > > -- > Mariano > http://marianopeck.wordpress.com

Feb. 23, 2015

Re: [Pharo-users] i feel dumb / Pharo3 > OrderedCollection >> do:

by Mariano Martinez Peck

On Fri, Feb 20, 2015 at 5:48 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > It depends on your OrderedCollection implementation. > > OrderedCollection has a variable size in memory. When instantiated, it has > for example 10 slots, and if you have more than 10 objects, it needs to > change its size to hold more slots. > > I thought that was the case too, but I cannot find in code what you say. OrderedCollection nor it's parents are created with #variableSubclass... As you can see, "OrderedCollection isVariable" answers false. So where is that "variable size in memory" ? Thanks, > The current implementation relies on an indirection to an array, when the > array overflows, the orderedCollection allocates a new bigger array and > copy the slots from the existing array. There are some heuristics on array > size to avoid having to grow the array too often. > > If you want the shallowCopy to work, you have to use the old > implementation of OrderedCollection, which encodes in its field directly > the values it holds. In this case however when the collection overflows you > create a new orderedCollection so you need to use #become: to migrate > references to the old orderedCollection to the new one. This used to be a > bad idea because the become primitive was slow, but since we have Spur, it > may be relevant to look at it again. This old implementation is more memory > efficient too. > > 2015-02-20 8:05 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > >> >> On 20 Feb 2015, at 06:23, S Krish <krishnamachari.sudhakar(a)gmail.com> >> wrote: >> >> >> I presumed shallowCopy for literal arrays / OrderedCollection should have >> been a true copy. Perhaps need to understand this.. >> >> >> OrderdCollection is not just one object, but it holds on to an Array that >> has itâs content. You copy the outside collection object, but share >> the Array. >> >> shallowCopy >> "Answer a copy of the receiver which shares the receiver's instance >> variables. It should never be overridden. I'm invoked from the copy >> template method. Subclasses that need to specialize the copy should >> specialize the postCopy hook method." >> ... >> <primitive: 148> >> class := self class. >> class isVariable >> ifTrue: >> [... newObject :=* class basicNew: index*. ....] >> ifFalse: [newObject := *class basicNew*]. >> .. >> whileTrue: >> [newObject instVarAt: index put: (self instVarAt: index). >> ... >> ^ newObject >> >> On Wed, Feb 18, 2015 at 10:52 PM, Marcus Denker <marcus.denker(a)inria.fr> >> wrote: >> >>> >>> On 18 Feb 2015, at 18:13, Cameron Sanders via Pharo-users < >>> pharo-users(a)lists.pharo.org> wrote: >>> >>> >>> *Date: *18 Feb 2015 18:12:33 CET >>> *Subject: **i feel dumb / Pharo3 > OrderedCollection >> do:* >>> *From: *Cameron Sanders <camsanders(a)aol.com> >>> *To: *Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >>> >>> >>> I must be making some silly error here that i cannot see clearly. Why >>> does the following leave anything in the list 'a'? Run it in a workspace. >>> With or without the shallowCopy, i am left with a list with half of the >>> elements in it. Always half. >>> >>> This version of Pharo3 (21.0) was downloaded last week. I am running on >>> a Mac. >>> >>> Thanks in advance. ... Maybe I just need more coffee. >>> -Cam >>> >>> | a | >>> a := { #a. #b. #c. #d. } asOrderedCollection. >>> a shallowCopy do: [ :item | (a includes: item) ifTrue: [ a remove: item >>> ]]. >>> a size >>> >>> >>> shallowCopy is not enoughâ¦ OrderedCollection is made up of an internal >>> array. >>> >>> #copy does the right thing, just copies the array: >>> >>> postCopy >>> array := array copy >>> >>> and for Array, copy is a shallowCopy. >>> >>> Marcus >>> >>> >>> >>> >> >> > -- Mariano http://marianopeck.wordpress.com

Feb. 23, 2015

Re: [Pharo-users] Roassal question

by Pierre CHANSON

Hi Werner, yes the builder is not made to work for Tracher canvas and Trachel shapes because in a builder we use methods that can be understood by an RTView and RTShape etc. Why don't you use an RTView and RTBox ? so you can use directly the builder with view elements as objects ? I am not sure to understand your problem because to me you can always create any desired boxes using RTBox new width:y; height:x then place them with #translateTo: or #translateBy: It would be much more interesting as you can then treat your objects elements in the view with their model contents and not only shapes in an TRCanvas. Pierre 2015-02-23 16:04 GMT-03:00 Werner Kassens <wkassens(a)libello.com>: > Hi Pierre, > perhaps i should show what i intend to do, i attached a screenshot and i > would like to have the axis' on the picture to the right. > > > On 02/23/2015 04:38 PM, Werner Kassens wrote: > >> Hi Pierre, >> i still have a problem since i can't place my RTBoxes at the position i >> need them to be. obviously they dont understand #translate: or >> #translateTo: like the things in TRCanvas. is there a way around this >> restriction? >> werner >> >> >> >>

Feb. 23, 2015