On Tue, May 29, 2012 at 6:47 AM, Edward K. Ream <[email protected]> wrote:
> It may take days, weeks or months of experimentation before I > can discover exactly what makes each program tick. Otoh, the experimentation will yield immediate results. A new module, say leoTools.py, will probably contain support classes for rope and coverage and maybe even 2to3 and pylint. These classes will handle common tasks for @command nodes. For example, one can imaging a set of @command nodes that users could write that will allow refactoring of a set of files defined in each @command node. rope has a "virtual file interface" that would allow refactorings to be done directly in Leo outlines. leoTools.py would be the place to define the virtual file interface. Similarly, leoTools.py could provide common code used in, say, "@test coverage" in unitTest.py. Finally, Leo could offer a set of 2to3 commands for converting selected nodes of a Leo outline. These are just first thoughts: I expect quite a bit of activity on these fronts in the coming days and weeks. Edward -- 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.
