A couple of links related to "versioning" just in case they serve as an inspiration:
http://coreobject.org/technotes/ (https://www.youtube.com/watch?v=UmpaAunTEQ0) https://github.com/mirage/irmin (http://roscidus.com/blog/blog/2015/04/28/cuekeeper-gitting-things-done-in-the-browser/) This is what it came to my mind when the discussion about "multithread" graphs started but not till recently I found real implementations of that idea. Too bad none of them is written in python. On Wednesday, June 1, 2016 at 9:46:37 AM UTC-4, Kent Tenney wrote: > > Only tangentially relevant: > > The versioning idea I had working briefly and am still aiming for, > I consider 'spatial' as apposed to a time travel notion. > > I had buttons labeled 'Left', 'Right', 'Up', and 'Down' > The idea is the different versions are next to each other instead > of before and after. A database held each version. > This is at the node level. > > The usage is like: > - I want to try a variation of the code in this node. > > - I press 'Right' and, if there is nothing to the right of the current > node, > a copy is made. If I'd previously created a node to the 'Right', it > is retrieved. > > - edit, edit, test ... press 'Left' > > - now I see the original node, on it's right is the variation. Same for > any > number of locations in any direction. > > - all versions exist in the DB backend, only one in the Leo file. > > I have good intentions of implementing this in a more robust way than > the proof of concept I had working at one time. I found it very simple > and convenient during the bit of testing I did, don't know if it would > really hold up long term. > > Thanks, > Kent > > On Wed, Jun 1, 2016 at 7:45 AM, Edward K. Ream <edre...@gmail.com > <javascript:>> wrote: > > I'll be working on pyflakes for at least several more days. > > > > As I do so, I am struck by how important the clone-find-all (cff, cfa, > cffm) > > command are: they provide exactly the kind of search-related views that > Leo > > needs. For me, cff is the workhorse. To my knowledge, these commands > exist > > in no other environment. > > > > As I consider how to present my pyflakes work, it occurs to me that a > > relatively easy script might be almost as useful as the clone-find > commands. > > Kent has asked for a long time for node history. The idea is to take > > history to the "limit", by allow a slideshow-like view of an entire Leo > > outline based on git commits. Hit the back button: go back in time to > see > > what the *entire* file was like at the previous commit. Hit the forward > > button, go forward in time. > > > > Imo, this is probably the only way to show what has really changed. > Diffs > > are far too scattered. Preferably, the time travel would not modify the > git > > repo. Instead, it would be better to have the script do a "lightweight" > > computation of the various versions of the outline. > > > > We'll see how feasible this would be. We must make it difficult to > revert > > to a previous time by accident... > > > > In short, I want a way of describing, for instance to the pyflakes > people, > > the steps I took getting from A to B. Diffs have no chance of doing > what I > > want. A "movie" of how pyflakes_study.leo has changed seems like the > only > > way. More generally, such a feature might be a killer feature, just > like > > cff. > > > > Edward > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "leo-editor" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to leo-editor+...@googlegroups.com <javascript:>. > > To post to this group, send email to leo-e...@googlegroups.com > <javascript:>. > > Visit this group at https://groups.google.com/group/leo-editor. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
