...
[16:46:32 CDT(-0500)] <dmccallum54> so that if you, say, click a different journal entry, then click back on the original journal entry, oops, all your clobbering is still there
[16:52:18 CDT(-0500)] <pspaude1> Sorry answerwing q's to our docs person. Ok, that makes a lot of sense I've done some limited testing and I'll look for that. Actually, the list view is working the best, I'm trying to understand the confidentiality and other fields how to reset those. At first glance server call seems easiest, but if you know of better ways let me know.
[16:53:19 CDT(-0500)] <dmccallum54> the client side option is to defer all form-model bindings to save time
[16:54:46 CDT(-0500)] <dmccallum54> i think some of our forms elsewhere already do that. and you'll some of it going on here as well. e.g. in Ssp.controller.tool.journal.TrackTreeViewController
[16:55:40 CDT(-0500)] <dmccallum54> i'm pretty sure there's a more idiomatic Ext.js way of doing all of this, but we're so far afield of that i doubt it's worth even trying
[16:56:01 CDT(-0500)] <pspaude1> So, it doesn't change the model object store until save correct?
[16:56:12 CDT(-0500)] <dmccallum54> that's the "save time binding" option, yeah
[16:58:19 CDT(-0500)] <dmccallum54> Ssp.controller.person.CaseloadAssignmentViewController has reams and reams (and reams) of code for doing stuff like this (late, manual form->model bindings
[16:58:35 CDT(-0500)] <dmccallum54> looks like the idiomatic Ext.js mechanism is Form.updateRecord()
[16:58:41 CDT(-0500)] <dmccallum54> which we use sparingly
[16:58:46 CDT(-0500)] <dmccallum54> in our great wisdom, no doubt
[17:00:09 CDT(-0500)] <pspaude1> Cool, I'll take a look. This seems like a good way to go, since I'm already having issues with parts not refreshing
[17:00:18 CDT(-0500)] <dmccallum54> k. thx
[17:00:22 CDT(-0500)] <pspaude1> I'll defer to the wisdom and not use it 