Hi,
Ok, I'll do a sample.
for GameObject, material, texture, and object, it will be up to particular needs because they are not really serializable easily, especially objects ( GO, material and object), for texture,
--GameObject: use the name or the full path name ( I can make an action for that if you want)
-- Texture: use Resources and save the relative path, or use a Url and download, or use an id and have your textures referenced in ArrayMaker on a Hashtable
-- Material: same as textures, url could point to bundles
-- objects: it depends the object, but data will likely need to be serialized specifically to fit into xml
Bye,
Jean
--