Planner: Plugin Support

[BeatLink]

Implementing a plugin system would help make planner easier to maintain as well as more customizable to individual users taste. It will help reduce bloat and feature creep by allowing the application to have a small, solid core, while still allowing users to install as many plugins as they want or need to suit their purposes.

[alainm23]

I like the idea.

[BeatLink]

Awesome! As a step further, once this is implemented, you could reimplement existing core features as separate plug-ins as well. Completely up to you though, and its something to think about after the plug-in support is implemented so you can sleep on it.

[alainm23]

I just uploaded a basic plugin system implementation but now I don't know how to make it work, I think I'll need some help.

[BeatLink]

Hmm. Okay, ill take a look at the codebase when I can and see what I can do.

[BeatLink]

But basically, a typical plugin architecture works by passing parts of the application you want plugins to access as parameters to the plugin initializer. To start out, you could pass broad generic objects, (such as the window object, database manager object and so on) but down the line you will want to create more specific objects and functions to limit plugin access, improve security and prevent breaking and crashing when plugins conflict with each other or try to access the same object at the same time

[alainm23]

I'm very happy to announce that the plugin system works 🎉️🎉️🎉️

This plugin gives solution to #571 and it is only the first step for a new Planner.

[BeatLink]

Awesome!

[Skaldebane]

Great job! This'll make it easier to make custom plugins for custom needs. Waiting for documentation once it's done 👌