Improvements we would like to see in FreeCAD

[KeithSloan]

1. getGlobalPlacement to support Links

The frame of reference for Placements in FreeCAD is the containing Part, or the base Document.

We nearly always need the GlobalPlacement for GDML exports. The FreeCAD API has getGlobalPlacement but it does not support Linked objects or Parts. Our coding would be much simpler if we could rely on getGlobalPlacement

2. Ability to scan document structure without having to resort to using Qt
   see https://singerlinks.com/2023/11/how-to-iterate-the-freecad-document-tree-using-python/

On export we need to recreate the FC doc structure in GDML and were very surprised that we had to resort to processing using the Qt api.

3. FC Mesh to support Quad & Triangular Facets

GDML Tessellations can contain Quad & Triangular Facets. FC Mesh only supports Quad by converting to two Triangular.
We could process Tessellations faster, if we could rely on just using Mesh facilities as these are implemented in C++

4. Spreadsheet

1. Radians
   GDML supports both Radians and Degrees for angles, yes we can convert but this does not enable symmetric import/export.
   Users would like to be able to import a design, make changes and then export, with the requirement if an angle is specified in radians on import it is also on export. Note: The specification does not limit units to purely degrees or radians.
2. Alias and Column Names
   Variables in GDML can be and are often single characters, so this makes creating an Alias in a Spreadsheet difficult as we have to introduce a prefix on input that is removed on export, not very elegant and the user gets to see the prefix.

5. Action Property

Some GDMLObjects have n sub Objects, examples being Sections, Vertex, we therefore need a way of adding deleting.

One approach would be to have a property that was of a new type, Action, such that clicking on the property would just drive onChanged or execute

6. Special Characters in Names