I also have provided same facility in my project , that palette Entry can
be added at runtime.
When particular action executes , in it's handler i have added new
PaletteEntry to one static paletteContainer ( Drawer) ( one for every
editor).
Similarly i keep record of newly added palette Entries into database,
identified by unique ID so that next ( after restarting eclipse) when i
open same editor file i should get same palette , and dnd should produce
same model last saved ( not the same object but same key attr).
In this way i can even add paletteDrawer , palette separator , which are
persistent as their unique attr are stored in dbase.
So is this the right way to have persistent palette which can be
custumized
( add , delete , rename , change desc) at runtime ,in any way.