I know unified nodes have been "tried" previously (though I don't know the exact results of the experiment).
I think it might be cool to move forward with this after the release. It should get rid of lots of contortions in the codebase, and most importantly, the vnodes really are not necessary in any sense to represent clones (i.e. it's just one new layer that can get broken). Moving to the unified nodes should simplify leo's conceptual model significantly, and eliminate the need to use positions for everything. As opposed to positions, tnodes - Have identity (gnx) - Can be cached -- 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 -~----------~----~----~----~------~----~------~--~---
