Charles, Having a persisted undo/redo log also implies an audit log... which is very cool.
Okay... I think we have to roll these concepts into the Record/Field stuff so that it's all nice and automagic. What are your other requirements/fantasies? Thanks, David On Mon, Oct 6, 2008 at 12:23 AM, Charles F. Munat <[EMAIL PROTECTED]> wrote: > > Yeah, I've thought about this before in the context of a sort of > infinite undo function. As you make changes in your form, they are saved > to the database. Then you can, when you navigate away, choose whether to > save them as temp edits, publish them, or delete them. If you save them > as temporary edits, you can come back and pick up where you left off, > with the undo stack intact. Then you can back up through the history. > > I've thought for a long time that as many things as possible should be > versioned (like operating systems) so that there is always an infinite > undo/redo. Since I'm building websites that are really small Content > Management Systems, this really appeals to me. > > For example, if you were editing page text, it would be nice to be able > to start by creating a working copy of the current page. Then you could > make a series of undo-able edits to the page, stopping and returning to > it whenever you wanted to. Finally, you could either publish the > finished page (i.e. make it public as a new page or replacing a current > page), or delete it. > > What you're talking about seems like a good basis for something like that. > > Chas. > > David Pollak wrote: > > > > > > TylerWeir wrote: > >> Charles, can you implement something like the auto-saving feature of > >> GoogleDocs/GMail? > >> > >> > > I really like this idea. I'm going to noodle on a way to make it a part > > of Lift... basically an form that periodically serializes from browser > > to server and allows the serialized data to be placed in a persistent > store. > > > >> This may be annoying based on whether or not it's permissible to have > >> incomplete/imperfect values. > >> > >> But if the user can have a draft status of the form, then simply save > >> the form data, mark it as jank and when they come back to edit and > >> submit you can validate/sanitize. > >> > >> Hope that helps. > >> > >> Ty > >> > >> > >> > >> > > > > > > > > > > > -- Lift, the simply functional web framework http://liftweb.net Collaborative Task Management http://much4.us Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
