Community
Participate
Working Groups
This enhancement describes the ability for common navigator viewer instances to "inherit" the action and content bindings from other viewers.
Created attachment 89103 [details] Suggested implementation patch This patch contains changes to the naviagtor registry reader to recognize a predefined "option" for viewer inheritance, and register these relationships. The reader then registers bindings with all child viewers
I took a different approach than your implementation (sorry I can't attach a patch, I put the patch in my clipboard and overwrote it, after I had checked it in). Anyhow, I added an inheritsBindingsFrom attribute to the viewer element. It inherits the bindings (both types) and the drag assistants (like your patch), it does not inherit the viewer properties. It also does not have any way to add bindings in the child viewer, it uses exactly those of the parent. If this does not meet your requirements, please open another bug report. Released to HEAD, I20090308-2000, 35M6
I have tested, and this is fantastic!! But.. I really can't use without the ability to extend beyond whats inherited. I will verify this, but open a separate enhancement... hopefully in time for M7?
Added https://bugs.eclipse.org/bugs/show_bug.cgi?id=270008