![]() ![]() nameVisible attribute of element was renamed as areaVisible logitude attribute of element was corrected as longitude sh3d files, its XML format had to evolve a little to fix some typos and other small problems: To let the XML entry generated by Export to XML/OBJ plug-in share the same DTD as the Home.xml entry in. The JavaScript part of the Export to HTML5 plug-in now supports pinch for zoom under Android and Windows, and was optimized to draw 3D lines faster. Here's the new versions 1.2 of Export to HTML5 and Export to XML/OBJ plug-ins.īoth plug-ins are now based on the management of the new XML entry that was added to. The Html file start to load *.zip and stops there. it's possible to somehow detect that accessing files from files is disabled right from the page script, and display corresponding message. ![]() even add a message on local file access to ViewHome.html. Probably it's good to add info on that to blog/manual e.t.c., or m.b. To run the exported ViewHome*.html in Chrome browser, you have to start chrome.exe with "-allow-file-access-from-files" commandLine option (no quotes).Įlse it will just stuck on "loading model" message. This thing does not work in Chrome out of the box. ![]() The script creates one object for each obj file (leaving easier editing of objects in blender), this is the the main difference to use the obj file generated by SweetHome 3D. I published the python script to import SweetHome 3D HTML5 to blender in GitHub: SweetHome3D HTML5 to Blender importer. With the new XML the light will can be edited in Sweet Home and blender will be used only as viewer. ![]() Now I have to change my blender import script to work with the new XML schema. Puybaret thank's for the Export to XML/OBJ plug-in! Home.xmlĮmmanuel Puybaret, Sweet Home 3D developer Hope you'll find all kind of use for your Sweet Home 3D dataĭownload links for Export to XML/OBJ plug-in:Įxport to XML/OBJ plug-in 1.1 was released on Įxport to XML/OBJ plug-in 1.2 was released on Įxport to XML/OBJ plug-in 1.3 was released on This plug-in reuses the same classes as Export to HTML5 plug-in, that's why it uses the same version number 1.1. A more complete description of the schema will be available with next Sweet Home 3D release. If needed, look at .exportxml.HomeXMLExporter class source code included in the plug-in or ask for more information in this forum. Lengths are in centimeters and angles in radians. An exported Home instance will have an XML structure looking like this:Īt the moment, the only elements which have an id are level and wall elements because they can be referenced in other elements. Its elements and attributes match API (except for the classes starting by Home which is omitted, like HomeLight class which becomes light element). The XML schema used in the Home.xml entry should be quite straightforward. This generated ZIP file is compatible with Sweet Home 3D JS viewer (it just contains more data that the home file generated by Export to HTML5 plug-in, and will be readable with Sweet Home 3D 5.3 too, once the upcoming changes in. furniture icons, texture images and other images. 3D models only at OBJ+MTL format (models at other format will be converted) HomeStructure/Home.obj that contains the home structure computed by Sweet Home 3D classes (wall, rooms, ground and 3D labels) Home.xml entry with all the data of the edited home at XML format (including furniture visible or not, walls, rooms, texts, dimensions lines, polylines.) As I received an other request similar to lcgamboa's one, I finally programmed the additional Export to XML/OBJ plug-in (see links at end of message) that proposes the Tools > Export to XML/OBJ format menu item able to generate a ZIP file that contains: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |