On Wed, Jul 7, 2010 at 11:27 PM, Terry Brown <[email protected]> wrote: > There's also plugins/leocursor.py and the example referenced from that file. > From memory:
I had seen the somewhat similar functionality in iLeo, but not leocursor. Thanks for the pointer. > lc.Events[0].start_time == start_time attribute embedded in body text (or > unknownAttributes) of first Events child > > lc.Contact.Email == Email node under Contact node under Website node. For these examples, how does the code know whether to retrieve an attribute vs. retrieving a child node? I noticed in your examples file that the attribute access does not refer to attributes on Leo's tree, but rather attributes defined in body text using a particular syntax. that seems useful. Having the attributes hidden in the node would not have been easy for the user to edit (unless Leo has a plugin that allows arbitrary editing of node attributes). The code I shared has different intent than leocursor. Leocursor seems focused mainly on descending the tree whereas the code I shared is about surfing along any axis in the tree. Brian -- 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.
