On Jul 8, 2:55 pm, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> The trunk now contains the first incarnation of leoShadow.py. This
> contains revised/refactored code from the mod_shadow plugin.
I have begun the final phase of the project, the integration of the
mod_shadow plugin code directly into Leo's core.
This is an excellent opportunity to use the principles of extreme
programming. Much of the code consists of munging file and path
names. I've created 7 helper methods that handle these picky and
important details. These methods allow much more thorough error
checking and reporting. I developed each method hand in hand with a
corresponding unit test in test.leo. Do so actually *increases* the
speed of development. Those familiar with TDD will know why. In
essence, each unit test becomes the quickest, easiest way to test and
modify the code.
So this is good progress. I had forgotten that Bernhard had requested
that I put hooks for the shadow plugin in Leo's atFile logic. After
the code is revised, the changeover will simply be a matter of
replacing the hooks with the corresponding code from the shadow
plugin. It may happen today.
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
-~----------~----~----~----~------~----~------~--~---
