Allow instantiatable plugins for droplab
We currently have a problem with droplab, all of the plugins are object literals, i.e. singletons.
This means if we use a plugin twice on one page, under 2 separate instances of DropLab
, one dropdown will affect the state of the other. I'm sure there is some case where this is handy. But we should also handle cases where its not wanted.
We can fix this by letting people provide instantiatable objects (prototypes/classes) that droplab can then instantiate when needed to avoid shared scopes.