I recorded some videos to showcase the prototypes, you can see them in this YouTube channel https://www.youtube.com/playlist?list=P ... ture=share
I thought it worths split the previous topic to a more appropriate one.
I'd like report into this new topic the update to my experiments with a kind of "Assembly" approach to BIM modelling, in the hope it can improve the current modelling experience. This also go into the direction to address last year discussion about separating Arch objects and their geometries (profile extrusion vs wall).
If you are curious and want to try out, please try the attached macro. Note that the implementation is at the moment very rough, and the possibilities are quite limited.
EDIT: 2 _ notes on how it is supposed to work:
The proposed wall object is a "Part::FeaturePython" object, with "App::OriginGroupExtensionPython".
From the User point of view it "behaves" like an App::Part, so its children are "moved directly " and are always shown in place with the wall.
The wall shape at the moment is just a box, with a boolean cut of the object found in the "Openings" propertyLinkChild.
The wall can have 2 different DisplayMode properties (fund under view properties):
- Group: The wall shows every children. This is good for editing because you can move every object indipendently.
- all other choices (default FlatLines): The wall displais it's own shape, that is a Part Compound of all the children. This is good for moving all together because the user will ALWAYS select the wall when clicking on the 3d View, and not one of its children.
We can later implement a switch between this 2 visual styles.
EDIT: 3 _ many thanks to realthunder for providing the base object to play around!