On Sep 2, 4:02 am, Offray Vladimir Luna Cárdenas <[email protected]> wrote:
> In my dreams, I would like to see Leo as a kind of backend for trees and > clones in the web. I too have dreams--they are muddy at present. The central area of confusion is what constitutes a **sharable item**. So for in Leo, these have been clones. That is, in Leo we share by *identity*. This creates unbreakable links, which is essential for Leo's underlying node structure. However, I am beginning to feel uncomfortable with identity as the basis of user-centric sharing. Instead, I am intrigued with sharing by *relationship*. Relationships (user-defined patterns) change as data (content) changes, but perhaps this is more a benefit than a problem. Identity has severe problems: when "identical" nodes are written to several files, changing some but not all of the "identical" nodes creates an **identity crisis**. As a practical matter, source code repositories have no built-in tools to handle either identities or identify crises. In short, Leo's clones are rock solid internally, but cause no end of grief externally. Let's imagine a world without *external* clones. There is a great divide: A. External nodes have no identity. Leo's external files become isomorphic (identical) to emacs org-mode files. B. External nodes continue to have identity (gnx's in node sentinels). The problem with B is, as I said above, there are no tools to handle identity crises. Leo itself has makeshift rules (conflict trees), but these are problematic. Furthermore, I dislike using clones in programming as a substitute for methods. Alas, we are stuck with html :-) **Important**: Leo's hidden machinery (special uA's in root @file nodes) provides a *breakable* way of associating attributes with external files. If (a big if) we can live with links that can break (say as the result of updating from the repository) we could allow still allow clones for html programming (or any other purpose) while banishing external identity. If we banish external identity, @auto nodes become equivalent (as far as sharing goes) to @file nodes. There would also be no need for @shadow, and probably little need for @nosent and @asis. > would be nice to have Leo documents rendered on the web. Another of my dreams. A big project, but you have made a good start with dynatree. Edward -- 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.
