← Revision 1 as of 2006-01-20 20:34:20
Size: 308
Comment:
|
← Revision 2 as of 2006-01-20 21:40:37 →
Size: 1014
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 4: | Line 4: |
* IlianaAvila - The best way of getting the names of the children nodes of a metanode is by using the GINY method to get the children Nodes of a Node, and then iterating through the children to get their names using Cytoscape methods. The '''''commonname''''' attribute is not meant to be storage for the children nodes' names, it is just a possible way of labeling a metanode, which can change. I don't like the idea of having an attribute to store the names of children nodes because we would need to keep this attribute synchronized to the actual metanode membership. So if a node is no longer a child of a metanode, or a new node is added as a child, we would need to reflect this in the attribute. |
Comments on Metanode Concept Plugin
KeiichiroOno - Currently, metanode plugin uses commonname as the storage for member node names. Should we create a new attribute membernode or children to store member node names? Or just continue to use commonname ?
IlianaAvila - The best way of getting the names of the children nodes of a metanode is by using the GINY method to get the children Nodes of a Node, and then iterating through the children to get their names using Cytoscape methods. The commonname attribute is not meant to be storage for the children nodes' names, it is just a possible way of labeling a metanode, which can change. I don't like the idea of having an attribute to store the names of children nodes because we would need to keep this attribute synchronized to the actual metanode membership. So if a node is no longer a child of a metanode, or a new node is added as a child, we would need to reflect this in the attribute.