I wish plugin.xml would allow me
- to specify properties
- install the same action many times, with different
In a plugin.xml, I install 8 actions to clear of set 4 properties that 1
editor could have.
When you look at those 8 actions code, it's just 2 lines, 2 methods that
just pass 2 params to the common ancestor (set/clear, prop1..4)
If plugin.xml would accept properties, it could scrap those 8 classes,
in this very simple case.
Does it make sense to anybody else?