I totally agree. However, @realthunder hasn't stopped (or even slowed down) development of Asm3 until it's been reviewed. He's been adding features (the Python interpreter is the killer one, IMO), fixing his and the upstream's bugs. What I understand is that he says his branch has to be reviewed in order to perform the possible replacements (Parts with Assembly containers and such).wsteffe wrote: ↑Tue Jan 08, 2019 2:31 pmI think that the maintainers of FreeCAD projects are free to merge the LinkStage3 branch. It is just that they don't want.
Realthunder asked to evaluate the possibility of this merge more than 6 moths ago (30 June 2018) and I do not have yet seen any reply from the main the FreeCAD project leaders.
So I do not think that it would be a good idea stopping the development of ASM3 branch to wait for a merge which probably will never happen.
Regarding the keeping track of references in either main assembly file or the part files: It's technically impossible to properly design/manage a re-usable library infrastructure if you stick with modifying the dependencies (the part files) regarding to their use places. You would never change a library code when you use the library in your code, would you? KiCAD has tried that and obviously failed.
If I correctly understand the problem, it's a problem of breaking change in the library part. If you are the author of PART_A and use it both in PRODUCT1 and PRODUCT2, then delete something in PART_A while you are working on PRODUCT2, then PRODUCT1 becomes broken. Is that correct? If yes, I'll continue my proposal.