Just to provide some thoughts about valuespace:
ILeo has the "LeoWorkbook" concept. However, that quickly creates a
setup which is hard to manage, because it requires you to execute
scripts in certain sequence, perhaps doing some work in ipython shell,
etc.
Valuespace aims to make the same problem domain (sort of using leo
like a spreadsheet) easier to tackle. I think it is easier to approach
- just write your "application" in a tree and run vs-update.
"Application" consists of two passes:
1. Evaluate the whole leo tree in tree-order, with following rules:
Headline "@= foo" => assign body to foo
@a => evaluate body of parent, with following rules:
"@x foo()" => execute one line of python code
@x {
import os
print "many"
print "lines"
@x }
@x =foo {
assign
many
lines
to variable foo
@x }
Pass 2: evaluate @r nodes.
Everything else is ignored. This lets you "annotate" large bodies of
text with python code, extracting and processing information according
to your needs.
Everything is run in namepace g.vs, so you can refer to g.vs.foo in
your ctrl+b scripts. Namespace persists, unless you do vs-reset.
The alternative, doing things in leo scripts that traverses outline
itself becomes cumbersome quite easily.
--
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.
