On Mon, May 28, 2012 at 2:51 AM, tfer <[email protected]> wrote: > Even rougher second draft:
Excellent. Now you are talking about why Leo isn't just another IDE or just another outliner. > Special headlines can be used to designated parts of Leo outlines that > correspond to external text > files. Such headlines can have files generated from their subtrees by > template(s) contained in body text. These templates determine how the file > will be assembled from the descendent nodes. Alternatively, other forms of > these headlines can read in entire files and dissect them into outlines. > > One of the big ideas of Leo is that the body text in nodes is data, an > analogy can be made to the cells in spreadsheets, here the data is not in a > grid, but held in graphs, each node having a parent, possible siblings, and > descendents. Leo has a dead simple DOM held in the python data structures > that is easily interacted with via python. All sorts of transforms, > summarizing, and synthesizing are doable via python. DOM's aren't held in data structures, they are the means of accessing the data structures. So I'd say: Leo scripts use a dead simple DOM (Document Object Model) to access all the data in Leo outlines. Examples: p is the presently selected outline node, p.b and p.h are the node's body text and headline and p.v is the underlying data object for the node. > More than just text can be held in a node, Leo has a way to add whatever you > like via, what are called, "unknown attributes", or uA's. These are unknown > in the sense that Leo is set up to deal with text, but through through > detectors uA's are found, made to persist, and, via custom or plug-in > coding dealt with. It's ok to call them user attributes. I'd rewrite the last paragraph something like this: You can add addition *user data* (uA's for short) to any node. uA's can be additional text, including references to external resources, or even binary data. Once associated with a node, Leo will save the uA to the .leo file, and restore the uA when you next load the file. uA's persist arbitrary data for plugins or scripts. Leo scripts access uA's with p.v.u. Again, you are making excellent progress on the abstract. This is important. I've learned from reading thousands of abstracts in science journals that abstracts serve multiple functions: 1. They tell referees and eventual readers why the article is important. 2. They teach both referees and eventual readers something about the overall field covered by the main article. 3. They summarize the article so that all readers will take away the essential points without having to delve into the details in the main article. This your abstract now does. 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.
