• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Inter plugin communication (in applet)

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I am developping an Applet as a Mainframe. Tools/Plugins can be added to this applet/frame via an addPlugin function. There is no need for dynamic Plugin extensibility.
Plugins are hardcoded. In most cases the data to work with is selected from a tree.

Those plugins should be able to communicate with each other and send/share data.
My approach was, that each plugin has its own data object (extends Oberservable) containing the data it needs. Every plugin can read/write the data object of any other plugin.
Plugins are informed of changes in ther data object by the notifyOberserves() method.
By this, i overwrite the data objects content.

Now my question:

Is there any good idea to implement inter plugin communication within one app(-let) ?
Assumed the data to communicate could change from plugin to plugin or while developing new ones. How to implement a kind of generic communication?

I hope someone will understand what I mean by all this ;)
 
Ranch Hand
Posts: 1936
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Benne House wrote:
Assumed the data to communicate could change from plugin to plugin or while developing new ones. How to implement a kind of generic communication?


Why do you want a generic communication?

And could you please to give a concrete example of what you're trying to do?
At this point, I don't know what to suggest, because I don't understand the problem well enough.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic