Sure!
So your first patch for the Assembly branch is putting gcc in C11 mode. Will be integrated right away!

Yes, such a model is basically unusable to further work with it. This is the number one reason I currently work on adding more features to part design like primitives, loft and sweep, to allow a real transition from mixed models into a usable "PartDesign Part" Thats the right way to go. T...

We have to make external pivy the default! General we will have a split point, which is the Part object. Above the Part the Assembly is in charge. There will be the referencing and importing. Below Part object the modeling stuff happens (PartDesign, Mesh, ....). Most of the Import stuff is in the im...

Hi, yea, you need in any case the external Pivy! I did a big merge of master and tandersons branch into the Assembly2 branch. On Window it compiles, but I have a problem with a crash on shape highlighting... There are several angles of attack at the moment. Tanderson working to get the PartDesign in...

I never considered limiting features, what I meant is the ability alter the dependency graph. i.e. reorder features, insert feature etc. In what kind of workflow you actually need that? right now part design has the body object that serves two purposes. 1) as a reference so App::Part (for example) ...

Hi together,
I was some time absent, and the FEM workbench was half usable when I left
I'm really pleased some of you are take it further!

What happens in FEM in the last half year and what are the problems?

Because of my experience, I don't agree with this. But that is alright as I am not trying to change the design. I simply want to know what the design is and what needs to be done to merge the assembly fork. Never mind! Its important to have this discussion. As more consensus as better! Basically I ...

What do you mean with reorder? If you just mean a kind of grouping, then the GeometricGroup is a option. There you can bundle some model steps. The Body adds to the behaviour of a GeometricGroup a Tip, which is a actual tip of the model and in PartDesign the only visible (besides planes and other he...

in PartDesign a sketch should always base on a other feature or one of the base planes. But its on the Gui commands, which build up the mode,l to enforce that, not on the sketch itself! Because the sketch can used in many different ways outside the PartDesign...

IMO a sketch without a support should be possible.
And anyway, a DocumentObject should not throw an exeption like that!

IMO that exception has to get out of the code. If there is no support the sketch just stays were it is!