Hi Edward, I don't know how often this has been asked: What if options would not be set via head or body of a node but be attributes of this node? Of course not Class attributes but attributes of specific instances to keep everything smaller.
Why I'm asking: Today I tried to integrate my code nodes into my yet to be written bachelor-thesis. And I found out: 1) how shortsighted I am (unfortunately a often returning insight) 2) how to do it Besides being superhappy now I still wonder about the way to set the options. One benefit would be (aside from having a cleaner tree and using title and body for what they are, that is title and body) that one could imagine other viewers of the codebase. For example one could have Nodes for developers or versions or dates...... A viewer that would help with project development would then associate developers and their written code. A viewer that would help with project management would organize tasks or calendars or dates or whatnot. A viewer that would help with file management would show directories and files (and maybe lines or shapes or sounds ....) as nodes .... What do you think ? Have viewers that can not be sure that a certain attribute even exist but try nevertheless? Stupid and useless or worth it ? Greetings, Holger Am Mittwoch, 29. Juli 2015 15:07:44 UTC+2 schrieb Edward K. Ream: > > In my mind, all essential aspects of Leo are complete. Sure, there will > always be improvements to be made, and I intend to keep making them, but > now that that we have @clean the most important work is complete. > > Imo, Leo is good enough as it is. What's not so good is outreach to the > rest of the world. Marketing, if you will. > > An excellent suggestion is to reach out to magazine editors, get them > excited, and have them write or commission articles about Leo. I think > this is a great idea, but we haven't made much progress on this front. > > Recently I've been thinking about creating "true" Leo modes for emacs and > vim. This would be a lot of work. In essence, this would create Emacs and > Vim guis. All other code must remain the same, and the gui must (mostly) > be written in Python, not elisp or vim script. > > Your comments, please. > > 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
