I manged to inspect the code and figure out what changes I needed to make, ipython demos (kind of an interactive slideshow where you run canned python code in ipython, with an opportunity to explore what you like after "running" each slide).
The active path plugin was very helpful once I got the plugin settings correct, (had to look at the ones in leoSetting.leo to 'grok' it, did not understand the @data usage until after that). The recursive load of all the python files proved a little counter productive and lead to a bunch of warnings. What worked better was apply load recursively to the @path node without any auto loading of *.py files, that gave me the overall structure of the package. I just loaded the files I needed to inspect. It also helped to be running ipython in a console alongside this to explore the code. I can see thing I like to add to active_path plugin. For instance, on the "package tree" of filenames, it would be useful to be able to load in module docstrings into the empty bodies of *.py files, (and write them back out as you create/alter them after exploring the code), these seem to be lacking in ipython. Tom -- 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.
