A couple of final points
1. Is kendo.observable.trigger() an undocumented function?
mentions it in this forum, but I have not seen it anywhere else. Does
that mean we cannot rely on it? It seems useful to me, if there is no
performance issues over .set() and .get()
2. I like shorter, simpler, and less code for maintenance and
upkeep. So I find creating row-templates, and relying on magic numbers
outside the VM fragile, creating issues for code maintenance.
3. Take a look at my latest update to my codePen: http://codepen.io/DrYSG/pen/wnDxL
tell me what I am doing is that much more expensive by using
.trigger() instead of set() and get() and row-templates. I am not
dogmatic (too old and experienced for that), just curious, but I want to
make sure the design paradigm I am using is not doing massive re-layout
and other nasty side effects, especially if the table grows to hundreds