Plugin Framework

[LeStarch]

The AutoAck code is becoming slightly hard to maintain due to many different commands all being part of a centralized "if" statement in the main loop. It is not strictly clear where or how to add new functionality. However, the basic functionality of any action remains simple:

On receive message m from user u, perform action(m,u).
onMessage(m,u)

Therefore, a simple plugin framework can be created so that every plugin is clean, and implements a small set of functions. This simplifies adding new code.

This issue is to add a simple framework for plugins and refactor basic actions of the Auto-Ack to be implemented that framework. It also constitutes the refactor of basic actions into "Plugins"

Plugin Framework:
Class:
Function 1: run(user,message)
Runs this plugin with IRC message consisting of given 'message' from given 'user'
Function 2: list()
Allows user to list commands supported by this plugin.

[chrismattmann]

yes, this makes total sense to me. ack.

[lewismc]

Seen

[LeStarch]

https://github.com/LeStarch/AutoAck has the changes for this issue. Once I finish testing Tweet functionality I will issue a pull request and this functionality can be brought into the fold.

[lewismc]

Bewm

On Tuesday, September 23, 2014, LeStarch [email protected] wrote:

https://github.com/LeStarch/AutoAck has the changes for this issue. Once
I finish testing Tweet functionality I will issue a pull request and this
functionality can be brought into the fold.

—
Reply to this email directly or view it on GitHub
#17 (comment).

Lewis

[tbpalsulich]

I like this idea. We may even consider entirely separate AutoAck programs -- one for IRC, one for Twitter, GitHub, etc. Each program could call the same plugins to get the proper responses.

So, we would have plugins for services (IRC, Twitter, etc, each with specific response protocols), and each of those has possibly overlapping plugins for how to respond. Does that make sense?

[lewismc]

Makes about as much sense as AutoAck...
Chocalate radiator springs to mind!!!

On Tue, Sep 23, 2014 at 3:53 PM, Tyler Palsulich [email protected]
wrote:

I like this idea. We may even consider entirely separate AutoAck programs
-- one for IRC, one for Twitter, GitHub, etc. Each program could call the
same plugins to get the proper responses.

So, we would have plugins for services (IRC, Twitter, etc, each with
specific response protocols), and each of those has possibly overlapping
plugins for how to respond. Does that make sense?

—
Reply to this email directly or view it on GitHub
#17 (comment).

Lewis