- Pharo-users - lists.pharo.org

Possible bug with Voyage-Mongo date

by raphonic

I'm running Pharo 3.0 beta with Voyage-Mongo. When I save a DateAndTime instance in the database, it's saved in Mongodb as the previous day. This occurs for all dates. This could be an issue with either the Mongo driver or Voyage-Mongo, i'm not exactly sure which since both their tests pass. -- View this message in context: http://forum.world.st/Possible-bug-with-Voyage-Mongo-date-tp4735597.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Jan. 10, 2014

Re: [Pharo-users] [Pharo-dev] Pharo3 build is green!

by Luc Fabresse

Congrats ;-) #Luc 2014/1/10 Tudor Girba <tudor(a)tudorgirba.com> > Thank you! > > Doru > > > On Thu, Jan 9, 2014 at 9:02 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > >> >> FInallyâ¦ a lot of work went into this, and I thank everyone who helped! >> >> We are now running 34134 (together) for the 3 architectures... >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Jan. 10, 2014

Re: [Pharo-users] [Pharo-dev] Pharo3 build is green!

by Tudor Girba

Thank you! Doru On Thu, Jan 9, 2014 at 9:02 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > FInallyâ¦ a lot of work went into this, and I thank everyone who helped! > > We are now running 34134 (together) for the 3 architectures... > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 10, 2014

Pharo3 build is green!

by Marcus Denker

FInallyâ¦ a lot of work went into this, and I thank everyone who helped! We are now running 34134 (together) for the 3 architectures...

Jan. 9, 2014

Re: [Pharo-users] [Pharo-dev] [Moose-dev] Re: Feature for request for GraphET?

by Tudor Girba

