Updated widget initialization

Updated widget initialization to now use the same event cycle for all widget's that were initialized from the previous event cycle via the $timeout promise.

Instead of causing angular to $digest for every single widget, it should only need to digest once per set of widgets.

This also may help with the FOUJUI problem (Issue #18?), by making it one cycle to initialize everything then hand off to the browser.

-----
I came up with this when my proof of concept angular app, running against our application had about 50 widgets (datepickers, spinners and dropdowns) initalizing.  There was a visible wave as each $timeout was digested, initializing each control.  Which while interesting to watch, certainly wasn't desired!

Questions, comments and concerns are welcomed!