Plugin System?

[spencerthayer]

So I am modifying Shout to a point where I cannot easily update it when you push a new fix. I'm wondering what your thoughts are on core modifications like this

Is there a plugin system planned for shout? It would be nice to be able to have all the system wide changes I want to make remain in a separate folder that isn't touched from a git update.

Those changes being fairly significant...

• autoconnect hack.
• removing private use options.
• removing any connection options except for choosing a nickname.
• restricting users from accessing the settings
• restricting users from connecting to other servers.
• restricting users from joining other channels.
• Significant Theme and CSS redesigns.
• Auto generating nicknames for users upon application start.
• Load balancing hack for free Heroku hosting.
• And soon passing URL key values.

[erming]

I'm currently thinking about overhauling the architecture of both the backend and the frontend. If I could use the eventEmitter pattern as much as possible, on both the server and the client, that would make a good fit for plugins. Everything in the core would then fire an event that you could hook into.

I might create a new branch soon, in which I start doing this overhaul.

Stay tuned!

[spencerthayer]

+1

[ibizaman]

Thanks to @janza: #320, some of it came true!

[spencerthayer]

It's a start in the right direction!

[YeahToast]

I +1 this

[olivierlambert]

Centralizing plugin stuff here: #554