Hi Fabrizio,
The development of GraphET is discontinued. We should focus on Charter instead.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Jul 31, 2014, at 7:21 AM, Fabrizio Perin <fabrizio.perin(a)gmail.com> wrote:
Hi,
I built sometimes ago a tab in the moose panel to show an eyesee pieChart:
viewAccessesTypesPieChartIn: composite
<moosePresentationOrder: 275>
composite eyesee
title: 'Database accessor types';
titleIcon: MooseJEEIcons pieChart;
diagram: [ :view :each | each mooseInterestingEntity viewAccessesTypesPieChartOn:
view ];
when: [ :input | input mooseInterestingEntity isKindOf: FAMIXDBAccessGroup ]
Now, if I load eyesee and the eyesee glamour presentation everything is fine, however, I
would like to port this view on graphET. So, I tried:
viewAccessesTypesPieChartIn: composite
<moosePresentationOrder: 275>
composite graphET
title: 'Database accessor types';
titleIcon: MooseJEEIcons pieChart;
diagram: [ :view :each | each mooseInterestingEntity viewAccessesTypesPieChartOn:
view ];
when: [ :input | input mooseInterestingEntity isKindOf: FAMIXDBAccessGroup ]
now the local variable each contains the presentation instead of the model, is that a
wanted feature? If so, how can i access the model elements to invoke the view I need?
Should I move the logic that implements the view?
Thanks in advance,
Fabrizio
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev