On Thu, Oct 24, 2013 at 9:06 AM, Kent Tenney <[email protected]> wrote:
> I still think 'looking over Edwards shoulder' is the only way
> I will be able to fully appreciate the benefit of clones ...
>
I agree. Otoh, step-by-step "hints" might suffice for some.
A preview: I make a clone of anything I'm working on, and move it to the
*last* node of the outline. This can be a multi-step process.
Suppose, as will soon happen, that I am going to fix a bug in Leo's @shadow
logic.
1. Find @file leoShadow.py in leoPy.leo
2. Clone same.
3 Move clone to last node of the outline, thereby closing all nodes.
This allows easy access to the file that probably contains all the
to-be-changed code.
4. Opened the cloned copy of @file leoShadow.py.
Note: the origin node would expand if it were visible, but it's not.
5. Look around :-) I don't remember details.
6. Clone class shadowController and move it to the last outline node.
Once again, all outline nodes are closed.
The advantage of doing this is that the <<docstring>> and <<imports>>
sections unlikely to be changed, so we may as well *focus* on the
shadowController.
7. Look around for nodes are tree relating the the bug.
8 Repeat this process each node that is related to the bug:
clone it and move to the last node of the outline.
9 When all relevant nodes have been discovered, change the clones at the
top level, thereby changing the nodes in @file leoShadow.py.
10. When the project is done, document what has happened *without* using
clones, and just *delete* all the cloned top-level nodes.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
