Comment #1 on issue 884 by alexandr...(a)gmail.com: The Roassal presentation should react to custom ports http://code.google.com/p/moose-technology/issues/detail?id=884 Events cannot be used for that purpose?

Comment #3 on issue 884 by alexandr...(a)gmail.com: The Roassal presentation should react to custom ports http://code.google.com/p/moose-technology/issues/detail?id=884 I do not know. If Glamour generates event, then Roassal can listen at them.

Comment #5 on issue 884 by tu...(a)tudorgirba.com: The Roassal presentation should react to custom ports http://code.google.com/p/moose-technology/issues/detail?id=884 Ok. Here is a working version for now: browser := GLMTabulator new . browser with: [:tabulator | tabulator column: #index; column: #visualization. tabulator transmit to: #index; andShow: [:a | a list ]. tabulator transmit to: #visualization; andShowIfNone:[ :a | a roassal painting: [:view :collection :roassal | view shape label. view nodes: collection. view gridLayout. roassal on: GLMContextChanged do: [:ann | ann property = #highlight ifTrue: [ ann oldValue ifNotNil: [ ROUnhighlightElement on: (ann presentation view raw elementFromModel: ann oldValue)]. ROHighlightElement on: (ann presentation view raw elementFromModel: ann value) color: Color red ]]]]. tabulator transmit from: #index; to: #visualization port: #highlight ]; openOn: ( 1 to: 20).

Comment #7 on issue 884 by tu...(a)tudorgirba.com: The Roassal presentation should react to custom ports http://code.google.com/p/moose-technology/issues/detail?id=884 Great. Here is a slightly extended version in which we deal with bidirectional updates between the list and roassal: | browser | browser := GLMTabulator new . browser with: [:tabulator | tabulator column: #index; column: #visualization. tabulator transmit to: #index; andShow: [:a | a list ]. tabulator transmit to: #visualization; andShowIfNone:[ :a | a roassal painting: [:view :collection :roassal | view shape label. view interaction on: ROMouseLeftClick do: [:ann | (roassal pane port: #selection) value: ann element model ]. view nodes: collection. view gridLayout. roassal on: GLMContextChanged do: [:ann | ann property = #selection ifTrue: [ ann oldValue ifNotNil: [ ROUnhighlightElement on: (ann presentation view raw elementFromModel: ann oldValue)]. ROHighlightElement on: (ann presentation view raw elementFromModel: ann value) color: Color red ]]]]. tabulator transmit from: #index; to: #visualization port: #selection. tabulator transmit from: #visualization port: #selection; to: #index port: #selection. ]. I think it's pretty cool that we can easily accommodate such a scenario without worrying about possible infinite loops.

Comment #9 on issue 884 by benjamin...(a)gmail.com: The Roassal presentation should react to custom ports http://code.google.com/p/moose-technology/issues/detail?id=884 One thing I haven't been able to work out is when clicking on the #visualization background I need the element to deselect and also deselect the element in the list. I observe that when clicking in the #visualization pane, hightlighted-selection still works when the following lines are commented out. + view interaction on: ROMouseLeftClick do: [:ann | (roassal pane port: #selection) value: ann element model ]. + tabulator transmit from: #index; to: #visualization port: #selection. + tabulator transmit from: #visualization port: #selection; to: #index port: #selection. Also I see that adding a break here.... roassal on: GLMContextChanged do: [:ann | self halt. shows this is invoked three times when clicking on an element in the #visualization pane but not invoked when clicking on the background on the #visualization pane. I am unable to find my way any deeper than that. Any ideas?

Updates: Status: Started Comment #11 on issue 884 by alexandr...(a)gmail.com: The Roassal presentation should react to custom ports http://code.google.com/p/moose-technology/issues/detail?id=884 What about this issue? Is there something to do? Here is a new version of Ben's script (ROHighlightElement and ROUnhighlightElement) have been changed into ROBlink : -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | browser activeSelection | activeSelection := ROSelection new onInclusion: [ :element | ROBlink highlight: element color: Color red ]; onExclusion: [ :element | ROBlink unhighlight: element ]. browser := GLMTabulator new . browser with: [ :tabulator | tabulator column: #index; column: #visualization. tabulator transmit to: #index; andShow: [:a | a list ]. tabulator transmit to: #visualization; andShowIfNone: [ :a | a roassal painting: [ :view :collection :roassal | view shape label. view interaction on: ROMouseLeftClick do: [:ann | (roassal pane port: #selection) value: ann element model ]. view nodes: collection. view gridLayout. roassal on: GLMContextChanged do: [ :ann | ann property = #selection ifTrue: [ activeSelection clear. activeSelection add: (ann presentation view raw elementFromModel: ann value) . ]. ]. ]. ]. tabulator transmit from: #index; to: #visualization port: #selection. tabulator transmit from: #visualization port: #selection; to: #index port: #selection. ]. browser openOn: #(1 2 3 4 5). -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Everything seems to work as expected. Shall I close the issue? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

Comment #13 on issue 884 by alexandr...(a)gmail.com: The Roassal presentation should react to custom ports http://code.google.com/p/moose-technology/issues/detail?id=884 Is there an event, sorry, an announcement, about deselection? by the way, why do we still use the word "Announcement" whereas the whole World calls an event event? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings