On Wed, 30 Nov 2011 00:31:33 -0800 (PST) HansBKK <[email protected]> wrote:
> My goal is to *not* make use of structures that are specific to Leo, > so if fifteen years from now I'm not using Leo anymore, the next > 50,000 chunks of text I've captured/written won't need a programmer to > continue being accessible, relatively easy to transform into whatever > I'll be using next. Fundamentally Leo stores data in XML. It's always going to be possible to get data back out of a .leo file without Leo, although it might require tools / skills somewhat different from plain text. But storing a tree with clones in plain text would make the plain text so sentinel heavy it might as well be XML... > In the browsing/googling I've been doing since, maybe the idea of > "UNL" are a good approach? Whatever I do, I'll need to keep the link > source strings in sync with the target name/location - I would just > rather avoid having to remember to do a full grep search and replace > manually every time I edit a heading string. ok, I was perhaps heading off in the wrong direction before, I think I see what your saying now. You want some kind of text based link which doesn't break when you edit the components (node headlines) which it targets. UNLs are an example of a text base link, but they break when you edit the headlines they reference. I can't see a simple way to make them unbreakable without using clones or backlinks, which aren't text based. I guess you could have a routine which checks for impacted UNLs every time you edit a headline, or re-arrange nodes (which will also break UNLs). Perhaps the document could be scanned for UNLs, the internal node IDs of the nodes they target noted, and then UNLs could be updated using these node IDs as needed. Interesting thought. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
