20 Jan
2010
20 Jan
'10
3:04 a.m.
On 19 Jan 2010, at 07:40, Tudor Girba wrote:
I know it does not do that. I'm sorry, it seems that I am not being
clear. The problem is that the use of this mock collection is
needlesly complicating the code. I am all for MVC but in this case it
only serves to confuse the picture. Please simplify the example. I as
a dumb Glamour user dont know how these announcements work, dont
complicate it more by adding an extra layer of indirection. Let the
menu item construct the right announcement and send it to where it
needs to go. Please dont expect me to go looking at/stepping through
the entire code of the MVC setup to find that 1 line of code that
sends the update to the right place.
OK, found that, thanks!
--
Johan Fabry
jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile
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. - 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 :).