For example Current situation in ArchStairs.py:-
- In original ArchStairs.py, it generate as desired the base Structure, Stringer, Tread (visible identifiable 'objects') under 1 single Stairs object
- I have not studied materials in Window/Door (glass, frame) and am not aware if originally if / how different Materials should/could be 'stored' in different parts abovementioned in ArchStairs
- Renato Rebelo suggested adding Riser (thickness)
- Currently trying to complete (curvilinear) Railing as experimental feature in ArchStairs
- Earlier experiment add 'multiple-segment' of a stairs - e.g. a flight, a landing, another flight...
- Now each flight, landing, railing are 'separate' Components Stairs objects grouped under 1 'master Stairs object - not sure this is optimal approach
(But then one have finer control over these 'Components' / different forms) - Though not in Window object, I am thinking if it is also better separating e.g. Tread, Structure (Riser maybe) and group them under another level of Stairs Object or whatever
(Window/Door has not separated glass pane, door panel, frame into 'Components') - Then, each (sub-)Components could be assigned with different Materials?
- Not knowing how e.g. exporting to IFC would treat these (sub-)Components and Multiple-Materials
- In earlier discussion, I discuss about 'Profile Generators e.g. for Stairs' - similar to underlying Sketch in a Window
- I am thinking for Stairs, I generate separate Profile for each of its 'sub'-Components
- E.g. currently 2 Separate Wire object for 2 railing (though not sketch at the moment - need to be 3d)
- Then, there will be several Sketches / Wires object 'attached/linked' to the Stairs - Structure, Tread, Riser...
- This seems create complication and components management problem
- Like in the Video Regis posted earlier here, other soft can handle object with probably hundreds of components like Curtain Wall
- I have been thinking if Window --> Curtain Wall should have each Window 'modules' (to extreme each glass pane, frame...) separate into Components so each could then be 'tweaked' individually
- In most case this may not be necessary, e.g. only 1 or 2 panels are turned into a door and others kept as typical
- For a Stairs, there may be a few numbers of Components in a 'Master' Stairs
- For a Curtain Wall, there may be a few hundreds of e.g. Utilised Window Units thus Components in a 'Master' Window / Curtain Wall object
- Making each unit a Component under a 'master' Window/Curtain Wall object may have performance, processing sub-components, model tree management issue...
- Currently it seem not possibly for FC to hide objects https://forum.freecadweb.org/viewtopic.php?f=10&t=3677
Any ideas / thoughts?