I have a new gripe with the web interface of web2py. I lost a measurable amount of work while editing a db schema tonight. I had the editor up on db.py when I was interrupted. A couple of hours later I returned to the editor and put in about 20 minutes of concentrated effort. When I pressed the "save" button, I was taken back to the "log in" dialog. After logging in, the editor returned, but without my efforts recorded. My work was lost.
I think if a timeout occurs, it should lock or somehow render the edit page immediately unusable so that I cannot enter new data. Or, even better, the timeout should be prevented while the editor is active. This is not an easy subject, I understand, But losing any amount of work is highly undesirable and should be prevented. It is most annoying that the work is just gone forever, with no ability to retrieve it from the browser at all. This is one reason why many people don't trust web editors -- they are too prone to lose work. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