Hi Daniel, Good work! But, there is still something I do not quite understand. Take a look at the produced image. Why is it that in the first red bar appears behind the gray one, and the rest appear in front of the corresponding gray bars? Related to the GapFraction: Could you describe what makes it such an expensive issue to compute the width of the bar with a bit of scaling? I am asking because this particular diagram does not work without it. Cheers, Doru [image: Inline image 1] On Wed, Jan 8, 2014 at 6:50 PM, Daniel Aviv Notario < daniel_avivnotario(a)hotmail.com> wrote: > So, attending to the request Doru made, here's something similar to the > example he provided in EyeSee... All the methods were already implemented > but most of them didn't have a clear accesor to modify them. > > So, if you just load the last version of GraphET and do this: > > > builder := GETDiagramBuilder new. > grouped := { #item1->{10 . 12 . 11 . 14 } . #item2-> { 1 . 1 . 20 > } > . #item3->{ 1 . 1 . 1 . 1 . 1} }. > diag := (GETVerticalBarDiagram new) > modelLabels: [:each | each key ]; > y: [:each | each value size]; > yAxisLabel: 'Count'; > valueAxis; > height:200; > spacing:20; > yAxisOnRight; > color: Color veryLightGray; > axisColor: Color veryLightGray; > models: grouped; > yourself. > diag2 := (GETVerticalBarDiagram new) > y: [:each | each value sum]; > regularAxis; > height: 200; > spacing:20; > yAxisLabel: 'Sum'; > color: (Color red); > axisColor: (Color red); > models: grouped; > yourself. > (builder unionDiagram) > add: diag; > add: diag2. > builder open > > > You'll see it's very similar. There's two things I couldn't replicate so > far, one of them is the rotating labels, as Roassal can't rotate labels > yet, and the second one was the GapFraction, as axis in GraphET need some > work yet, so implementing that kind of thing would be hard. I think I'll > dedicate to a proper axis in the next couple of weeks. > > Cheers :)! > > > > >>> ---------- Forwarded message ---------- > > > >>> From: Tudor Girba <tudor(a)tudorgirba.com> > > > >>> Date: Sat, Jan 4, 2014 at 10:39 PM > > > >>> Subject: Re: [Pharo-dev] Feature for request for GraphET? > > > >>> To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > >>> > > > >>> > > > >>> Here is one thing I would want: a correspondent Graph-ET > > > >>> functionality to make something like this EyeSee script work as > > > >>> in > > > >>> the first attached picture. > > > >>> > > > >>> renderer := ESDiagramRenderer new. > > > >>> grouped := { #item1->{10 . 12 . 11 . 14 } . #item2-> { 1 . 1 . 20 > > > >>> } > > > >>> . #item3->{ 1 . 1 . 1 . 1 . 1} }. > > > >>> diag := (ESVerticalBarDiagram new) > > > >>> identifier: [:each | each key ]; > > > >>> y: [:each | each value size]; > > > >>> yAxisLabel: 'Count'; > > > >>> valueAxis; > > > >>> rightYAxis; > > > >>> defaultColor: Color veryVeryLightGray; > > > >>> axisColor: Color veryVeryLightGray; > > > >>> models: grouped; > > > >>> rotatedLabels: true; > > > >>> yourself. > > > >>> diag2 := (ESVerticalBarDiagram new) > > > >>> y: [:each | each value sum]; > > > >>> regularAxis; > > > >>> yAxisLabel: 'Sum'; > > > >>> gapFraction: 2 / 3; > > > >>> defaultColor: (Color red); > > > >>> axisColor: (Color red); > > > >>> models: grouped; > > > >>> yourself. > > > >>> (renderer compositeDiagram) > > > >>> add: diag; > > > >>> add: diag2. > > > >>> renderer open > > > >>> > > > >>> > > > >>> <Screenshot 2014-01-04 22.31.57.png> > > > >>> > > > >>> > > > >>> The best I could produce with Graph-ET is this (I commented out > > > >>> the > > > >>> message to which I did not find a correspondent): > > > >>> > > > >>> builder := GETDiagramBuilder new. > > > >>> grouped := { #item1->{10 . 12 . 11 . 14 } . #item2-> { 1 . 1 . 20 > > > >>> } > > > >>> . #item3->{ 1 . 1 . 1 . 1 . 1} }. > > > >>> diag := (GETVerticalBarDiagram new) > > > >>> "identifier: [:each | each key ];" > > > >>> y: [:each | each value size]; > > > >>> yAxisLabel: 'Count'; > > > >>> valueAxisLine; > > > >>> "rightYAxis;" > > > >>> color: Color veryLightGray; > > > >>> "axisColor: Color veryLightGray;" > > > >>> models: grouped; > > > >>> "rotatedLabels: true;" > > > >>> yourself. > > > >>> diag2 := (GETVerticalBarDiagram new) > > > >>> y: [:each | each value sum]; > > > >>> regularAxis; > > > >>> yAxisLabel: 'Sum'; > > > >>> "gapFraction: 2 / 3;" > > > >>> color: (Color red); > > > >>> "axisColor: (Color red);" > > > >>> models: grouped; > > > >>> yourself. > > > >>> (builder compositeDiagram) > > > >>> add: diag; > > > >>> add: diag2. > > > >>> builder open > > > >>> > > > >>> <Screenshot 2014-01-04 22.36.40.png> > > > >>> > > > >>> Cheers, > > > >>> Doru > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 8, 2014

Re: [Pharo-users] World to Morph Local Co-ordinates

by Sean P. DeNigris

Markus Schlager-2 wrote > http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2013-September… Interesting thread - thanks! ----- Cheers, Sean -- View this message in context: http://forum.world.st/World-to-Morph-Local-Co-ordinates-tp4735247p4735265.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Jan. 8, 2014

Re: [Pharo-users] World to Morph Local Co-ordinates

by Markus Schlager

Maybe this thread gives some pointer: http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2013-September… I tend to call this a bug - at least it's not the expected behavior of embedded morphs IMO. Markus

Jan. 8, 2014

Re: [Pharo-users] World to Morph Local Co-ordinates

by Igor Stasenko

On 8 January 2014 19:54, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I'm sure this must be addressed somewhere, but searching the archives for > "morph local point" didn't produce anything helpfulâ¦ > > I have a PasteUpMorph that represents a scaled down world. So when a morph > sets its position to e.g. 0@0, I want to set it to the topLeft corner of > the > pasteUp. I can use align:with:, but I thought some of the following might > have some usefulness, but all returned 0@0. None of them have tests... > screen globalPointToLocal: (0@0). > screen localPointToGlobal: (0@0). > screen pointInWorld: (0@0). > screen referencePositionInWorld: (0@0). > screen point: 0@0 from: screen. > > perhaps if you pick some morph, which (sub)chile of some TransformMorph, you will be able to see the difference. but for screen/world zero is always zero, because there is no difference between local and global , since its transformation is identity :) > Is there an easy built-in way to convert points from World to the bounds of > another (assume rectangular) morph? > > piece of cake, since all morphs use same, global coordinates, simple subtraction works: localpoint := globalpoint - morph topLeft > Thanks. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/World-to-Morph-Local-Co-ordinates-tp4735247.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- Best regards, Igor Stasenko.

Jan. 8, 2014

World to Morph Local Co-ordinates

by Sean P. DeNigris

I'm sure this must be addressed somewhere, but searching the archives for "morph local point" didn't produce anything helpfulâ¦ I have a PasteUpMorph that represents a scaled down world. So when a morph sets its position to e.g. 0@0, I want to set it to the topLeft corner of the pasteUp. I can use align:with:, but I thought some of the following might have some usefulness, but all returned 0@0. None of them have tests... screen globalPointToLocal: (0@0). screen localPointToGlobal: (0@0). screen pointInWorld: (0@0). screen referencePositionInWorld: (0@0). screen point: 0@0 from: screen. Is there an easy built-in way to convert points from World to the bounds of another (assume rectangular) morph? Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/World-to-Morph-Local-Co-ordinates-tp4735247.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Jan. 8, 2014

