Roles are all about static composition, and events are for dynamic composition. Roles that emit() events blur this distinction, so I'm deeming them to be "bad". Additionally, one of Reflex's prime directives is for consumers to decide how they'll handle things. Implementing "interface" callbacks in roles (even default ones) takes this away from the consumer. The current solution is to provide declarative helpers to define the defaults. They also make more explicit that it's the consumer's role (har) to define callbacks in all cases. This is slightly less convenient, but it's a lot cleaner. Also add vim format lines so I stop dealing with whitespace inconsistencies.
…orker management requirements.
…egration Patterns. Summarize some of those patterns in the TODO outline, and add tasks to investigate more.
Using it in my rx-firmata work: $uno->put_handle("\xF0\x6B\xF7"); $uno->next('initialized');
…e project back 3%. :(
… alternatives that were considered, pros and cons.
…l don't work, however.
… timers. About 97% done with the renaming.
…ed to change a lot of code and docs that used Reflex::Timer, which has bee deleted.
…thods. I still don't like the function names, but they're good placeholders for now.
… to Reflex::Base.