On Tue, Oct 4, 2011 at 8:14 AM, Kent Tenney <[email protected]> wrote: > Possibly related. > > My interest in LeoFS started with the desire for a list of nodes sorted by > when I last created, edited and viewed them. > (I tend to be working on several things at once, want to retrieve my prior > train of thought effortlessly) > > I like the idea of an sqlite file which has a row for each node, changing > a node creates a new row. This will provide timelining and versioning.
Very interesting. We are getting lots of provocative ideas these days. As I said in my comment to Matt, it will be challenging to get the proper granularity for undo. I suspect the smallest level of granularity that could form the basis of a new kind of undo would be an entire editing session for a single node. That is, we would create a snap shot of a node whenever we leave the node. There is an interesting discussion of simplicity in this month's issue of Scientific American: Big Progress on the Little Things. The point is that simplicity of the iPhone etc is trumping feature-itis. This applies to every aspect of Leo. It may be that our discussions will lead to some spectacular collapse in complexity. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
