WISH: support for xml-based step file format export-import

[ivelin.peychev]

Not a problem, just will allow much more possibilities.

Export/import models with attributes that can be assigned to objects’ usertext. Is one of the best features that could be implemented.

Also as mentioned in another thread:

WISH: join when importing IGES

I’ve added it as a Wish item: https://mcneel.myjetbrains.com/youtrack/issue/RH-51255 When Rhino reads a STEP file, the surfaces that make up a designated closed solid are Joined. They are not Joined when using IGES. If you need a Solid and don’t want to Join them yourself, the STEP advantage is Rhino tries to Join them for you.

STEP is superior to IGES due to a mechanism implemented in Rhino to join surfaces into polysurfaces.

Currently Rhino supports only 2 STEP standards, and there are plenty more. Automotive industry is not the only one which uses Rhino!

as a matter of fact other industries use rhino much more than automotive, considering that most (if not all) of the car manufacturers use primarily CATIAv5 and CATIAv6.