Question about Part Feature
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Question about Part Feature
Is current PartDesign NEXT Part feature equivalent of a Part or of an Assembly or both?
- DeepSOIC
- Veteran
- Posts: 7896
- Joined: Fri Aug 29, 2014 12:45 am
- Location: used to be Saint-Petersburg, Russia
Re: Question about Part Feature
Assembly will most likely consist of Instances of Parts, or Parts themselves. Part will probably be able to contain a (sub)assembly, but I'm not sure... Part is called "Part", but you can use it for anything you want. You just need to consider, how various tools handle it, like exports...triplus wrote:Is current PartDesign NEXT Part feature equivalent of a Part or of an Assembly or both?
Re: Question about Part Feature
This is what puzzles me:
Part feature with added 2 Body features. Is this a Part or an Assembly?
P.S. Due to missing Revolve feature i settled for linear guide.
Part feature with added 2 Body features. Is this a Part or an Assembly?
P.S. Due to missing Revolve feature i settled for linear guide.
- DeepSOIC
- Veteran
- Posts: 7896
- Joined: Fri Aug 29, 2014 12:45 am
- Location: used to be Saint-Petersburg, Russia
Re: Question about Part Feature
I'd say, both. It's a Part, which is itself an assembly of parts.triplus wrote:Part feature with added 2 Body features. Is this a Part or an Assembly?
It's a question of how you want to call them, not what they are. You already said what they are: two Bodies in a Part container.
Re: Question about Part Feature
On the plus side when looking at it we see it the same way. On the down side the level of confusion amazes me.
If only it could be that simple. Assembly shouldn't be called a Part in my opinion. That by itself introduces confusion beyond compare. And if it is an Assembly and not a Part user should be able to add Assembly constraints between Body features in the future? And likely that will work different compared to assembling assemblies?I'd say, both. It's a Part, which is itself an assembly of parts.
Are they? Two Bodies in a Part container? Or are they two Parts in an Assembly container?It's a question of how you want to call them, not what they are. You already said what they are: two Bodies in a Part container.
Re: Question about Part Feature
Onshape folks would probably call it part studio Anyway, I think we should not complicate too much with naming and not go in to too strict, locked down workflows. As is the code of FreeCAD so should also its workflows be open and allow users of different backgrounds and industries to model as they like and need.
Re: Question about Part Feature
I think it makes sense to use "part" as a general term to include "assemblies" and "bodies". A body would be an indivisible part, while an assembly contains multiple parts. In that sense, the only difference between a sub-assembly and an assembly is that a subassembly is used as a part of anther (sub)assembly.DeepSOIC wrote:Assembly will most likely consist of Instances of Parts, or Parts themselves. Part will probably be able to contain a (sub)assembly, but I'm not sure... Part is called "Part", but you can use it for anything you want. You just need to consider, how various tools handle it, like exports...triplus wrote:Is current PartDesign NEXT Part feature equivalent of a Part or of an Assembly or both?
My latest (or last) project: B-spline Construction Project.
Re: Question about Part Feature
My question has nothing to do with locking down the workflow. It's about determining what exactly is the Part feature in PartDesign NEXT.saso wrote:Onshape folks would probably call it part studio Anyway, I think we should not complicate too much with naming and not go in to too strict, locked down workflows.
A Body is not invisible and you say it is a Part. I agree with that. A Body is a Part? Assembly contains multiple Parts. I agree with that. And the only sane conclusion i can make of it is current Part feature in PartDesign NEXT is Assembly feature. No? Adding assembly constraints between Body (Part) features is therefore on the todo list? And once achieved Assembly NEXT/PartDesign NEXT like envisioned before starting the work should be achieved?jnxd wrote:I think it makes sense to use "part" as a general term to include "assemblies" and "bodies". A body would be an indivisible part, while an assembly contains multiple parts. In that sense, the only difference between a sub-assembly and an assembly is that a subassembly is used as a part of anther (sub)assembly.
Re: Question about Part Feature
I guess it depends on the design intent:
Potential user facing confusion therefore can't be easily resolved.
P.S. As i was thinking if this would be Assembly feature it might make sense to move it in Assembly workbench. In PartDesign workbench user would therefore insert a Part (currently Body) feature and such Part features could be grouped under Assembly (currently Part) feature if needed. But that would i guess introduce confusion when user would need to insert Assembly feature to create what they perceive as a (multi Body) Part. And i don't know if it is planned but current Body feature is such a nice candidate to support adding (assembly) constraints between them. I guess they could be called Part constraints if that happens.
Anyway i hoped to think of a solution that could reduce potential user confusion. But i don't see an easy one ATM.
Potential user facing confusion therefore can't be easily resolved.
P.S. As i was thinking if this would be Assembly feature it might make sense to move it in Assembly workbench. In PartDesign workbench user would therefore insert a Part (currently Body) feature and such Part features could be grouped under Assembly (currently Part) feature if needed. But that would i guess introduce confusion when user would need to insert Assembly feature to create what they perceive as a (multi Body) Part. And i don't know if it is planned but current Body feature is such a nice candidate to support adding (assembly) constraints between them. I guess they could be called Part constraints if that happens.
Anyway i hoped to think of a solution that could reduce potential user confusion. But i don't see an easy one ATM.
Re: Question about Part Feature
Also, suppose if I make a CSG solid under the Part workbench, then how can I make a part out of it?
Currently I can't find anyway to do it under the Part or PartDesign workbench.
Currently I can't find anyway to do it under the Part or PartDesign workbench.