On Apr 13, 7:20 am, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> It appears that Leo will, relatively soon, move to the unified-node world. Compatibility with existing code and scripts should be no big deal. Indeed, unified nodes will contain .v and .t ivars, inited in the ctor as follows: self.v = self self.t = self That is for any node n, n.v == n, n.t == n, n.v.t == n. In other words, if there is only one kind of node, the problem of distinguishing between vnodes and tnodes becomes pretty easy :-) Similarly for positions. p.v == p.n == p.v.t. I'll probably write scripts to eliminate references to v and t from Leo's core (and plugins) but it is my intention that old scripts works as before. There will be instances where this could produce weird, inefficient or even incorrect code. We shall see... Edward P.S. I just finished talking to my brother Speed. He points out that several interesting projects use DAG's, and that work is happening in devising a DAG-based file format for holograms. DAG's are used in 3-D cad formats. Apparently representing holograms as DAG's improves compression. Anyway, a simplified, more flexible format for .leo files could make Leo relevant for such projects. This will encourage me to make the format of .leo files as straightforward, "honest", (optionally) compressible and user-customizable as possible. EKR --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
