[orion-dev] Plugin organization

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

Since we've grown a half dozen Orion plugins
in the past week, our approach of dumping all plugins and associated files
in the root directory is becoming unmanageable. It is hard to differentiate
plugin code from framework code this way, which will be important once
we actually want to host these plugins on different servers from the framework.
I took an initial cleanup step by putting all plugin HTML files in a new
/static/plugins directory. Since the plugin file's location is essentially
the plugin id, it was important to at least do this "breaking"
step before M6. Further cleanup/organization of the various JS files used
by the plugins can then be done without breaking anything. Once you pull
the client from master you should flush your local storage to discard any
installed plugins from the old location (invoke "localStorage.clear();"
from your browser's _javascript_ console).

Also keep in mind when creating plugins
that the decision point on when to move code into a plugin is different
from Eclipse desktop. In Eclipse, creating a plugin is largely a packaging
decision: "Would I ever want to install/run X without Y". In
Orion, the decision largely depends on host separation: "Would I ever
want to install X on a different web server from Y". Since code in
a plugin will have significantly reduced privileges and a non-trivial performance
overhead per plugin, we don't want to be creating Orion plugins lightly.

John