Hi,
OK, so I got it running now, thanks!
But I hit the next hurdles:
- the updatableBrowser example is too complex for the glamour
newbees like me. Can you make a simple example, like using a plain old OrderedCollection {1 2 3} that is shown in a list and a button where hitting the button adds the next number to the collection?
OrderedCollection does not throw announcements, that is why I use a mock collection that does throw announcements when you add and remove entities.
I updated the example with a menu.
- there is no menu in the mondrian presentations of updatableBrowser
(and neither in the root of AspectMaps) :-(
Yes, it does, only Mondrian shows the root menu only within the bounds of the graph. So, in the example, if you place your mouse between 1 and 2 so that no popup text appears, you will get the menu. It is not ideal, but now the ball is in the Mondrian court to deal with the root menu in the complete canvas :).
Anyway, now it looks like we have a small problem in updating the list due to some changes in the MorphTreeWidget. I will look into it.
Cheers, Doru
On 18 Jan 2010, at 18:26, Tudor Girba wrote:
Hi,
It's done in two ways :).
- 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)
- 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
-- Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."