search

LaKraven / LKSL

LaKraven Studios Standard Library
http://otapi.com
Other
51 stars 15 forks source link

Event Type Registration replace with Named Events #13

Closed LaKraven closed 9 years ago

LaKraven commented 9 years ago

Re #12, It will no longer be necessary to "Register" Event Types, or to provide a unique GUID for each Event Type.

This is because an Event will no longer be Streamable by default (see issue #12 for more info on that).

It makes sense to provide each Event Type with a "friendly name" for certain other features of the Event Engine (such as the upcoming Real-Time Tracking solution for debugging) to make it easier to differentiate between implementations. This will replace the GUID requirement on TLKEvent.

LaKraven commented 9 years ago

Decided that it's more reasonable to allow each implementing developer to decide whether or not they wish to associate names with their Events.

Producing a registration system to request an Event Type by Name is laughably easy, so there's no point in me forcing this option on everyone.