November 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Added shop page

by Christoph Wysseier

Am 28.11.13 11:51, schrieb phil(a)highoctane.be: > I am getting used to the CMSBox UI. And if you have an unsolvable problem once or feedback concerning the user interface we are always available for your comfort and support: mail(a)cmsbox.com Cheers, Chris -- Christoph Wysseier netstyle.ch GmbH & Cmsbox GmbH, CEO

Nov. 29, 2013

Re: [Pharo-dev] Coordinates problem with Athens and Morphic while coding Hyperion

by kilon alios

"why?" what Stephane ? Continue what ? I did not say I don't want to learn . On Fri, Nov 29, 2013 at 9:52 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > > Ok I have verified and indeed its not an Athens problem. My bad. The > position of the morph is reported at 5@30 and the not the correct 0@0. So > it looks like Morphic for some strange reason it offsets it. > > I knew about translateBy but I did not know about restoreAfter. so thank > you. > > I prefer my version of the code because it makes clearer what I am trying > to do. However ideally because I am drawing a box inside another box the > best way would be to follow your approach and scale the second box using > one shape instead of two I am currently doing. But thats the price I am > paying from not knowing exactly how to do this. > > Also trying to painstakingly find the correct transform and scale values > requires A LOT of testing . This is why I find a vector editor for Athens > and Pharo absolutely essential. No coding can beat designing via mouse. > > On the other hand I could use Inkscape and import the svg to Athens , > which what I am about to research. Designing all GUI elements by code is a > very bad idea, but no less a learning experience. > > I will most probably move to Roassal too. > > > why? > Just continue and learn. > > > As always thanks for the help. > > > On Thu, Nov 28, 2013 at 12:29 PM, Igor Stasenko <siguctua(a)gmail.com>wrote: > >> well, by default the athens canvas coordinate system matches morphic one.. >> but you know, it always hard to be sure, especially if you perform any >> local coordinate transformations before that morph has any chance to draw >> itself.. >> >> You can figure this out easily: draw something at 0@0 and see where it >> is. >> then draw something at morph's x@y position and see it too. >> >> btw, you know you don't have to create same paths over and over. >> you can easily put static parts out of regularly (and costly) evaluated >> code: >> >> shape := canvas cacheAt: self "morph" ifAbsentPut: [ >> aCanvas createPath: [:path | >> path relative. >> " no move-to here *** path moveTo: ((self position x )+5)@(self position >> y);" >> lineTo: 20@0; >> cwArcTo: 5@5 angle: 45; >> lineTo: 0@20; >> cwArcTo: (-5)@5 angle: 45; >> lineTo: (-20)@0; >> cwArcTo: (-5)@(-5) angle: 45; >> lineTo: 0@(-20); >> cwArcTo: 5@(-5) angle: 45. >> ]. >> ]. >> >> "and here we're using coordinate transform to translate origin point to >> given position, so it will be the starting point (0@0) of our shape" >> >> canvas pathTransform restoreAfter: [ >> canvas pathTransform translateBy:((self position x )+5)@(self position >> y). >> canvas drawShape: shape. >> ] >> >> by analogy you can cache all static pieces, just do something: >> >> shapes := canvas cacheAt: self ifAbsentPut: [ self >> constructStaticShapesOn: aCanvas ] >> >> where #constructStaticShapesOn: must answer an array of them. >> >> >> On 28 November 2013 11:12, kilon alios <kilon.alios(a)gmail.com> wrote: >> >>> wow you guys are fast at replying :) >>> >>> I did >>> >>> >>> self changeProportionalLayout. >>> editButton := HypEditButton new . >>> editButton position: 0@0. >>> self addMorph: editButton fullFrame: #(0 0 0 0 0 0 100 100). >>> >>> I am afraid Igor I still see no change with your code. >>> >>> I like to note here, that when I first created the editButton as morph , >>> it indeed placed it in correct place. A 0@0 placed it in top left >>> corner as expected. But I did overide its DrawOn: with an empty method and >>> used my own method to render it with Athens. So it looks like the problem >>> is Athens related and not Morphic related or maybe a disagreement between >>> Morphic and Athens. >>> >>> just for the record here is the code I use to render the HypEditButton >>> morph >>> >>> render:aCanvas >>> |shape1 shape2 shape3 editButtonColor | >>> shape1 := aCanvas createPath: [:path | >>> path relative . >>> path moveTo: ((self position x )+5)@(self position y); >>> lineTo: 20@0; >>> cwArcTo: 5@5 angle: 45; >>> lineTo: 0@20; >>> cwArcTo: (-5)@5 angle: 45; >>> lineTo: (-20)@0; >>> cwArcTo: (-5)@(-5) angle: 45; >>> lineTo: 0@(-20); >>> cwArcTo: 5@(-5) angle: 45. >>> ]. >>> shape2 := aCanvas createPath: [:path | >>> path relative . >>> path moveTo: ((self position x +7))@((self position y +3)); >>> lineTo: 18@0; >>> cwArcTo: 2@2 angle: 45; >>> lineTo: 0@20; >>> cwArcTo: (-2)@2 angle: 45; >>> lineTo: (-20)@0; >>> cwArcTo: (-2)@(-2) angle: 45; >>> lineTo: 0@(-20); >>> cwArcTo: 4@(-2) angle: 45. >>> ]. >>> shape3 := aCanvas createPath: [:path | >>> path relative . >>> path moveTo: ((self position x +15))@((self position y +10)); >>> cwArcTo: 5@5 angle: 90; >>> cwArcTo: (-5)@5 angle: 90; >>> cwArcTo: (-5)@(-5) angle: 90; >>> cwArcTo: 5@(-5) angle: 90. >>> ]. >>> ( editMode = true) ifTrue: [ editButtonColor := Color green] ifFalse: [ >>> editButtonColor := Color red ]. >>> (aCanvas setStrokePaint: editButtonColor) width: 1. >>> >>> aCanvas drawShape: shape1 . >>> aCanvas drawShape: shape2. >>> aCanvas setPaint: (editButtonColor alpha: 0.3 ). >>> aCanvas drawShape: shape3. >>> >>> >>> >>> >>> >>> >>> On Thu, Nov 28, 2013 at 12:03 PM, Igor Stasenko <siguctua(a)gmail.com>wrote: >>> >>>> >>>> >>>> >>>> On 28 November 2013 10:59, kilon alios <kilon.alios(a)gmail.com> wrote: >>>> >>>>> just tried it, I see no change >>>>> >>>>> try: >>>> self changeProportionalLayout >>>> >>>> editButton := HypEditButton new . >>>> self addMorph: editButton fullFrame: #(0 0 0 0 0 0 100 100). >>>> >>>>> >>>>> >>>>> On Thu, Nov 28, 2013 at 11:54 AM, Benjamin < >>>>> Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >>>>> >>>>>> Can you try to do something like >>>>>> >>>>>> self changeProportionalLayout >>>>>> before adding the morph ? >>>>>> >>>>>> Ben >>>>>> >>>>>> On 28 Nov 2013, at 10:51, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>>> >>>>>> So I have found some strange problems with my vector editor , >>>>>> Hyperion. >>>>>> >>>>>> Hyperion is a Morph openInWindow. Code can be found in the class side >>>>>> of Hyperion>>open. >>>>>> >>>>>> The coordinate system when detecting events (mouseOver, mouseUp and >>>>>> mouseDown events of the Hyperion instance) looks like it takes to account >>>>>> also beyond the morph as coordinates as a result events happening at the >>>>>> top right edge of the morph where Hyperion is rendered is 6@30( >>>>>> which is the size of the window's title bar plus its borders). Thats ok, I >>>>>> have taken these offsets to account when computing the position of the >>>>>> mouse. I guess it uses the global coordinated and not the local coordinates >>>>>> of the morph. >>>>>> >>>>>> I am adding a button to control the edit mode of a line, when in edit >>>>>> mode handles for line's control points are shown and those handles can be >>>>>> dragged around to control the shape of the line , when off edit mode, the >>>>>> line will be able to be drag around (not implemented yet). >>>>>> >>>>>> My problem is that when I add that button as morph to the existing >>>>>> morph of Hyperion in 0@0 , it actually appears in 0@30 in local >>>>>> coordinated of the Hyperion moprh which in global coordinates it 6@60( 0@0+ 6@30+ 0@30= 6@60). >>>>>> Why is that ? >>>>>> >>>>>> I have no clue why I am getting an offset of 0@30 in local >>>>>> coordinates of the Hyperion morph. >>>>>> >>>>>> here is the picture showing a) how it looks like b) the code that set >>>>>> the position c) transcript showing mouse coordinates when clicked in the >>>>>> top left corner of Hyperion morph >>>>>> Hyperion coordinates problem.JPG<https://docs.google.com/file/d/0B1L74rM985aqVTZleHlmb3RmbWs/edit?usp=drive_…> >>>>>> >>>>>> if anyone wants to try the code himself the repo is here >>>>>> >>>>>> http://www.smalltalkhub.com/#!/~kilon/Hyperion >>>>>> >>>>>> To sum up, to place that button on top left, I will have to position >>>>>> it 0@(-30) which for me makes no sense at all. >>>>>> >>>>>> Please note that everything is rendered with Athens. >>>>>> >>>>>> Maybe I have messed up the code myself somewhere but I have looked >>>>>> it again and again I cant find a problem with my code. >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko. >>>> >>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > >

Nov. 29, 2013

Re: [Pharo-dev] Coordinates problem with Athens and Morphic while coding Hyperion

by kilon alios

please note that the button for inserting an image is different to the button for attaching an image. Strange that it does not let you attach files, maybe if you zip, but in any case why dont you make smalltalkhub repo and publish the code there and give me the link to it ? On Fri, Nov 29, 2013 at 6:36 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 28 November 2013 22:49, kilon alios <kilon.alios(a)gmail.com> wrote: > >> well I could ask you to give me access to those files , that would be a >> good start ;) >> >> I am so new to this google drive thing >> >> hehe.. me too.. apperently it doesn't wants to just attach files, > and need multiple more clicks to enable weird sharing, like sending a copy > is not > good enough :) > > >> >> On Thu, Nov 28, 2013 at 10:08 PM, Igor Stasenko <siguctua(a)gmail.com>wrote: >> >>> >>> BezierMorph.st.gz<https://docs.google.com/file/d/0B7dd-52sqS20SW9JMUxZREh1ZkJEc1UwZkNiYy1jbnZ…> >>> >>> Morphic-BezierCurve.st<https://docs.google.com/file/d/0B7dd-52sqS20LW5XV2NwaFpPeEJudFFGZ3ZsZFBxZC0…> >>> >>> On 28 November 2013 16:54, kilon alios <kilon.alios(a)gmail.com> wrote: >>> >>>> absolutely, more code mean deeper understanding how to be more >>>> dangerous as a coder >>>> >>> >>> here it is.. it took me some effort to find it, buried under piles of >>> other things. >>> i don't know which one is latest/working, and don't ask me how it works >>> .. it was long ago i was young and sky was blue :) >>> >>> >>> On Thu, Nov 28, 2013 at 4:16 PM, Igor Stasenko <siguctua(a)gmail.com>wrote: >>> >>>> >>>> >>>> >>>> On 28 November 2013 13:52, kilon alios <kilon.alios(a)gmail.com> wrote: >>>> >>>>> thats all I got I am afraid right now. A simple editing of a straight >>>>> line, but I am learning athens, roassal, morphic so it takes time. Its my >>>>> first with everything and my very first project with pharo. I am not aiming >>>>> for something super sophisticated, bezier lines, gradients, bitmaps etc >>>>> simple stuff but I am having so much fun with this project I wont give up >>>>> until I have it finished. :) >>>>> >>>>> >>>> btw, if you want, i got somewhere code for Bezier curve editing (in >>>> morphic).. >>>> it is not fully working, but at least something you can look at: >>>> - if i remember you can add control points and move them around. >>>> >>>> >>>> >>>>> >>>>> On Thu, Nov 28, 2013 at 2:30 PM, Alexandre Bergel < >>>>> alexandre.bergel(a)me.com> wrote: >>>>> >>>>>> Do you have more screenshots of Hyperion? >>>>>> >>>>>> Alexandre >>>>>> -- >>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>>> Alexandre Bergel http://www.bergel.eu >>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>>> >>>>>> >>>>>> >>>>>> On Nov 28, 2013, at 7:49 AM, kilon alios <kilon.alios(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>> > Ok I have verified and indeed its not an Athens problem. My bad. >>>>>> The position of the morph is reported at 5@30 and the not the >>>>>> correct 0@0. So it looks like Morphic for some strange reason it >>>>>> offsets it. >>>>>> > >>>>>> > I knew about translateBy but I did not know about restoreAfter. so >>>>>> thank you. >>>>>> > >>>>>> > I prefer my version of the code because it makes clearer what I am >>>>>> trying to do. However ideally because I am drawing a box inside another box >>>>>> the best way would be to follow your approach and scale the second box >>>>>> using one shape instead of two I am currently doing. But thats the price I >>>>>> am paying from not knowing exactly how to do this. >>>>>> > >>>>>> > Also trying to painstakingly find the correct transform and scale >>>>>> values requires A LOT of testing . This is why I find a vector editor for >>>>>> Athens and Pharo absolutely essential. No coding can beat designing via >>>>>> mouse. >>>>>> > >>>>>> > On the other hand I could use Inkscape and import the svg to Athens >>>>>> , which what I am about to research. Designing all GUI elements by code is >>>>>> a very bad idea, but no less a learning experience. >>>>>> > >>>>>> > I will most probably move to Roassal too. >>>>>> > >>>>>> > As always thanks for the help. >>>>>> > >>>>>> > >>>>>> > On Thu, Nov 28, 2013 at 12:29 PM, Igor Stasenko <siguctua(a)gmail.com> >>>>>> wrote: >>>>>> > well, by default the athens canvas coordinate system matches >>>>>> morphic one.. >>>>>> > but you know, it always hard to be sure, especially if you perform >>>>>> any local coordinate transformations before that morph has any chance to >>>>>> draw itself.. >>>>>> > >>>>>> > You can figure this out easily: draw something at 0@0 and see >>>>>> where it is. >>>>>> > then draw something at morph's x@y position and see it too. >>>>>> > >>>>>> > btw, you know you don't have to create same paths over and over. >>>>>> > you can easily put static parts out of regularly (and costly) >>>>>> evaluated code: >>>>>> > >>>>>> > shape := canvas cacheAt: self "morph" ifAbsentPut: [ >>>>>> > aCanvas createPath: [:path | >>>>>> > path relative. >>>>>> > " no move-to here *** path moveTo: ((self position x )+5)@(self >>>>>> position y);" >>>>>> > lineTo: 20@0; >>>>>> > cwArcTo: 5@5 angle: 45; >>>>>> > lineTo: 0@20; >>>>>> > cwArcTo: (-5)@5 angle: 45; >>>>>> > lineTo: (-20)@0; >>>>>> > cwArcTo: (-5)@(-5) angle: 45; >>>>>> > lineTo: 0@(-20); >>>>>> > cwArcTo: 5@(-5) angle: 45. >>>>>> > ]. >>>>>> > ]. >>>>>> > >>>>>> > "and here we're using coordinate transform to translate origin >>>>>> point to >>>>>> > given position, so it will be the starting point (0@0) of our >>>>>> shape" >>>>>> > >>>>>> > canvas pathTransform restoreAfter: [ >>>>>> > canvas pathTransform translateBy:((self position x )+5)@(self >>>>>> position y). >>>>>> > canvas drawShape: shape. >>>>>> > ] >>>>>> > >>>>>> > by analogy you can cache all static pieces, just do something: >>>>>> > >>>>>> > shapes := canvas cacheAt: self ifAbsentPut: [ self >>>>>> constructStaticShapesOn: aCanvas ] >>>>>> > >>>>>> > where #constructStaticShapesOn: must answer an array of them. >>>>>> > >>>>>> > >>>>>> > On 28 November 2013 11:12, kilon alios <kilon.alios(a)gmail.com> >>>>>> wrote: >>>>>> > wow you guys are fast at replying :) >>>>>> > >>>>>> > I did >>>>>> > >>>>>> > >>>>>> > self changeProportionalLayout. >>>>>> > editButton := HypEditButton new . >>>>>> > editButton position: 0@0. >>>>>> > self addMorph: editButton fullFrame: #(0 0 0 0 0 0 100 100). >>>>>> > >>>>>> > I am afraid Igor I still see no change with your code. >>>>>> > >>>>>> > I like to note here, that when I first created the editButton as >>>>>> morph , it indeed placed it in correct place. A 0@0 placed it in top >>>>>> left corner as expected. But I did overide its DrawOn: with an empty >>>>>> method and used my own method to render it with Athens. So it looks like >>>>>> the problem is Athens related and not Morphic related or maybe a >>>>>> disagreement between Morphic and Athens. >>>>>> > >>>>>> > just for the record here is the code I use to render the >>>>>> HypEditButton morph >>>>>> > >>>>>> > render:aCanvas >>>>>> > |shape1 shape2 shape3 editButtonColor | >>>>>> > shape1 := aCanvas createPath: [:path | >>>>>> > path relative . >>>>>> > >>>>>> > path moveTo: ((self position x )+5)@(self position y); >>>>>> > lineTo: 20@0; >>>>>> > cwArcTo: 5@5 angle: 45; >>>>>> > lineTo: 0@20; >>>>>> > cwArcTo: (-5)@5 angle: 45; >>>>>> > lineTo: (-20)@0; >>>>>> > cwArcTo: (-5)@(-5) angle: 45; >>>>>> > lineTo: 0@(-20); >>>>>> > cwArcTo: 5@(-5) angle: 45. >>>>>> > ]. >>>>>> > >>>>>> > shape2 := aCanvas createPath: [:path | >>>>>> > path relative . >>>>>> > >>>>>> > path moveTo: ((self position x +7))@((self position y >>>>>> +3)); >>>>>> > lineTo: 18@0; >>>>>> > cwArcTo: 2@2 angle: 45; >>>>>> > lineTo: 0@20; >>>>>> > cwArcTo: (-2)@2 angle: 45; >>>>>> > lineTo: (-20)@0; >>>>>> > cwArcTo: (-2)@(-2) angle: 45; >>>>>> > lineTo: 0@(-20); >>>>>> > cwArcTo: 4@(-2) angle: 45. >>>>>> > ]. >>>>>> > shape3 := aCanvas createPath: [:path | >>>>>> > path relative . >>>>>> > >>>>>> > path moveTo: ((self position x +15))@((self position >>>>>> y +10)); >>>>>> > >>>>>> > cwArcTo: 5@5 angle: 90; >>>>>> > cwArcTo: (-5)@5 angle: 90; >>>>>> > cwArcTo: (-5)@(-5) angle: 90; >>>>>> > cwArcTo: 5@(-5) angle: 90. >>>>>> > >>>>>> > >>>>>> > ]. >>>>>> > >>>>>> > ( editMode = true) ifTrue: [ editButtonColor := Color green] >>>>>> ifFalse: [ editButtonColor := Color red ]. >>>>>> > (aCanvas setStrokePaint: editButtonColor) width: 1. >>>>>> > >>>>>> > aCanvas drawShape: shape1 . >>>>>> > aCanvas drawShape: shape2. >>>>>> > aCanvas setPaint: (editButtonColor alpha: 0.3 ). >>>>>> > aCanvas drawShape: shape3. >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > On Thu, Nov 28, 2013 at 12:03 PM, Igor Stasenko <siguctua(a)gmail.com> >>>>>> wrote: >>>>>> > >>>>>> > >>>>>> > >>>>>> > On 28 November 2013 10:59, kilon alios <kilon.alios(a)gmail.com> >>>>>> wrote: >>>>>> > just tried it, I see no change >>>>>> > >>>>>> > try: >>>>>> > self changeProportionalLayout >>>>>> > >>>>>> > editButton := HypEditButton new . >>>>>> > self addMorph: editButton fullFrame: #(0 0 0 0 0 0 100 100). >>>>>> > >>>>>> > >>>>>> > On Thu, Nov 28, 2013 at 11:54 AM, Benjamin < >>>>>> Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >>>>>> > Can you try to do something like >>>>>> > >>>>>> > self changeProportionalLayout >>>>>> > before adding the morph ? >>>>>> > >>>>>> > Ben >>>>>> > >>>>>> > On 28 Nov 2013, at 10:51, kilon alios <kilon.alios(a)gmail.com> >>>>>> wrote: >>>>>> > >>>>>> >> So I have found some strange problems with my vector editor , >>>>>> Hyperion. >>>>>> >> >>>>>> >> Hyperion is a Morph openInWindow. Code can be found in the class >>>>>> side of Hyperion>>open. >>>>>> >> >>>>>> >> The coordinate system when detecting events (mouseOver, mouseUp >>>>>> and mouseDown events of the Hyperion instance) looks like it takes to >>>>>> account also beyond the morph as coordinates as a result events happening >>>>>> at the top right edge of the morph where Hyperion is rendered is 6@30( >>>>>> which is the size of the window's title bar plus its borders). Thats ok, I >>>>>> have taken these offsets to account when computing the position of the >>>>>> mouse. I guess it uses the global coordinated and not the local coordinates >>>>>> of the morph. >>>>>> >> >>>>>> >> I am adding a button to control the edit mode of a line, when in >>>>>> edit mode handles for line's control points are shown and those handles can >>>>>> be dragged around to control the shape of the line , when off edit mode, >>>>>> the line will be able to be drag around (not implemented yet). >>>>>> >> >>>>>> >> My problem is that when I add that button as morph to the existing >>>>>> morph of Hyperion in 0@0 , it actually appears in 0@30 in local >>>>>> coordinated of the Hyperion moprh which in global coordinates it 6@60( 0@0+ 6@30+ 0@30= 6@60). >>>>>> Why is that ? >>>>>> >> >>>>>> >> I have no clue why I am getting an offset of 0@30 in local >>>>>> coordinates of the Hyperion morph. >>>>>> >> >>>>>> >> here is the picture showing a) how it looks like b) the code that >>>>>> set the position c) transcript showing mouse coordinates when clicked in >>>>>> the top left corner of Hyperion morph >>>>>> >> Hyperion coordinates problem.JPG >>>>>> >> >>>>>> >> if anyone wants to try the code himself the repo is here >>>>>> >> >>>>>> >> http://www.smalltalkhub.com/#!/~kilon/Hyperion >>>>>> >> >>>>>> >> To sum up, to place that button on top left, I will have to >>>>>> position it 0@(-30) which for me makes no sense at all. >>>>>> >> >>>>>> >> Please note that everything is rendered with Athens. >>>>>> >> >>>>>> >> Maybe I have messed up the code myself somewhere but I have looked >>>>>> it again and again I cant find a problem with my code. >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > -- >>>>>> > Best regards, >>>>>> > Igor Stasenko. >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > -- >>>>>> > Best regards, >>>>>> > Igor Stasenko. >>>>>> > >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko. >>>> >>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> > > > -- > Best regards, > Igor Stasenko. >

