Hi folks,
I am Pablo Estefó an ObjectProfile engineer and I will continue the excellent work of Daniel Aviv on Graph-ET (on Roassal2).
I’ve just added the “oblique” labels feature(for Roassal2’s GraphET version only). And the result is something like this:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonal numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
It produces:
If we change the rotated label as diagonal inverted:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonalInverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new inverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
I am thinking a succinct way to specify it.
Well, as you can see the axis configuration will get more complex the more options we can provide. So our next question to drive our development is: How can we get the richest input in order to interpret it and return the best plot with the minimum configuration input.
I would like to know your opinions to develop a better Graph-ET :-)
Cheers, Pablo
Hi Pablo,
Welcome. Beautiful start :)
Would it be possible to create a configuration for GraphET2?
Keep it up.
Cheers, Doru
On Thu, Mar 13, 2014 at 9:26 PM, Pablo Estefó pestefo@gmail.com wrote:
Hi folks,
I am Pablo Estefó an ObjectProfile engineer and I will continue the excellent work of Daniel Aviv on Graph-ET (on Roassal2http://smalltalkhub.com/#!/~ObjectProfile/Roassal2 ).
I've just added the "oblique" labels feature(for Roassal2's GraphEThttp://smalltalkhub.com/#!/~DanielAvivNotario/GraphET2 version only). And the result is something like this:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (*GETRotatedLabelDecorator new diagonal numberOfLabels: 5*).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
It produces:
If we change the rotated label as diagonal inverted:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (*GETRotatedLabelDecorator new diagonalInverted numberOfLabels: 5*).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (*GETVerticalLabelDecorator new numberOfLabels: 5*).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (*GETVerticalLabelDecorator new inverted numberOfLabels: 5*).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ I am thinking a succinct way to specify it.
Well, as you can see the axis configuration will get more complex the more options we can provide. So our next question to drive our development is: How can we get the richest input in order to interpret it and return the best plot with the minimum configuration input.
I would like to know your opinions to develop a better Graph-ET :-)
Cheers, Pablo
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Welcome. Beautiful start :)
Would it be possible to create a configuration for GraphET2?
Something that Daniel did, and I do not know whether this is optimal or not, is that classes of GraphET1 and GraphET2 have the same names. We cannot have GraphET1 and GraphET2 at the same time (contrary to Roassal1 which can be loaded with Roassal2).
Alexandre
On Thu, Mar 13, 2014 at 9:26 PM, Pablo Estefó pestefo@gmail.com wrote: Hi folks,
I am Pablo Estefó an ObjectProfile engineer and I will continue the excellent work of Daniel Aviv on Graph-ET (on Roassal2).
I’ve just added the “oblique” labels feature(for Roassal2’s GraphET version only). And the result is something like this:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonal numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
It produces: <Screenshot 2014-03-13 15.18.16.png>
If we change the rotated label as diagonal inverted:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonalInverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
<Screenshot 2014-03-13 15.18.22.png> Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ <Screenshot 2014-03-13 15.18.37.png> Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new inverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ <Screenshot 2014-03-13 15.18.49.png> I am thinking a succinct way to specify it.
Well, as you can see the axis configuration will get more complex the more options we can provide. So our next question to drive our development is: How can we get the richest input in order to interpret it and return the best plot with the minimum configuration input.
I would like to know your opinions to develop a better Graph-ET :-)
Cheers, Pablo
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Mar 13, 2014, at 18:30, Alexandre Bergel alexandre.bergel@me.com wrote:
Welcome. Beautiful start :)
Would it be possible to create a configuration for GraphET2?
For now to try GraphET2 in Moose you have to: 1) Remove the GraphET package 2) Execute:
Gofer new smalltalkhubUser: 'DanielAvivNotario' project: 'GraphET2'; package: 'ConfigurationOfGraphET2'; load. (Smalltalk at: #ConfigurationOfGraphET2) loadDevelopment
Something that Daniel did, and I do not know whether this is optimal or not, is that classes of GraphET1 and GraphET2 have the same names. We cannot have GraphET1 and GraphET2 at the same time (contrary to Roassal1 which can be loaded with Roassal2).
The quickest way is to rename the prefix of classes to GE2 maybe? I read a thread about renaming GraphET, this situation is a good opportunity for that.
Cheers, Pablo
Alexandre
On Thu, Mar 13, 2014 at 9:26 PM, Pablo Estefó pestefo@gmail.com wrote: Hi folks,
I am Pablo Estefó an ObjectProfile engineer and I will continue the excellent work of Daniel Aviv on Graph-ET (on Roassal2).
I’ve just added the “oblique” labels feature(for Roassal2’s GraphET version only). And the result is something like this:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonal numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
It produces: <Screenshot 2014-03-13 15.18.16.png>
If we change the rotated label as diagonal inverted:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonalInverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
<Screenshot 2014-03-13 15.18.22.png> Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ <Screenshot 2014-03-13 15.18.37.png> Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new inverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ <Screenshot 2014-03-13 15.18.49.png> I am thinking a succinct way to specify it.
Well, as you can see the axis configuration will get more complex the more options we can provide. So our next question to drive our development is: How can we get the richest input in order to interpret it and return the best plot with the minimum configuration input.
I would like to know your opinions to develop a better Graph-ET :-)
Cheers, Pablo
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Renaming it to GET2 would be the best way to go given that it depends on Roassal2 which took the same approach.
Could you do this modification?
Doru
On Fri, Mar 14, 2014 at 2:47 PM, Pablo Estefó pestefo@gmail.com wrote:
On Mar 13, 2014, at 18:30, Alexandre Bergel alexandre.bergel@me.com wrote:
Welcome. Beautiful start :)
Would it be possible to create a configuration for GraphET2?
For now to try GraphET2 in Moose you have to:
- Remove the GraphET package
- Execute:
Gofer new smalltalkhubUser: 'DanielAvivNotario' project: 'GraphET2'; package: 'ConfigurationOfGraphET2'; load. (Smalltalk at: #ConfigurationOfGraphET2) loadDevelopment
Something that Daniel did, and I do not know whether this is optimal or not, is that classes of GraphET1 and GraphET2 have the same names. We cannot have GraphET1 and GraphET2 at the same time (contrary to Roassal1 which can be loaded with Roassal2).
The quickest way is to rename the prefix of classes to GE2 maybe? I read a thread about renaming GraphET, this situation is a good opportunity for that.
Cheers, Pablo
Alexandre
On Thu, Mar 13, 2014 at 9:26 PM, Pablo Estefó pestefo@gmail.com wrote: Hi folks,
I am Pablo Estefó an ObjectProfile engineer and I will continue the excellent work of Daniel Aviv on Graph-ET (on Roassal2).
I've just added the "oblique" labels feature(for Roassal2's GraphET version only). And the result is something like this:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonal numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
It produces: <Screenshot 2014-03-13 15.18.16.png>
If we change the rotated label as diagonal inverted:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonalInverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
<Screenshot 2014-03-13 15.18.22.png> Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ <Screenshot 2014-03-13 15.18.37.png> Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new inverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ <Screenshot 2014-03-13 15.18.49.png> I am thinking a succinct way to specify it.
Well, as you can see the axis configuration will get more complex the more options we can provide. So our next question to drive our development is: How can we get the richest input in order to interpret it and return the best plot with the minimum configuration input.
I would like to know your opinions to develop a better Graph-ET :-)
Cheers, Pablo
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Mar 14, 2014, at 10:53, Tudor Girba tudor@tudorgirba.com wrote:
Renaming it to GET2 would be the best way to go given that it depends on Roassal2 which took the same approach.
Could you do this modification?
Done! :-)
Doru
On Fri, Mar 14, 2014 at 2:47 PM, Pablo Estefó pestefo@gmail.com wrote:
On Mar 13, 2014, at 18:30, Alexandre Bergel alexandre.bergel@me.com wrote:
Welcome. Beautiful start :)
Would it be possible to create a configuration for GraphET2?
For now to try GraphET2 in Moose you have to:
- Remove the GraphET package
- Execute:
Gofer new smalltalkhubUser: 'DanielAvivNotario' project: 'GraphET2'; package: 'ConfigurationOfGraphET2'; load. (Smalltalk at: #ConfigurationOfGraphET2) loadDevelopment
Something that Daniel did, and I do not know whether this is optimal or not, is that classes of GraphET1 and GraphET2 have the same names. We cannot have GraphET1 and GraphET2 at the same time (contrary to Roassal1 which can be loaded with Roassal2).
The quickest way is to rename the prefix of classes to GE2 maybe? I read a thread about renaming GraphET, this situation is a good opportunity for that.
Cheers, Pablo
Alexandre
On Thu, Mar 13, 2014 at 9:26 PM, Pablo Estefó pestefo@gmail.com wrote: Hi folks,
I am Pablo Estefó an ObjectProfile engineer and I will continue the excellent work of Daniel Aviv on Graph-ET (on Roassal2).
I’ve just added the “oblique” labels feature(for Roassal2’s GraphET version only). And the result is something like this:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonal numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
It produces: <Screenshot 2014-03-13 15.18.16.png>
If we change the rotated label as diagonal inverted:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonalInverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
<Screenshot 2014-03-13 15.18.22.png> Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ <Screenshot 2014-03-13 15.18.37.png> Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new inverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ <Screenshot 2014-03-13 15.18.49.png> I am thinking a succinct way to specify it.
Well, as you can see the axis configuration will get more complex the more options we can provide. So our next question to drive our development is: How can we get the richest input in order to interpret it and return the best plot with the minimum configuration input.
I would like to know your opinions to develop a better Graph-ET :-)
Cheers, Pablo
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Renaming it to GET2 would be the best way to go given that it depends on Roassal2 which took the same approach.
Could you do this modification?
Done! :-)
Can you say a bit more Pablo ?
What is the configuration? What are its dependencies? ...
Alexandre
Doru
On Fri, Mar 14, 2014 at 2:47 PM, Pablo Estefó pestefo@gmail.com wrote:
On Mar 13, 2014, at 18:30, Alexandre Bergel alexandre.bergel@me.com wrote:
Welcome. Beautiful start :)
Would it be possible to create a configuration for GraphET2?
For now to try GraphET2 in Moose you have to:
- Remove the GraphET package
- Execute:
Gofer new smalltalkhubUser: 'DanielAvivNotario' project: 'GraphET2'; package: 'ConfigurationOfGraphET2'; load. (Smalltalk at: #ConfigurationOfGraphET2) loadDevelopment
Something that Daniel did, and I do not know whether this is optimal or not, is that classes of GraphET1 and GraphET2 have the same names. We cannot have GraphET1 and GraphET2 at the same time (contrary to Roassal1 which can be loaded with Roassal2).
The quickest way is to rename the prefix of classes to GE2 maybe? I read a thread about renaming GraphET, this situation is a good opportunity for that.
Cheers, Pablo
Alexandre
On Thu, Mar 13, 2014 at 9:26 PM, Pablo Estefó pestefo@gmail.com wrote: Hi folks,
I am Pablo Estefó an ObjectProfile engineer and I will continue the excellent work of Daniel Aviv on Graph-ET (on Roassal2).
I’ve just added the “oblique” labels feature(for Roassal2’s GraphET version only). And the result is something like this:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonal numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
It produces: <Screenshot 2014-03-13 15.18.16.png>
If we change the rotated label as diagonal inverted:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonalInverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
<Screenshot 2014-03-13 15.18.22.png> Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ <Screenshot 2014-03-13 15.18.37.png> Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new inverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ <Screenshot 2014-03-13 15.18.49.png> I am thinking a succinct way to specify it.
Well, as you can see the axis configuration will get more complex the more options we can provide. So our next question to drive our development is: How can we get the richest input in order to interpret it and return the best plot with the minimum configuration input.
I would like to know your opinions to develop a better Graph-ET :-)
Cheers, Pablo
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow" _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Now I must have missed something... Does that mean that rotated text is working in Rossal / Roassal2 ?
With Roassal2
https://www.facebook.com/ObjectProfile/photos/a.573528479400420.1073741841.3...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | v shape | v := RTView new. shape := RTRotatedLabel new. shape angleInDegree: [ :cls | cls numberOfMethods negated / 1.5 ]. shape text: [ :cls | ‘ ', cls name ]. shape color: (Color black alpha: 0.2). v addAll: (shape elementsOn: Collection withAllSubclasses).
v canvas color: Color white. v open -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Cheers, Alexandre
Ideas to make Graph-ET more usable as the configuration options grow? Sorry I can't be ore helpful, but all I can think of is make the configuration interactive via menus and dialogs. Refer to existing charting apps like Microsoft Excel for workflow.
cheers -ben
Pablo Estefó wrote:
Hi folks,
I am Pablo Estefó an ObjectProfile engineer and I will continue the excellent work of Daniel Aviv on Graph-ET (on Roassal2).
I’ve just added the “oblique” labels feature(for Roassal2’s GraphET version only). And the result is something like this:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonal numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
It produces:
<Mail Attachment.png>
If we change the rotated label as diagonal inverted:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETRotatedLabelDecorator new diagonalInverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
<Mail Attachment.png> Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
<Mail Attachment.png> Vertical labels =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ | diagram | diagram := GETDiagramBuilder new. diagram horizontalBarDiagram models: #(0.2 0.5 2 0.3 0.51 1); color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]]; valueAxisLine; baseAxisLine; addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5); addValueDecorator: (GETVerticalLabelDecorator new inverted numberOfLabels: 5).
diagram open =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
<Mail Attachment.png> I am thinking a succinct way to specify it.
Well, as you can see the axis configuration will get more complex the more options we can provide. So our next question to drive our development is: How can we get the richest input in order to interpret it and return the best plot with the minimum configuration input.
I would like to know your opinions to develop a better Graph-ET :-)
Cheers, Pablo
Moose-dev mailing list
Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Ben Coman -
Pablo Estefó -
Tudor Girba