Ross Diankov

at minimum, I was thinking of creating a **self.instance_url** variable for all urls that could not be resolved. that way when the object is saved back, it can set the...

it could be a python string or an object modeling the collada instance_\* elements. either way, external references are not something that i want my application to read, but i...

"i want my application to read" as in i don't want it resolving into a file that it then loads into memory, that can take too much processing power

that makes us the world's first users of external references with collada (yay!). unfortunately this is a feature that we cannot live without. For now, how do we implement the...

i added several new dae files with external references to my git clone. however, i can't do any new pull requests until you clear my current one. for the time...

FYI: mug1external.dae references a simple one link object mug1.dae lab3external.dae references an entire robot with multiple links and physics info

Given that elements like instance_physics_model can have children specific to the physics specification, it might be necessary to create a separate InstancePhysicsModel class to manage that info (assuming user doesn't...

ok... that knocks down articulated_system, physics_model, and rigid_body and the associated libraries. what about kinematics_scene, physics_scene and those libraries? how should i connect them with the current scene?

the goal right now is to be consistent with the rest of the pycollada programming style, which is just a way of converting collada xml to python objects.

i started a branch called collada15spec for creating the 1.5 spec classes. https://github.com/rdiankov/pycollada/tree/collada15spec please keep in mind i'm only going to implement what is necessary for my application to work,...