On Fri, 23 Dec 2011 10:32:04 -0800 (PST) mdb <[email protected]> wrote:
> I also wonder about the best work flow for developing or modifying a > plugin I edit the code in one instance of Leo and test it in another, which I launch from the command line with python launchLeo.py del.leo so the test outline del.leo is loaded instead of the default outline(s). I end the and restart the second instance repeatedly throughout the process. For plugin initialization / integration testing that seems the most straight forward - for tree manipulation testing etc. it's probably more efficient to use a script. > one problem I foresee is understanding what is 'persistent' after code > script runs, such as what happens when the plugin init step creates > g.something. Anything you set on g is persistent for the runtime of the Leo instance, anything you set on c is persistent while that outline is loaded, but not if it's reloaded. Also, g.app.db['somekey'] and c.db['somekey'] persist between runs, the latter depends on a consistent path to the outline though. Cheers -Terry -- 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.
