Enable a transform function to be registered on an asset, to be applied to the asset just before it is served in a response to "getAsset".

Metadata on the funct...

Info on how the asset is stored on the server, eg.

• path to where attachments may be fetched

Documented here: http://scenejs.wikispaces.com/Asset+Server+API+-+...

Support assets parsed from OBJ and MTL files.

Metadata:

• Spatial extends
• MTL libs
• Stats on textures, vertices, face counts
• Attachments

Create demo where visitor can fly through the AssetMap kd-tree and look at assets

Parsers require update after these SceneJS API changes:

Remove "cfg" from node configs: https://xeolabs.lighthouseapp.com/projects/50643/tickets/162-remove...
...

Now only returns JSON subgraph, with JSONP support. Remove module and socket packaging.

Replace Collada parser with one that creates an optimal subgraph:

• generates the new JSON API
• parsing only the default <visual_scene>
• creates unfolded instance-...

Serve symbol assets that are then instanced by kd-nodes in the client

Specify flag when getting kd-tree BoundingBoxes to make them visible:

{
    cmd: "getAssetMapBoundingBoxes",
    showBoxes : true
}

Server will automatically create one or more simpler versions of each asset, using a mesh simplification algorithm.

This could be done either at

• the parsing ph...

Make a badge widget on jQuery that shows the current status of the Asset Server.

Perhaps showing:

• Availability status
• Asset count
• Load

Eg.

• Available
• Very bus...

Assets should not be provided in its actual responses to Sockets - potentially it might be supplying the whole massive scene if the viewpoint was far enough bac...

Allow a kd-tree to be shared between browser and Asset Server

The SceneJS Asset Server can provide assets (models) to client scene graphs through WebSockets. Ea...

Create new delete command:

{
    cmd: "deleteAsset",
    id: "com.foo.models.myAsset"
}

This way the store will have everything it needs to re-build its assets whenever extended to extract new features from source files.

This way we'll be able to get an easy dump of all the commands to reissue if we need to rebuild the store.