Dynamic data loading:
-For a given ePlant object (notably a gene), create functions for loading partial information about the object (e.g. annotation, localization, etc.) and set up status indicators tracking whether data are (1) not loaded, (2) being loaded or (3) loaded.
-This would reduce unnecessary loading of data when only a part of it is needed, which may increase latency (for example, if data loading includes SUBA localization, then the query is noticeably slow)
Event listeners:
-For ZUI and ePlant objects with event-driven properties, allow multiple event listeners to be bound to a given event. The object should have an eventListeners attribute, with arrays of event listeners wrapped in it.
-For example:
var object = {
eventListeners: {
click: [Array of listeners],
mouseover: [Array of listeners],
...
}
};
-I think this will be useful in the future. If not, it is still a good feature to have (native JavaScript DOM objects and Cytoscape.js all support this feature).
Dynamic data loading: -For a given ePlant object (notably a gene), create functions for loading partial information about the object (e.g. annotation, localization, etc.) and set up status indicators tracking whether data are (1) not loaded, (2) being loaded or (3) loaded. -This would reduce unnecessary loading of data when only a part of it is needed, which may increase latency (for example, if data loading includes SUBA localization, then the query is noticeably slow)
Event listeners: -For ZUI and ePlant objects with event-driven properties, allow multiple event listeners to be bound to a given event. The object should have an eventListeners attribute, with arrays of event listeners wrapped in it. -For example:
-I think this will be useful in the future. If not, it is still a good feature to have (native JavaScript DOM objects and Cytoscape.js all support this feature).