Re: [Pharo-users] [Moose-dev] Re: [Pharo-dev] Feature for request for GraphET?

by Daniel Aviv Notario

So, attending to the request Doru made, here's something similar to the example he provided in EyeSee... All the methods were already implemented but most of them didn't have a clear accesor to modify them. So, if you just load the last version of GraphET and do this: builder := GETDiagramBuilder new. grouped := { #item1->{10 . 12 . 11 . 14 } . #item2-> { 1 . 1 . 20 } . #item3->{ 1 . 1 . 1 . 1 . 1} }. diag := (GETVerticalBarDiagram new) modelLabels: [:each | each key ]; y: [:each | each value size]; yAxisLabel: 'Count'; valueAxis;height:200;spacing:20; yAxisOnRight; color: Color veryLightGray; axisColor: Color veryLightGray; models: grouped; yourself. diag2 := (GETVerticalBarDiagram new) y: [:each | each value sum]; regularAxis;height: 200;spacing:20;yAxisLabel: 'Sum';color: (Color red); axisColor: (Color red); models: grouped; yourself. (builder unionDiagram) add: diag;add: diag2. builder open You'll see it's very similar. There's two things I couldn't replicate so far, one of them is the rotating labels, as Roassal can't rotate labels yet, and the second one was the GapFraction, as axis in GraphET need some work yet, so implementing that kind of thing would be hard. I think I'll dedicate to a proper axis in the next couple of weeks. Cheers :)! > > >>> ---------- Forwarded message ---------- > > >>> From: Tudor Girba <tudor(a)tudorgirba.com> > > >>> Date: Sat, Jan 4, 2014 at 10:39 PM > > >>> Subject: Re: [Pharo-dev] Feature for request for GraphET? > > >>> To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > >>> > > >>> > > >>> Here is one thing I would want: a correspondent Graph-ET > > >>> functionality to make something like this EyeSee script work as > > >>> in > > >>> the first attached picture. > > >>> > > >>> renderer := ESDiagramRenderer new. > > >>> grouped := { #item1->{10 . 12 . 11 . 14 } . #item2-> { 1 . 1 . 20 > > >>> } > > >>> . #item3->{ 1 . 1 . 1 . 1 . 1} }. > > >>> diag := (ESVerticalBarDiagram new) > > >>> identifier: [:each | each key ]; > > >>> y: [:each | each value size]; > > >>> yAxisLabel: 'Count'; > > >>> valueAxis; > > >>> rightYAxis; > > >>> defaultColor: Color veryVeryLightGray; > > >>> axisColor: Color veryVeryLightGray; > > >>> models: grouped; > > >>> rotatedLabels: true; > > >>> yourself. > > >>> diag2 := (ESVerticalBarDiagram new) > > >>> y: [:each | each value sum]; > > >>> regularAxis; > > >>> yAxisLabel: 'Sum'; > > >>> gapFraction: 2 / 3; > > >>> defaultColor: (Color red); > > >>> axisColor: (Color red); > > >>> models: grouped; > > >>> yourself. > > >>> (renderer compositeDiagram) > > >>> add: diag; > > >>> add: diag2. > > >>> renderer open > > >>> > > >>> > > >>> <Screenshot 2014-01-04 22.31.57.png> > > >>> > > >>> > > >>> The best I could produce with Graph-ET is this (I commented out > > >>> the > > >>> message to which I did not find a correspondent): > > >>> > > >>> builder := GETDiagramBuilder new. > > >>> grouped := { #item1->{10 . 12 . 11 . 14 } . #item2-> { 1 . 1 . 20 > > >>> } > > >>> . #item3->{ 1 . 1 . 1 . 1 . 1} }. > > >>> diag := (GETVerticalBarDiagram new) > > >>> "identifier: [:each | each key ];" > > >>> y: [:each | each value size]; > > >>> yAxisLabel: 'Count'; > > >>> valueAxisLine; > > >>> "rightYAxis;" > > >>> color: Color veryLightGray; > > >>> "axisColor: Color veryLightGray;" > > >>> models: grouped; > > >>> "rotatedLabels: true;" > > >>> yourself. > > >>> diag2 := (GETVerticalBarDiagram new) > > >>> y: [:each | each value sum]; > > >>> regularAxis; > > >>> yAxisLabel: 'Sum'; > > >>> "gapFraction: 2 / 3;" > > >>> color: (Color red); > > >>> "axisColor: (Color red);" > > >>> models: grouped; > > >>> yourself. > > >>> (builder compositeDiagram) > > >>> add: diag; > > >>> add: diag2. > > >>> builder open > > >>> > > >>> <Screenshot 2014-01-04 22.36.40.png> > > >>> > > >>> Cheers, > > >>> Doru

Jan. 8, 2014