2 ms·
Mostly for persistence. Save it into a file, restart the program and load the entire state losslessly. You can also send it to a server or do whatever you want.
by JetSpiegel 9y ago
Mostly for persistence. Save it into a file, restart the program and load the entire state losslessly. You can also send it to a server or do whatever you want.
With the correct widget types, the business state IS the GUI state and can be treated the same.
For simple GUIs, there will be no redundancies and no undefined states.
- vram22 9y ago>Mostly for persistence. Save it into a file, restart the program and load the entire state losslessly. Interesting, and makes sense. Coincidentally, just today I was remembering the feature of the Palm IV or V that I used to have (also the Palm Zire later, but don't remember if the latter also had the feature), of saving app state, so that when you turn it on again, all apps would be running (or was it only single-app-at-a-time, don't remember) with their exact state preserved from when you shut it down, down to even the last characters entered in the middle of a field in a form that you were filling in, for example. Also it was an almost instant-on kind of device. And was wishing that my PC / laptop could be that way too. I had read a while ago that some work had been done on much faster booting times for Linux or other OS-based PCs. Don't know the current status of such efforts.