trace: true output is way too verbose #15
Description
trace: true should be useful for Ki users. Right now, it's got a whole bunch of logging info that's only useful for people writing Ki itself. Please clean it up (perhaps add a second mode, traceAll: true that has the stuff that's there now).
What I want to know is: which event/actions were sent to the statechart, which states were given a chance to handle the event, which state did handle the event OR that the event was ignored, and finally which transition was specified (if any) along with the exit/enterState calls that are made. This allows me to fully trace user statechart code and see exactly what's happening.
Thanks!