Editing Scalable Vector Graphics (SVG)
From Wiki.OSArch
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 10: | Line 10: | ||
* Supported everywhere! | * Supported everywhere! | ||
* Easy to read, easy to write, and a variety of data types to play with (paths, primitives, groups, defs...) | * Easy to read, easy to write, and a variety of data types to play with (paths, primitives, groups, defs...) | ||
| − | * Classes (like layers, but more flexible, which is both good and bad) with styles at run-time | + | * Classes (kinda like layers, but more flexible, which is both good and bad) with styles at run-time (in my opinion, better than baked) |
* Can be turned interactive, with HTML, CSS, and Javascript (animation, hyperlinking, style combo changes, LOD zoom in/out, drag/drop - annoying tag obscuring your drawing? Just flick it away! Real-time updates from RSS or API - no more outdated drawings at site! Etc...) | * Can be turned interactive, with HTML, CSS, and Javascript (animation, hyperlinking, style combo changes, LOD zoom in/out, drag/drop - annoying tag obscuring your drawing? Just flick it away! Real-time updates from RSS or API - no more outdated drawings at site! Etc...) | ||
| − | * Can add properties and metadata relating it back to model space. And not just classes, but serious metadata - could include IFC-XML inside SVG using their "metadata" element. | + | * Can add properties and metadata relating it back to model space. And not just classes, but serious metadata - you could actually, believe it or not, include IFC-XML inside SVG using their "metadata" element. |
Cons of SVG: | Cons of SVG: | ||
| − | * CAD programs don't typically treat it as a CAD format. Modification is usually done in artsy programs like | + | * CAD programs don't typically treat it as a CAD format. Modification is usually done in artsy programs like Inkscape which aren't designed for drafting. (but hey, Blender is an artsy program too, yet here we are!) |
| − | * Only one paper space. No absolute units. You can have embedded SVGs (which mean multiple SVGs), but everything has to be bound within a single document at the end of the day, there isn't | + | * Only one paper space. No absolute units. You can have embedded SVGs (which mean multiple SVGs), but everything has to be bound within a single document at the end of the day, there isn't the concept of "pages". (well, not natively, but we can hack it) |
* 2D only. Unless you include IFC-XML. | * 2D only. Unless you include IFC-XML. | ||
| − | = | + | =Resources= |
| − | |||
* SVG is listed in the [[AEC_Open_Data_Standards_Directory]] | * SVG is listed in the [[AEC_Open_Data_Standards_Directory]] | ||
| − | |||
| − | |||
| − | |||
* [https://en.wikipedia.org/wiki/Scalable_Vector_Graphics SVG article on Wikipedia] | * [https://en.wikipedia.org/wiki/Scalable_Vector_Graphics SVG article on Wikipedia] | ||
* [https://www.w3.org/Graphics/SVG/ World Wide Web Consortium's page on the SVG format] | * [https://www.w3.org/Graphics/SVG/ World Wide Web Consortium's page on the SVG format] | ||
| − | * [https:// | + | * Discussion on documentation formats on the OSArch discussion forum [https://community.osarch.org/discussion/170/what-is-best-for-documentation-when-svg-dxf-dwg What is best for documentation when svg, dxf, dwg?] |
| − | |||
| − | |||
