> I agree. The idea is that Leo detects the clone problem, unclones the > effected cloned nodes, and then informs the user that they have to > resolve the problem by creating a "Task" node containing cloned nodes.
An excellent idea. I would like to add to that: Sometimes to decide what to do with the broken clone, you do need the context. Therefore I (also) suggest adding these UI enhancements: 1. Mark and enumerate broken clones of the same clone with e.g. blue numbers. Each number is a version of the clone text, so we might have 2 nodes with version 1 of the clone and 3 nodes with version 2 (all 5 nodes originated from the same clone). 2. Use "goto-broken-clone", and "goto-next-clone" to examine the broken clones. "Goto-next-clone" should go to the next node that is a clone of the current node, not to any next clone node. 3. For each broken clone node/version you can decide a. Unclone this node (convert the node to a regular node). c. Make this node a clone of version x (discard the current node text). b. Make this version a clone of version x (the text of all nodes with this version is discarded). In the end we have either the original clone group with the text decided by the user, or a few clone groups/nodes with different text, also determined by the user. And Leo never obfuscate the true content of a file it loaded (by showing the text of the last loaded clone text). Gil
-- 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.
