| Invisible Plugin Architecture [message #329846] |
Tue, 08 July 2008 08:26 |
Eclipse User |
|
|
|
Hi,
I have 3 plugins; A, B C.
Plugin A is a TreeViewer
Plugin B is invisible
Plugin C is a TreeViewer
When an object in the TreeViewer in Plugin A is selected it should raise
an event (via setSelection). This event is received by plugin B
(selectionChanged called on listener). At plugin B some work is done.
Plugin B then raises an event. Plugin C receives this event and changes
the selected object (selectionChanged called on listener).
The workflow can also work backwards i.e. C->B->A
My problem is that Plugin B has no visual element to it as it works in the
background receiving events, doing some work on the input and the
propagating the event with some new output. The fact that it has no visual
element means that it cannot extend ViewPart. Also if I understand
correctly even if it did the SelectionService wouldn't work as the plugin
is not visible and so can't send/receive events.
So my question is, what is the best practice for creating a plugin the
works invisibly? How can I create events for the visible plugins to
consume?
Thanks,
Ronan
|
|
|
Powered by
FUDForum. Page generated in 0.02330 seconds
Home