thomas-neemann wrote: ↑Mon Apr 19, 2021 7:42 am
in my opinion, everything is already there that is necessary without assembly wbs
Yes, this is also my opinion.
what I propose is to make this the official FreeCAD position: let's decide that the App::Part (Std_Part) container is *THE
* assembly container, which can contain any other "stuff" , including other App::Part things, building nested assemblies. What I mean by that is that it is possible, today, thanks to realthunder
's App::Link interface introduced in v0.19, to build assemblies - even complex, nested assemblies - with core FreeCAD.
What I also propose is to separate the data structure (of loading external parts) from the placement of these parts relative to each other. This is a separate problem that should be dealt with by geometry solvers. Any and all such solvers should calculate the "Placement" property of the included objects. The most basic of such solver being manual placement. Another placement is of course Assembly4's Placement calculation through datum objects and the ExpressionEngine, but this is clearly only one of such possible solvers.
What this means in practice is that A2+ and Asm3 should be "ported
" to the App::Part container. Yes, I know, some people might think that I try to pull the cover to the Asm4 file format, but what I'm trying to say is the exact opposite : it's *BECAUSE
* that file structure is good that Asm4, by sheer luck, got to win the trophy. But now, face-it, this is the good solution. Independently from what anyone might think about personal opinions: the App::Part container with the App::Link interface is WORLDCLASS !!!!