On Fri, Jan 6, 2012 at 11:27 PM, mdb <[email protected]> wrote: [...] > Also tell me as a neophyte Leo code contributor how to push to the > right branch. I assume I modify LeoPyRef.leo, or do I edit the file > leoCommands.py that contain the saveAs code. > I am more clueless on the unit testing step.
I don't know the answer to your other questions, but this one I do. Make a personal copy of LeoPyRef.leo to LeoPy.leo. Make your changes to leoCommands.py by editing LeoPy.leo. This is your own version of the .leo file in which you can use clones to make your own "view" of the code for study/modification. Since LeoPy.leo is invisible to bzr, your "view" of the code will not be imposed on others when you checkin. Modifications to any nodes within an @file subtree will be visible to bzr because all the @file files are part of bzr. LeoPyRef.leo only needs to change when a new @file node is needed. See the mail archives (http://groups.google.com/group/leo-editor/browse_thread/thread/3f24628c7f735c42), there are recommendations for doing development in your own local branch (i.e. not your local copy of trunk, but your own local branch). When you develop directly on the local copy of trunk and during development you need to merge other changes in, the history won't be as clean as if you had used your own branch. About unit testing. Make sure you first run the existing unit test suite from unmodified trunk. There may be a few failures due to timing issues or slight environment issues. Then run the test suite from your modified branch. If you don't introduce any new failures, then that means you haven't broken any existing functionality (at least not any functionality which is covered by unit tests). Then check the unit tests for something similar to what you are testing. Use that as an example to create your own unit test. Brian -- 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.
