On Sat, Mar 26, 2016 at 11:18 AM, 'Terry Brown' via leo-editor < [email protected]> wrote:
On Sat, 26 Mar 2016 06:15:22 -0700 (PDT) > "Edward K. Ream" <[email protected]> wrote: > > > For example, a documentation script might "scrape" one or more .leo > > files for data, and then create nodes that reference the scraped data. > > My point, > > the original functionality valuespace is sort of a tree scraping data > collecting kind of animal, perhaps more sophisticated than what you're > looking for, but worth familiarity in terms of how it tags data for > collection and puts it back in the tree etc. > Thanks for this. I've just added a Leonine post-it note to study valuespace again. In any case, you are making my point that Leo can do really impressive things without the need to add new kinds of clones. I'm starting to get the feeling that might be possible to do auto-completion using live Python objects. This inkling (no more than that at present) was inspired by my new testing pattern: - @test node (contains driver code, with @others) - Clone of the class or classes under test. The code in the @test node gets access to the *latest* code *without *reload. This works, provided the class under test can be properly inited, which usually it can be. This testing strategy is kinda similar to creating a live class for autocompletion... 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
