Skip to content
gkistler edited this page Aug 26, 2011 · 62 revisions
  • Consider PRIORITY
  • Priority probably only comes into play when you want to "overwrite" an existing hook, and then only really makes sense in the "send" event. But really, the only case where you would want to overwrite a send event, is if you wanted to overwrite the default send event, and implement your own. I need to think some more about this.
  • Consider hooking send events
  • Module mapping declarations, currently look like:
	mappings = (Mapping(type=["privmsg"], command="alias", function=alias),)

Maybe different?

  • Container object for DB queries
  • The more module convenience the better, things like event.isadmin and the like might be really handy, or that can be left for module writer I suppose. I think it's nice though
  • Adds to complexity in the event system. Think about the case where you just want to capture every event to log, or to 'butt', you are processing the user fields, and checking admin status even though they'll never be used
  • Having a utility function though to check for admin status might be nice.
  • Agreed, utility functions are probably the way to go.

Clone this wiki locally