0 branches
Tree
Top files
Clone with HTTPS:
Event Bus
A module to provide eventing capabilities using pub/sub.
API
new[T]()- create a newEventBusEventBus.new[T]()- create a newEventBus
Structs:
EventBus:
publish(name T, sender voidptr, args voidptr)- publish an event with provided Params & nameclear_all()- clear all subscribershas_subscriber(name T)- check if a subscriber to an event existsSubscriber:subscribe(name T, handler EventHandlerFn)- subscribe to an eventsubscribe_once(name T, handler EventHandlerFn)- subscribe only once to an eventsubscribe_method(name T, handler EventHandlerFn, receiver voidptr)- subscribe to an event and also set thereceiveras a parameter. Since it's not yet possible to send methods as parameters, this is a workaround.is_subscribed(name T)- check if we are subscribed to an eventunsubscribe(name T)- unsubscribe from an eventEvent Handler Signature:The function given tosubscribe,subscribe_methodandsubscribe_oncemust match this:fn cb(receiver voidptr, args voidptr, sender voidptr) { } // Since V can map structs to voidptr, this also works struct ClickEvent { x int y int } // Example case where publisher sends ClickEvent as args. fn on_press(receiver voidptr, e &ClickEvent, sender voidptr) { println(e.x) // your code here... }
Usage
For usage across modules check the example.
Note As a general rule, you will need to subscribe before publishing.
main.v
module main
import eventbus
// initialize it globally
const eb = eventbus.new[string]()
fn main() {
// get a mutable reference to the subscriber
mut sub := eb.subscriber
// subscribe to the 'error' event
sub.subscribe('error', on_error)
// start the work
do_work()
}
// the event handler
fn on_error(receiver voidptr, e &AnError, work &Work) {
println('error occurred on ${work.hours}. Error: ${e.message}')
}
work.v
module main
import eventbus
struct Work {
hours int
}
struct AnError {
message string
}
fn do_work() {
work := Work{20}
// get a mutable Params instance & put some data into it
error := &AnError{'Error: no internet connection.'}
// publish the event
eb.publish('error', work, error)
}
Notes:
- Each
EventBusinstance has its own registry (i.e. there is no global event registry so you can't just subscribe to an event wherever you are. - Each
EventBushas aSubscriberinstance which will need to be either exposed or you can make small public helper functions specific to your module like (onPress,onError) and etc. - The
eventbusmodule has some helpers to ease getting/setting of Params (since V doesn't support empty interfaces yet or reflection) so use them (see usage above).The rationale behind separating Subscriber & Publisher:This is mainly for security because if publisher & subscriber are both passed around, a client can easily publish events acting as the server. So a client should only be able to use the Subscriber methods.