The LinkBranch has A3 internally implemented, so it is relevant.prokoudine wrote: ↑Sat Mar 25, 2023 10:52 am
Edit: I don't think it makes sense pointing to newer Link releases though. There have been no changes to asm3 code since 0.11.4 release in November.
The need for a default assembly workbench
Forum rules
Be nice to others! Read the FreeCAD code of conduct!
Be nice to others! Read the FreeCAD code of conduct!
Re: The need for a default assembly workbench
-
- Posts: 125
- Joined: Sat Feb 21, 2015 5:56 pm
Re: The need for a default assembly workbench
If you are using Link branch, Assembly 3 is already included in it
If you are using Master branch, Assembly 3 is an addon.
-
- Posts: 125
- Joined: Sat Feb 21, 2015 5:56 pm
Re: The need for a default assembly workbench
So lemme wrap my head around this.
The Link branch ships asm3 code in binary builds. There have been no changes to the actual WB code since the November release. Therefore there has been no newer asm3 code in newer Link releases per se. But because that unchanged asm3 code is part of a Link release, it is still an asm3 release?
Re: The need for a default assembly workbench
After having a PM conversation with @dan-miel I came to the conclusion that this new Assembly also needs to have something like being able to deal with a PDM.
So my proposal is roughly the same as the one of @Zolko, that is to have the list of files stored separately. My idea is to have a 'FileList.txt' stored inside the FCStd file and that FileList.txt looks like this:
Why a text file? Because it is much easier to deal with a text file than to deal with a XML file.
Why a version? Because then you are gonna open the exact same assembly. But you should be notified when some other guy works onto a different file (say BasePlate) and stores it (makes it rev06). Then when you are opening your assy in the file list there should be an update button.
I think that 5 digits is more than what FreeCAD can handle today.
Edit: Sorry. i meant Zolko, not Kunda.
So my proposal is roughly the same as the one of @Zolko, that is to have the list of files stored separately. My idea is to have a 'FileList.txt' stored inside the FCStd file and that FileList.txt looks like this:
Code: Select all
00000=/project/BasePlate.FCStd<rev05>
00001=/path/to/Nut-M3.FCStd<rev01>
00002=/path/to/Washer-M3.FCStd<rev02>
00003=/path/to/Bolt-M3x20.FCStd<rev01>
Why a version? Because then you are gonna open the exact same assembly. But you should be notified when some other guy works onto a different file (say BasePlate) and stores it (makes it rev06). Then when you are opening your assy in the file list there should be an update button.
I think that 5 digits is more than what FreeCAD can handle today.
Edit: Sorry. i meant Zolko, not Kunda.
Last edited by grd on Sat Mar 25, 2023 12:33 pm, edited 1 time in total.
About Nim. Latest Release 2.0.2. Here is Nim in 100 seconds and a Nim package. There are Qt and OCCT packages.
Re: The need for a default assembly workbench
I am just a (content) user so probably not the best one to answer...prokoudine wrote: ↑Sat Mar 25, 2023 12:02 pm ...Therefore there has been no newer asm3 code in newer Link releases per se...
for example 2022.07.04
https://github.com/realthunder/FreeCAD/ ... 07.04-edge
Assembly3
Fix checking of fixed part (#1200)
Fix assembly BuildShape handling (#1030)
Simply pip install of SolveSpace solver (#1244)
Improve error message on broken element (#1239)
Fix wrong shape on frozen assembly (#453)
-
- Posts: 125
- Joined: Sat Feb 21, 2015 5:56 pm
-
- Posts: 125
- Joined: Sat Feb 21, 2015 5:56 pm
Re: The need for a default assembly workbench
@grd
Do you think SVN-style versioning will be sufficient in a PDM?
Do you think SVN-style versioning will be sufficient in a PDM?
Re: The need for a default assembly workbench
probably because I am doddery old fart, that gets confused easilyprokoudine wrote: ↑Sat Mar 25, 2023 12:31 pm ....I'm not sure why you would pick a Link release from July 2022 as a suggestion (?) that there has been new asm3 code since the last asm3 release in November 2022.
Re: The need for a default assembly workbench
It all depends on whether one use a PDM or not, but if one is using a PDM then I think that this style of versioning is enough. I don't know the exact versioning type, that I only mentioned here. This is only for talking, I haven't thought about the exact style of versioning.prokoudine wrote: ↑Sat Mar 25, 2023 12:39 pm @grd
Do you think SVN-style versioning will be sufficient in a PDM?
About Nim. Latest Release 2.0.2. Here is Nim in 100 seconds and a Nim package. There are Qt and OCCT packages.