Thx, Terry
adding to the init step
g.mytest= mytest
works
I also wonder about the best work flow for developing or modifying a
plugin
I find that if I change mytest.py (using Leo), and then close and re-
open the .leo fine with the node that enabled mytest.py, the changes
are not in effect. Note I am not re-starting a Leo instance here.
Instead, I am simply opening a new leo outline tab. But instead, if
I re-start from scratch (closing Leo and opening the outline that
enables mytest.py), the changes are in effect. I assume this is
because Leo loads the mytest.py code once only.
This feature makes it harder to test new plugin code, fix bugs, and
make changes. Is there a way to work on plugin code in a more
interactive manner. I realize I could just test the code as simple
non-plugin script, but I'd rather see the code in action as a true
plugin, especially in my plans to write some Qt GUI interfaces. The
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.
So .. can I hear some useful workflow hints and steps from those that
write plugins ?
or simply correct any misconceptions I have.
--
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.
