freedman wrote: ↑
Sat Aug 24, 2019 5:46 pm
I'm dizzy when it comes to reading all the post and topics about what comes next. ...
You really need to read carefully this thread App::Link: the big merge
, and the information provided in realthunder's wiki in GitHub: Link
and Core Changes
. Most of that is developers documentation, it is not meant to be understood by common users, but by other developers.
2) Just to verify, Link is a piece of code from realthunder merged with 0.19? I think that's correct.
3) Is something going to be replaced, Asm3, 0.19?
Code is being added, not replaced.
4) I have seen Link, Link Stage, App::link, merge, link merge, ect. Is there a formal wording yet that I can use to search?
"Link", or more formally "App::Link", is a new type of "object", or more formally, a FreeCAD "App::DocumentObject". Everything that you create in FreeCAD, a line, a body, a part, a group, a Wall, an array, etc., is a "DocumentObject". "Link" is a special type of object with certain properties that will hopefully allow for doing assemblies easier.
During development, realthunder had various Git branches named "Link", "LinkDev", "LinkStage", "LinkStage2", "LinkStage3", etc., so people referred to "realthunder's work" in various ways, by the name of the feature "Link", or by the branch's name. Git is used by the FreeCAD programmers to manage code; "branch" is a term used a lot in Git. If you don't know Git, you can read more about it in the wiki, source code management
The branch that was just merged into the official FreeCAD code, with pull request #2350
, was LinkMerge
, which some people called just "Merge", or "Merge3", referring to the version of realthunder's "LinkStage3".
5) Are file types (structure) in question on this new path?
What does this even mean?
6) What should I be testing, ...
"Link" by itself is an internal piece of code that will have use in assembly (and some other cases). As a common user, you don't need to test anything in particular. Just test FreeCAD in general; test that everything works as good as it was before the big merge. The "LinkMerge" branch introduced more than the "Link" object; it also made many small changes to the core of FreeCAD (again see Link
and Core Changes
). So just test that everything works as you expect.
I feel like 0.19 isn't going to be around long?
What? Why? FreeCAD 0.19 is a development
version. It isn't even "released" at the moment, so it cannot "go away" before it has arrived. When FreeCAD 0.19 is released (maybe around May 2020, just like the previous versions of FreeCAD have been released in that time), it will become the latest official FreeCAD version. In that moment development will just continue with the v0.20 version.
7) If everything goes as planned what piece of code will FreeCAD be in 6 months.
Just what you see now, but better? Right now it's the moment to test FreeCAD 0.19 in general, and report bugs. Obviously the big merge of "LinkMerge" is disruptive, and brings some problems that are currently being addressed by the developers. Realthunder already submitted pull request #2449
to solve many small bugs found in the last few days. Hopefully things stabilize in the next few months, so when 2020 comes the entire FreeCAD codebase is more stable and the release of 0.19 goes smoothly.
What is Assembly3?
"Assembly3" is an assembly workbench written in Python that realthunder developed, that depends on the "Link" functionality that he also created. Assembly3 is still not officially merged into FreeCAD. However, since "Link" was already integrated into FreeCAD, it's just a matter of time for Assembly3 to be provided, either officially or as an installable add-on, just like A2plus Workbench
is provided currently.
How do I use Assembly3?