I am beginning to feel that something basic is missing from Leo. As Ville recently said, it's too hard to share data, especially .leo files. Sentinels are not the issue: we would still have the problem even if no one were bothered by sentinels.
This problem can not be solved by adding "ordinary" features. And deleting clones is also not a solution :-) This is a good time to confront this issue. The relevant parts of Leo's internals are "perfect": we have the simplest possible internal data model (the one-node world), and the simplest possible sentinels. So it's clear that "ordinary" optimizations will not suffice either. My unease increased after adding the "Recovered Nodes" feature. They shows how often Leo's load process is not as expected. I don't have a clear idea of the way forward. Something more is needed, but I couldn't say what. I suspect that new ideas will involve re-imagining how Leo interacts with the larger world. I'll be adding to this thread from time to time. I encourage any and all ideas. 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.
