2 ms·
A box with a name would be good, but you miss one important function of saving I took pains to preserve: it is the action which turns tentative changes to the f
by JulianMorrison 18y ago
A box with a name would be good, but you miss one important function of saving I took pains to preserve: it is the action which turns tentative changes to the file into permanent ones. You want to preserve those tentative changes, but you don't want to put them in the actual file until the user commands it.
- smokinn 18y agoTrue, with current software you don't want to save tentative changes but the only reason for that is that your "undo" history is lost the instant you close a program. If you could undo changes through the entire history of the document explicitly saving becomes pointless.
- JulianMorrison 18y agoThat works for a Word document, but what if you were editing a PHP file? You neither want your changes to be immediately applied while they aren't finished, nor can the PHP interpreter handle a special format with embedded undo. Or, lets suppose you just log the undo in a hidden file alongside the original. Imagine you've edited a lot of files. All that eternal undo would pile up, and you'd end up with gigabytes wasted on useless undo logs. Plus plenty of stranded logs from moved files. No, the ability to save, to not save yet, and to abandon the undo - those are useful features.