Export an Object to an XML File

The exportxml command can be used to export an object (including those attached to avatars), along with all the necessary textures.

llInstantMessage(CORRADE,
    wasKeyValueEncode(
        [
            // Export an object named "Mouse"
            "command", "exportxml",
            "group", wasURLEscape(GROUP),
            "password", wasURLEscape(PASSWORD),
            // NOTE: or an UUID can be passed
            // NOTE: this must be the name or
            // the UUID of an object (a root primitive).
            "item", "Mouse",
            "range", 5
            "callback", wasURLEscape(URL)
        ]
    )
);

The possible and currently supported downloadable assets are the following: Bmp Emf Exif Gif Icon Jpeg MemoryBmp Png Tiff Wmf

In case the path optional parameter is not specified, then the asset will be downloaded, encoded as a Base64 string, then URI escaped and then placed as the value to the data key from the callback. If the path parameter is specified, then the data will be saved to the indicated path.

• Since an object export consists of both an XML file and the referenced textures, Corrade bundles the XML file and the textures in a ZIP file which it then Base64 encodes and sends it as the value of the data key in the command output. In order to retrieve all the files from the output, you must Base64 decode the value of the data key which will give you binary data representing a ZIP file. Depending on the language you script Corrade in, you can either save that data to a ZIP file and then decompress it using conventional tools or decompress the ZIP file in-memory if the scripting language provides memory streams.
• Contrary to some distinguished viewers, Corrade will only return data if it has succeeded in downloading all the textures, creating the XML file and successfully created a ZIP archive. If at any point there is a failure, Corrade will break execution and return the error. To that effect, the exportxml command does not return partial-results, as in exports with missing textures but will only return completely successful exports.
• Compared to the exportdae command, the exportxml command may only fail in case the object to export is a mesh or contains mesh components. This is simply due to the fact that the exportxml command is insufficient for exporting objects with mesh. When in doubt, you can use the exportdae command which will always succeed but will always convert all the primitives into meshes.
• In order to import back exported items, you can use the importxml command
• Setting the selection parameter appropriately when it is known beforehand whether the sought object is either attached to an avatar or rezzed in-world can greatly improve the search time and speed up the command.