tenquestionmarks/src/modules/mod.rs

pub mod lua;
pub mod discord;
pub mod stdin;
pub mod echo;
pub mod random;
pub mod pvn;
pub mod echobox;

pub mod loader;

use Tenquestionmarks;
use event::Envelope;

use std::sync::Arc;
use std::sync::mpsc::Receiver;
use transformable_channels::mpsc::ExtSender;

pub trait Module : Sync {
    fn register (&self, _: &Tenquestionmarks) {}
    fn run (&self, _: Box<ExtSender<Envelope>>, _: Receiver<Arc<Envelope>>) {}
}
Beginning of rust implementation for tenquestionmarks. 2017-02-08 03:25:03 -06:00			`pub mod lua;`
			`pub mod discord;`
Flesh out plugins event handling, add example stdin plugin (event producer) and echo plugin (event consumer). Next step: fleshing out user/channel structs 2017-02-13 00:22:06 -06:00			`pub mod stdin;`
			`pub mod echo;`
Add random response module 2017-02-16 02:00:38 -06:00			`pub mod random;`
initial pvn module implementation 2017-02-19 04:49:06 -06:00			`pub mod pvn;`
now with amazing echobox powers 2017-02-22 23:40:30 -06:00			`pub mod echobox;`
Beginning of rust implementation for tenquestionmarks. 2017-02-08 03:25:03 -06:00
			`pub mod loader;`

Flesh out plugins event handling, add example stdin plugin (event producer) and echo plugin (event consumer). Next step: fleshing out user/channel structs 2017-02-13 00:22:06 -06:00			`use Tenquestionmarks;`
Simplify module trait by combining produce/consume event methods into a single run method that runs in the module's own thread and can produce and/or consume events. Introduce an Envelope struct that encapsulates event + to/from so we can (eventually) tag every event and also limit where events are sent (e.g. you can have a specific module configured to talk or listen only to a certain other module). 2017-02-25 20:17:46 -06:00			`use event::Envelope;`
Beginning of rust implementation for tenquestionmarks. 2017-02-08 03:25:03 -06:00
send/receive Arc<Event> instead of Event so we don't have to clone objects all over the place. This might also enable us to be a bit more flexible with what we send with Events, and might simplify things elsewhere. 2017-02-19 02:55:30 -06:00			`use std::sync::Arc;`
replace Sender with ExtSender from transformable_channels. Now we can tag each outgoing envelope with the name of its sender 2017-02-25 21:11:25 -06:00			`use std::sync::mpsc::Receiver;`
			`use transformable_channels::mpsc::ExtSender;`
Flesh out plugins event handling, add example stdin plugin (event producer) and echo plugin (event consumer). Next step: fleshing out user/channel structs 2017-02-13 00:22:06 -06:00
rename plugin -> module 2017-02-16 01:05:33 -06:00			`pub trait Module : Sync {`
Simplify module trait by combining produce/consume event methods into a single run method that runs in the module's own thread and can produce and/or consume events. Introduce an Envelope struct that encapsulates event + to/from so we can (eventually) tag every event and also limit where events are sent (e.g. you can have a specific module configured to talk or listen only to a certain other module). 2017-02-25 20:17:46 -06:00			`fn register (&self, _: &Tenquestionmarks) {}`
replace Sender with ExtSender from transformable_channels. Now we can tag each outgoing envelope with the name of its sender 2017-02-25 21:11:25 -06:00			`fn run (&self, _: Box<ExtSender<Envelope>>, _: Receiver<Arc<Envelope>>) {}`
Beginning of rust implementation for tenquestionmarks. 2017-02-08 03:25:03 -06:00			`}`