On Tue, 8 Jul 2014 23:47:57 +0200 Fidel N <fidelpe...@gmail.com> wrote:
> About the gnx, I wanted to say something Edward didnt. Not a > complaint or anything, but from my point of view, the only feature > they are missing: > > When you cut an outline, then paste it otherwhere (same or other Just in case anyone else misses the point here, took me a while to work out what you meant, *cut* and paste..., when you paste only once, ideally could avoid losing the gnxs. Copy paste, or cut paste paste, would have to create new gnxs (at least on the second paste). Is tracking the number of pastes after a cut and only creating new gnxs on the second and subsequent pastes reasonable? Cheers -Terry > file), you loose the gnx of every node in that outline. > That prevents you from using gnx as a stable reference since cut and > paste is very frequent in any "leonine" workflow. > > Thats, IMO, the only (and big) weakness of gnx's. > > > On Tue, Jul 8, 2014 at 9:46 PM, Ville M. Vainio <vivai...@gmail.com> > wrote: > > > Just as a quick stab - I was looking at camlistore through last few > > days. > > > > https://camlistore.org/ > > > > It may be more natural fit for Leo outline management than git (as > > it's more about direct content addressable content access than > > git). I have had sketchy plans of reinventing something like > > camlistore from scratch, so it's something I will be looking into > > anyway. > > > > > > On Tue, Jul 8, 2014 at 3:46 PM, Edward K. Ream <edream...@gmail.com> > > wrote: > > > >> I've been studying the pro git book: http://git-scm.com/book and > >> am now closely studying the internals chapter: > >> http://git-scm.com/book/en/Git-Internals > >> > >> Stimulated by Kent's work with db's, the question arises: is it > >> possible to represent a Leo outline as a git object? > >> > >> I believe the answer is yes, and not just in the trivial sense > >> that any content is a blob: > >> > >> - Every node's gnx, headline, body text and uA (and anything else) > >> has a unique (sha-1) hash. > >> - We could define (git) tree objects that contain the following > >> entries: gnx, headline, body text, uA, parents, children. > >> - Empty uA's would be represented by the hash for an empty string. > >> - Parents and children entries would be other git tree objects. > >> > >> In this way, we could use git plumbing to build a git tree object > >> representing an entire outline, with all the data contained in > >> a .leo file. > >> > >> In other words, even though git is *content* addressable, the > >> content can contain gnx's, so that nodes *identities* are > >> preserved. > >> > >> Don't know whether any of this will be helpful in the current > >> creative ferment, but I thought I would point it out. > >> > >> 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+unsubscr...@googlegroups.com. > >> To post to this group, send email to leo-editor@googlegroups.com. > >> Visit this group at http://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 http://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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
