v.viewDict is an implementation detail. An alternative is to introduce 'edges' as separate first class construct, and then bundle edge type in that construct (color, half-clone, backlink, normal tree edge...).
This scheme (of edges overall) was discussed earlier, when talking about database storage for Leo (2 sql tables - Nodes and Edges) On Mar 4, 2012 2:26 PM, "Edward K. Ream" <[email protected]> wrote: > On Sat, Mar 3, 2012 at 1:00 PM, Seth Johnson <[email protected]> > wrote: > > > I will be very interested in how this shapes up and how you start > > looking at collaboration, distribution and versioning. (BTW, I would > > designate those "organizations" by unique keys for their use type, > > link type and particular use, as well as designating the states they > > reside in.) > > Right. These would be the keys to v.viewDict. > > Edward > > -- > 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. > > -- 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.
