18 Jan
2010
18 Jan
'10
10:26 p.m.
Hi,
It's done in two ways :).
1. The actions defined on the Mondrian presentations now appear as a
menu on the root in the view. With this you can trigger update. See:
GLMBasicExamples new updatableBrowser
(execute "self add: 4" in the inspector and then see what happens in
the views)
2. The painting block now gets after the entity variables an entry to
the mondrian presentation. So, you can use it for manipulating the
presentation from inside the mondrian script:
a mondrian
painting: [:view :entity :mondrianPresentation | ... ]
Cheers,
Doru
On 18 Jan 2010, at 19:35, Johan Fabry wrote:
On 18 Jan 2010, at 14:52, Tudor Girba wrote:
OK, thanks, please keep me posted. This is quite crucial so that
AspectMaps can work as intended ...
--
Johan Fabry
jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."
I want to
update the mondrian presentation based on changes made
in the model (either by a specific menu action or by clicking on a
button). The mondrian presentation should basically redraw itself
completely.
Well, there are two ways:
- either listen to an announcement, or
- if you want to trigger it from a menu item, you should just send
update to the presentation. However, I have the problem with
Mondrian in that I am not passing the presentation, but directly
the ViewRenderer in the painting. It is long on my to do list to
fix this. I will look into it.