Your option 1 is timed commit, so you probably mean option 2. The
difference is that you're proposing committing every time an
attribute has been changed, whereas I was proposing a save only
once the user selected another item to display, even when multiple
attributes have been changed in the DV.
Sorry, you're right -- I confused option 1 and 2.
I suspect that committing every time the attribute is changed, i.e.
when you exit editing a field, might be a little better than
committing when you switch to as new item and wouldn't be that much
slower. Of course to really know, it's probably worth trying both.
If I get some time to code it, maybe I could get you to help test it
for me.
But this would probably also need a timer that would commit
anyways after a minute if no further modifications were made but
the user never navigated away.
This is option 2 below
So it sounds like you prefer both options, right?
I was suggesting having the timed commit as a fallback, but commit
changes immediately if another item has been selected. Although it
is possible that this would not be worth the extra complexity.
I still need to look into this a bit, but I think that it might not
be very complicated.
John
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
