On Mon, Jan 23, 2017 at 12:39 PM, john lunzer <[email protected]> wrote:
I think node versioning is a potentially "killer app". > Maybe. I recently used gitk <filename> to review seemingly mysterious changes to a single file. Not "killer", by any means, but useful enough. > Having a fully automatic document versioning system at the .leo file level > and node level would be a turbo boost in project organization and > development tracking, a fine-grained full-fledged document history. At this > level you could truly be able to see a piece of software unfold and develop > in ways that aren't foreseeable with manual operation. > I am skeptical about such grand claims. The real "action" consists of ideas. They get translated into a gazillion small steps. It's almost certainly impossible to go backwards from code to concept. My present opinion, lightly held, is that if you can't deduce what is happening from the checkin logs, you have no chance of doing so from the actual code. > I think it would also provide robustness to the concept of "undo". Being > able to "undo" node level edits at any time and location is an awesome > idea. There are potential statistical and visualization concepts that can > aid development as well. > Again, I am skeptical. I suppose I could be persuaded by nifty visualizations. 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