Nov. 29, 2013

Re: [Pharo-dev] Coordinates problem with Athens and Morphic while coding Hyperion

by StÃ©phane Ducasse

> Ok I have verified and indeed its not an Athens problem. My bad. The position of the morph is reported at 5@30 and the not the correct 0@0. So it looks like Morphic for some strange reason it offsets it. > > I knew about translateBy but I did not know about restoreAfter. so thank you. > > I prefer my version of the code because it makes clearer what I am trying to do. However ideally because I am drawing a box inside another box the best way would be to follow your approach and scale the second box using one shape instead of two I am currently doing. But thats the price I am paying from not knowing exactly how to do this. > > Also trying to painstakingly find the correct transform and scale values requires A LOT of testing . This is why I find a vector editor for Athens and Pharo absolutely essential. No coding can beat designing via mouse. > > On the other hand I could use Inkscape and import the svg to Athens , which what I am about to research. Designing all GUI elements by code is a very bad idea, but no less a learning experience. > > I will most probably move to Roassal too. why? Just continue and learn. > > As always thanks for the help. > > > On Thu, Nov 28, 2013 at 12:29 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > well, by default the athens canvas coordinate system matches morphic one.. > but you know, it always hard to be sure, especially if you perform any local coordinate transformations before that morph has any chance to draw itself.. > > You can figure this out easily: draw something at 0@0 and see where it is. > then draw something at morph's x@y position and see it too. > > btw, you know you don't have to create same paths over and over. > you can easily put static parts out of regularly (and costly) evaluated code: > > shape := canvas cacheAt: self "morph" ifAbsentPut: [ > aCanvas createPath: [:path | > path relative. > " no move-to here *** path moveTo: ((self position x )+5)@(self position y);" > lineTo: 20@0; > cwArcTo: 5@5 angle: 45; > lineTo: 0@20; > cwArcTo: (-5)@5 angle: 45; > lineTo: (-20)@0; > cwArcTo: (-5)@(-5) angle: 45; > lineTo: 0@(-20); > cwArcTo: 5@(-5) angle: 45. > ]. > ]. > > "and here we're using coordinate transform to translate origin point to > given position, so it will be the starting point (0@0) of our shape" > > canvas pathTransform restoreAfter: [ > canvas pathTransform translateBy:((self position x )+5)@(self position y). > canvas drawShape: shape. > ] > > by analogy you can cache all static pieces, just do something: > > shapes := canvas cacheAt: self ifAbsentPut: [ self constructStaticShapesOn: aCanvas ] > > where #constructStaticShapesOn: must answer an array of them. > > > On 28 November 2013 11:12, kilon alios <kilon.alios(a)gmail.com> wrote: > wow you guys are fast at replying :) > > I did > > > self changeProportionalLayout. > editButton := HypEditButton new . > editButton position: 0@0. > self addMorph: editButton fullFrame: #(0 0 0 0 0 0 100 100). > > I am afraid Igor I still see no change with your code. > > I like to note here, that when I first created the editButton as morph , it indeed placed it in correct place. A 0@0 placed it in top left corner as expected. But I did overide its DrawOn: with an empty method and used my own method to render it with Athens. So it looks like the problem is Athens related and not Morphic related or maybe a disagreement between Morphic and Athens. > > just for the record here is the code I use to render the HypEditButton morph > > render:aCanvas > |shape1 shape2 shape3 editButtonColor | > shape1 := aCanvas createPath: [:path | > path relative . > > path moveTo: ((self position x )+5)@(self position y); > lineTo: 20@0; > cwArcTo: 5@5 angle: 45; > lineTo: 0@20; > cwArcTo: (-5)@5 angle: 45; > lineTo: (-20)@0; > cwArcTo: (-5)@(-5) angle: 45; > lineTo: 0@(-20); > cwArcTo: 5@(-5) angle: 45. > ]. > > shape2 := aCanvas createPath: [:path | > path relative . > > path moveTo: ((self position x +7))@((self position y +3)); > lineTo: 18@0; > cwArcTo: 2@2 angle: 45; > lineTo: 0@20; > cwArcTo: (-2)@2 angle: 45; > lineTo: (-20)@0; > cwArcTo: (-2)@(-2) angle: 45; > lineTo: 0@(-20); > cwArcTo: 4@(-2) angle: 45. > ]. > shape3 := aCanvas createPath: [:path | > path relative . > > path moveTo: ((self position x +15))@((self position y +10)); > > cwArcTo: 5@5 angle: 90; > cwArcTo: (-5)@5 angle: 90; > cwArcTo: (-5)@(-5) angle: 90; > cwArcTo: 5@(-5) angle: 90. > > > ]. > > ( editMode = true) ifTrue: [ editButtonColor := Color green] ifFalse: [ editButtonColor := Color red ]. > (aCanvas setStrokePaint: editButtonColor) width: 1. > > aCanvas drawShape: shape1 . > aCanvas drawShape: shape2. > aCanvas setPaint: (editButtonColor alpha: 0.3 ). > aCanvas drawShape: shape3. > > > > > > > On Thu, Nov 28, 2013 at 12:03 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 28 November 2013 10:59, kilon alios <kilon.alios(a)gmail.com> wrote: > just tried it, I see no change > > try: > self changeProportionalLayout > > editButton := HypEditButton new . > self addMorph: editButton fullFrame: #(0 0 0 0 0 0 100 100). > > > On Thu, Nov 28, 2013 at 11:54 AM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > Can you try to do something like > > self changeProportionalLayout > before adding the morph ? > > Ben > > On 28 Nov 2013, at 10:51, kilon alios <kilon.alios(a)gmail.com> wrote: > >> So I have found some strange problems with my vector editor , Hyperion. >> >> Hyperion is a Morph openInWindow. Code can be found in the class side of Hyperion>>open. >> >> The coordinate system when detecting events (mouseOver, mouseUp and mouseDown events of the Hyperion instance) looks like it takes to account also beyond the morph as coordinates as a result events happening at the top right edge of the morph where Hyperion is rendered is 6@30( which is the size of the window's title bar plus its borders). Thats ok, I have taken these offsets to account when computing the position of the mouse. I guess it uses the global coordinated and not the local coordinates of the morph. >> >> I am adding a button to control the edit mode of a line, when in edit mode handles for line's control points are shown and those handles can be dragged around to control the shape of the line , when off edit mode, the line will be able to be drag around (not implemented yet). >> >> My problem is that when I add that button as morph to the existing morph of Hyperion in 0@0 , it actually appears in 0@30 in local coordinated of the Hyperion moprh which in global coordinates it 6@60 ( 0@0 + 6@30 + 0@30 = 6@60). Why is that ? >> >> I have no clue why I am getting an offset of 0@30 in local coordinates of the Hyperion morph. >> >> here is the picture showing a) how it looks like b) the code that set the position c) transcript showing mouse coordinates when clicked in the top left corner of Hyperion morph >> Hyperion coordinates problem.JPG >> >> if anyone wants to try the code himself the repo is here >> >> http://www.smalltalkhub.com/#!/~kilon/Hyperion >> >> To sum up, to place that button on top left, I will have to position it 0@(-30) which for me makes no sense at all. >> >> Please note that everything is rendered with Athens. >> >> Maybe I have messed up the code myself somewhere but I have looked it again and again I cant find a problem with my code. > > > > > > -- > Best regards, > Igor Stasenko. > > > > > -- > Best regards, > Igor Stasenko. >

