dotasek

Decoupling this issue from previous mentions in favour of a list of possible functions to be supported (this way, I can close #72 for example, and later make an issue...

Some general thinking-out-loud: If we filter the level above from individual objects, we might get some useful functionality: ```GET /v1/networks/{networkId}/views/{viewId}/{objectType}/``` for example, is a level up from ```GET /v1/networks/{networkId}/views/{viewId}/{objectType}/{objectId}```, and...

This is related to https://github.com/cytoscape/cyREST/issues/64 in that we're trying to do a lot of work with a file, stream, or url, AND support the existing JSON formats from the RESTful...

This, along with #64, could be taken care of by using some of the code used in the drag and drop functionality.

There's still discussion of the successor to the DING rendering engine, which, depending on how its level of details is handled, may deviate from the current implementation. This complicates the...

@scootermorris did however mention that other level of detail controls can be handled through render.* properties in Cytoscape preferences. So implementing #13 would give us added value for level of...

To some extent, GET/PUT already exists, in that Zoom is provided by the NETWORK_SCALE_FACTOR visual property, which can be accessed via Network Views operations. This would make Zooming to selection...

Also The Google uses PATCH: https://developers.google.com/drive/api/v2/reference/#Children

https://developers.google.com/tasks/performance#patch