Changes between Version 23 and Version 24 of TemporallyExtendedAttributes


Ignore:
Timestamp:
06/26/14 13:59:24 (3 years ago)
Author:
skyebend
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TemporallyExtendedAttributes

    v23 v24  
    136136Spec says get methods should return TEA value and spell list.  Skye thinks we should have a parameter "return.tea=FALSE" which would return this.  Otherwise return single matching value if one found, or the first (earliest) value matching query and throw Warning if multiple values match. I think this will cover the most common use cases better.  ADDED TO SPEC, IMPLEMENTED 
    137137 
    138 Since spell structures forces non-overlapping, should we add an "earliest" and "latest" rule, and if it is set don't throw warning for multiple TEA match within query spell? 
     138Since spell structures forces non-overlapping, should we add an "earliest" and "latest" rule, and if it is set don't throw warning for multiple TEA match within query spell? IMPLEMENTED 
    139139 
    140140Since these function names are getting very long, should we have short-hand versions? activate.vertex.attribute() : vAttrOn()   
     
    153153Why should get.edge.attribute.active() take an edgelist as its argument instead of a network?  
    154154 
    155 Implemented get.edge.value.active() but not get.edge.attribute.active() because the later does not have a reference for the network object so some of the speced behavior will be much more complex to implement.   
    156  
    157155As the spec states, listing active attributes is more expensive that querying the attributes (because have to query all of them to determine what is on the list).  Would it make more sense to have list* methods just return the .active attributes, and user can directly query the ones they are interested in? Spec also doesn't say if should return "test.active" or "test" for active attributes.   
    158156