Nov. 29, 2013

Re: [Pharo-dev] How to update Deep into Pharo Chapter

by StÃ©phane Ducasse

thanks! On Nov 28, 2013, at 10:27 PM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > I commited a new file (GOC-ExceptionExclusions.tex) in the Exceptions folder with a short subsection explaining the use. Feel free to review and improve it before inclusion in the main file. Probably the better insertion point is just after the ExceptionSet explanation. > > For testing the latex compilation I temporally put a "\input" in the main file (this isn't commited). > > Regards, Gabriel > > On Wed, Nov 27, 2013 at 3:45 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Yes > It would be good that you put some comments so that I can read it fast. > > Stef > On Nov 26, 2013, at 11:07 PM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > >> Thanks Damien, >> What is the expected workflow? >> I checkout the latex code, made the changes and then commit? >> >> >> On Tue, Nov 26, 2013 at 4:30 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: >> On Tue, Nov 26, 2013 at 6:34 PM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: >> > Done. Username: gcotelli >> >> >> done >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> >> > >

Nov. 29, 2013

Re: [Pharo-dev] Registering for issue tracker

by StÃ©phane Ducasse

> > > Ben thanks for making it much more obvious what to do, +1

Nov. 29, 2013

Re: [Pharo-dev] [Review needed] fix for Pharo2 "text highlighting incorrect"

by StÃ©phane Ducasse

>>> > > That's sad; I was seriously interested in seeing what Igor has managed to do. Normally there is an up to dat configuration in the Athens and TextModel repository. Now he is back working on it. But please have a look we need clients pushing igor. Igor is overwhelmed by questions :) But the more people will come the more they will ask questions and the more we will answer (or prepare docs to avoid to have to repeat all the time). Stef > > I'll spend some time on this issue and set the issues right for 2.0 and 3.0; many good things can be done with that highlighting working. > > 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 >

Nov. 29, 2013

Re: [Pharo-dev] Added shop page

by StÃ©phane Ducasse

On Nov 28, 2013, at 11:51 AM, phil(a)highoctane.be wrote: > Feel free. > > I am getting used to the CMSBox UI. Grace from the sky is falling on you. Excellent. Stef > > --- > Philippe Back > Dramatic Performance Improvements > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 > Mail:phil@highoctane.be | Web: http://philippeback.eu > Blog: http://philippeback.be | Twitter: @philippeback > Youtube: http://www.youtube.com/user/philippeback/videos > > High Octane SPRL > rue cour Boisacq 101 | 1301 Bierges | Belgium > > Pharo Consortium Member - http://consortium.pharo.org/ > Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com > Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller > > > > > On Thu, Nov 28, 2013 at 11:32 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Great, thanks a lot for taking care of the website, Phil, much appreciated. > Can we send more change suggestions/requests to you ? > > Sven > > On 28 Nov 2013, at 11:29, phil(a)highoctane.be wrote: > > > While I was at it, I added a shop page with the goodies. > > > > That way it will not stay in the mailing list depths forever. > > > > http://www.pharo-project.org/community/shop > > > > If that's a problem, I can remove the page. > > > > Phil > > > > > > >

Nov. 29, 2013

Re: [Pharo-dev] Added page on Zeroconf under downloads

by StÃ©phane Ducasse

Thanks for that!!! On Nov 28, 2013, at 11:41 AM, phil(a)highoctane.be wrote: > Zeroconf was just not that visible and that's what is the cool way to do Pharo IMHO > > http://www.pharo-project.org/pharo-download/zeroconf > > Phil

Nov. 29, 2013

Re: [Pharo-dev] Bug font windows

by StÃ©phane Ducasse

Thanks igor. What is strange is that it worked the first time. >> That is what I wanted to ask: How you built the image. Ok. I will try to open a Pharo image built on Mac on a Windows machine and see what happens. > > I gave to the guys a image of moose with the lucene case study loaded and it opened well the first time. > After saving on windows (often they use moose from their USB) then we could not reopen it. > > Stef > > According to stack trace, it uses in-image font.. so it should be not related to > local filesystem change.. and need to rescan fonts. > > Another thought, it could be that > newFaceFromExternalMemory:index: > fails somehow .. (maybe freetype plugin unavail?) > > > > -- > Best regards, > Igor Stasenko.

Nov. 29, 2013