Sending an event obviously de-couple Ares from the plugin(s).
However, this signal will be sent to all plugins listening for the signal "onPaletteAction".

How do you manage that case (several plugins listening on the signal "onPaletteAction") ?
How a plugin will decide if it has something to do ?

After that, what a plugin can do when it receives such signal ?
If we allow a plugin to do anything it wants by going into the internal data of deimos, the inspector, ...
we will end-up into a very high coupling level between the plugins and Ares which is problematic.

In other words, any little change in Ares may break the behavior of Ares and the plugin.

So, we need to define some public interfaces between the Designer (Deimos, inspector, ...) and the
plugins.

For me, only deimos should be visible by the plugins.

@KiwookShim: Do you agree ?
We can organize a phone conf to move forward on that topic.