Hi Stefan,
actually what you refer to as the "quick and dirty" solution is probably the only feasible one: to store a copy of the entry in the browser and restore that copy with a "cancel" button.
Otherwise you would need a full-fledged revision management, to deal with multiple copies of the same entry open in several browsers.
Yet, that does not solve the "problem" of a crashed/closed browser: the entries will go back to drafts and might got overlooked. As you rightly say: this is a feature, not a bug.
This is only a problem when editing existing entries, not for new entries. Maybe a note right of the button "delete" would help, in case you edit an old entry: "This entry is now a draft; press Submit to make it a real entry again".
But as a first step, it might be worthwhile to document this behaviour in the ELOG "User's Guide". Drafts are currently only mentioned in the elogd.cfg syntax pages under "Save drafts" and "autosave". I'll try to propose a text :-)
Kind Regards
Andreas
| Stefan Ritt wrote: |
|
The problem is that the elog database does not allow for a copy of an entry before you make modifications (and therefore get a "draft"). This is actually very simila to other note taking programs. I use Evernote, which constantly synchronizes between devices, and there I also cannot go back to the version before I started making modification. What one would need is a version system (and Evernote has one), so you can go back to the previous verison, the pre-previous version and so on. But this requires a complete redesign of the elog database.
A quick and dirty solution would be to store the origianal entry inside the browser (using JavaScript). You could then restore the initial version with a "cancel" button. But this mechanism relies then on the browser. If you just leave the page, there is no way the browser can put back the old version.
Stefan
| Andreas Luedeke wrote: |
|
If I edit an old entry, and do some mistake while editing, then there is currently no way to savely discard the changes.
The problem is that the entry will become a draft: if I close the window without saving, then the whole entry is gone: it will be converted into a draft entry. But the draft does contain my changes, it is not the originally saved entry!
The draft mechanism should keep a copy of the entry before I opened it in edit mode, and allow to go back to that copy. The edit form has currently the buttons "Submit", "Save", "Preview" and "Delete"; it should have in addition the button "Cancel", that just closes the edit window without saving the entry and even deleting the draft that was saved while the entry was modified. This should bring you back to the previous list view.
Is anyone out there in favour of this change?
|
|
|