Well, this gives me a lot to think about. I've been more or less assuming the idea of one zettel/one node as being a limiting one, but perhaps it's the opposite, given all the capabilities of a node, hardly any of which I am familiar with. And that's what I need to do: dig in and get familiar with the organizational/accessing capabilities of Leo.
@EKR says Leo is the ultimate filing cabinet and I must dig into that instead of sitting here on the sidelines waiting for something to happen. I expect there are one or more tutorials somewhere dealing particularly with those aspects while leaving aside the programmer's aspects. I'll look around but if someone can point me ... One thing I wish I understood better is the acyclic graph model, how that plays out in Leo and what it accomplishes for us in organization/linking. And Thomas, perhaps I need to read your papers on semantic processing (haven't done so yet), as it seems that's more or less what the zettelkasten model offers (maybe the Leo model, in fact), and it appears you are bringing the body of your work to bear on this project. Which probably makes you nearly the perfect person to be working on this. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/03f48535-c322-44f5-afb8-e0e66bb2a453%40googlegroups.com.
