...
[11:36:16 CST(-0600)] <TonyUnicon> thanks for your help
[11:48:19 CST(-0600)] <dmccallum54> there's something to be said for consistency, but if you can accomplish the same thing more efficiently with a hasMany and without huge ripple effects, i've got no objections
[11:49:00 CST(-0600)] <TonyUnicon> judging by the number of forum posts on the Sencha site
[11:49:09 CST(-0600)] <TonyUnicon> it appears a lot of folks have trouble using it
[11:49:19 CST(-0600)] <dmccallum54> …again, worst case for us is to accidentally end up spending a lot of time on reengineering projects if we have a workable solution now, even if maybe non-ideal
[11:49:47 CST(-0600)] <TonyUnicon> its possible thats why they decided to use the api per entity approach
[14:46:08 CST(-0600)] <TonyUnicon> I did forget to mention today during the standup that I was able to rework the layout of the admin screens so that the TreeMenu is now collapsable
[14:46:18 CST(-0600)] <TonyUnicon> so there will be more real estate for the various forms and such
[14:46:23 CST(-0600)] <dmccallum54> cool
[14:46:34 CST(-0600)] <TonyUnicon> had to use a different layout manager but it looks pretty much the same