On Fri, Feb 27, 2009 at 4:45 PM, Kent Tenney <[email protected]> wrote:
> I'm unable to appreciate the details, but I sense a "perfect as enemy of good" > type situation. Now we are coming to my favourite "worse is better" approach ;-). Here's yet another wild idea: In a limited sense, if we assumed program source (as imported with @auto) as target of restructuring, we could encode the structure by using *hash value of function definition line * (plus thin file name, as possibly class name in python files) as gnx. That way, we could have our own structure in the .leo file and our private files, and create clones to the nodes, while still being able to grab updates from others (even updates that changed the function order). I may be going completely on the limb here. It could just be something to complement the @shadow, making it more robust / error tolerant. In any case, I don't think we can abandon @thin nodes. -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
