Reply to thread

Actually it's possible to write a plugins that send action, message, or keystroke to MP, so it's possible to

write a plugins that send command to MP, and it's possible to handle many event (for example, OnPropertyChange on GuiProperty), but this

require that every assembly must be the correct build, and if i write a plugin "alfa" that interact with a plugin "beta", i need the

assembly of "beta".

I think that a technique for interoperability between plugins and core:

- must be a "standard design guidelines" for core and plugins developers, so accepted by all developers

- must be implemented in MP core, cannot be implemented as process plugin, because also core need to support them

- must be assembly build indipendent

i think it's a very important also for building a scripting engine inside MP.

What type of technique (my proposal, PVRX or other) it's a detail, because if a techique exists in core, a plugins (like your PVRX) can

wrapper that, but actually for example it's practically impossible to intercept when the Alarm event in MyAlarm occur without changing the code,

because MyAlarm plugins doesn't expose any event.

Please note, it's not a critic to MyAlarm developer, it's only an example!

So, what others developers and lead developers think about this topic?

Ok, for now stability is more important of this, but we can start to study the best solution for interoperability of MP 9.9....

bye!