Hi,

Core object provides outlining with node versioning:

http://coreobject.org/

Still on early stages, but I think that it helps into making a point about these possibilities (which doesn't mean that they should be implemented on Leo ;-) ).

Cheers,

Offray


On 23/01/17 13:39, john lunzer wrote:
Been mostly on the sidelines on this one, mostly because I didn't have time to think about it.

I think node versioning is a potentially "killer app". 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 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.

I'm going to have to agree with Terry. In this context Fossil is a backend. The concepts of document/node versioning need to be abstracted to fit Leo and then a backend can be plugged into what Leo is trying to accomplish.

On Saturday, January 21, 2017 at 6:11:29 PM UTC-5, Edward K. Ream wrote:

    On Tue, Jan 17, 2017 at 9:32 AM, Offray Vladimir Luna Cárdenas
    <[email protected] <javascript:>> wrote:

        ​​
        Richard Hipp, Fossil and SQLite author, makes that distinction
        and about the "pile of files" database (like the .git folder)
        instead of the single file approach[2]. There is a lot of
        querying capabilities of the last one, as you can see on [4]

        [2] https://www.youtube.com/watch?v=8y_ABXwYtuc
        <https://www.youtube.com/watch?v=8y_ABXwYtuc>
        [3] https://www.youtube.com/watch?v=ghtpJnrdgbo
        <https://www.youtube.com/watch?v=ghtpJnrdgbo>
        [4]
        http://fossil-scm.org/index.html/doc/trunk/www/webpage-ex.md
        <http://fossil-scm.org/index.html/doc/trunk/www/webpage-ex.md>


            If the emphasis is on node versioning, there's this:

            https://groups.google.com/d/msg/leo-editor/LIUGtgP8T_s/oSQD4RQGeogJ
            
<https://groups.google.com/d/msg/leo-editor/LIUGtgP8T_s/oSQD4RQGeogJ>

            which points to a couple of older posts.


    ​I have copied these links and watch them soon.

    As just mentioned in another thread, fossil stuff will likely
    happen later this year.  That is, I personally have higher
    priority work.

    I would encourage everyone interested in fossil to continue their
    work, even as I work on other things.  And later, if I seem to
    forget fossil, please remind me ;-)

    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] <mailto:[email protected]>. To post to this group, send email to [email protected] <mailto:[email protected]>.
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 [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.

Reply via email to