> > > I envisioned this and in addition "saving" as simply tagging one of these > revisions. > > I am thinking about having Leo send some tag along with the snapshot. For example somewhere in Leo UI or in one special node user is asked to write short description of what task is he/she doing now. Snapshots are sent along with this description and later user can search for the outline as it was when some particular task was worked on.
Your demo is missing a powerful demonstration of this feature, the "over > the shoulder" demonstration. What is required is a "play" button. If you > slide the outline slider back in time and then provide a play button which > moves the slider forward after a time increment as well as visually jumps > to the largest changes you can "look over the shoulder" of a developer as > they develop. > Currently there is no single timeline of history that could be played forward or backward. Each node has it's own timeline, and outline itself has timeline too. Those timelines can be synchronized by timestamps, but for real looking over developer's shoulder feel, there has to be saved some additional data like: which node was selected, where was the cursor in the body, vertical scrollbar positions, ... It would be straightforward to add those information though. My original intention was just to provide unlimited, persistent undo/redo history. But more and more ideas come every day. Adding tag support would allow developer to see time spent on some tasks. Analyzing those timings developer can improve future predictions of how long will it take to do this or that. Currently I am thinking about incorporating my other Rust project (the one for reading xml Leo outlines and external files), in order to allow Leo not only to send snapshots but also to get snapshots of fully opened and loaded outlines along with belonging external files. That would reduce load time considerably. The largest external file in the Leo core is leo/test/activeUnitTests.txt, and on my machine it is loaded in about 6.4ms. This task is suitable for utilizing several CPU cores where Rust shines. I expect that loading an outline with 100 average external files can be done in less than 300ms. I have a lot of ideas, but also running out of time. :-( Vitalije -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/fa16ba4d-e8fa-45b3-86a4-8cf40cc6650a%40googlegroups.com.
