When I'm writing Leo scripts, I spend much time figuring
out what function to use: for child related methods:
for item in dir(c):
if "hild" in item:
g.es(item)
Sometimes I can identify the right method to use by
name, sometimes it takes trial and error.
I'm forever doing this for dir(c) dir(p) dir(g) ...
g.es(len(dir(c)))
reports 538
I'm trying to write simple scripts and faced with the
complexity of the entire core API.
I'd welcome a "user space" API which wrapped the
current "kernel space" API.
I tend to think of it as modeled after file system commands,
if I need a new node, I want to write:
touch("headline", "body") and get a sibling.
A child could be mknode("headline", "body")
etc.
This API would involve opinions of developers,
giving scripters a simple set of tools. As always, those with
different opinions would need to look under the hood and
call "kernel space" but many would never do that,
they would write the scripts they need within the
confines of "user space"
Thanks,
Kent
--
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.
