GSoC Proposal: Extended functionality of Rebar Addon
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Re: GSoC Proposal: Extended functionality of Rebar Addon
Should we move the topic to Arch? As it is really related to Arch and BIM?
- Suraj Dadral
- Posts: 307
- Joined: Fri Sep 07, 2018 5:32 pm
- Contact:
Re: GSoC Proposal: Extended functionality of Rebar Addon
Yes, I compiled FreeCAD many times. But, now using its AppImage for ease.
Thanks,
- Suraj Dadral
- Posts: 307
- Joined: Fri Sep 07, 2018 5:32 pm
- Contact:
Re: GSoC Proposal: Extended functionality of Rebar Addon
Looks good to me.
Thanks,
- Suraj Dadral
- Posts: 307
- Joined: Fri Sep 07, 2018 5:32 pm
- Contact:
Re: GSoC Proposal: Extended functionality of Rebar Addon
For this, I think we can use TechDraw workbench objects.amrit3701 wrote: ↑Mon May 04, 2020 5:15 pmAs @bernd already said, I would also like to allow the user to use his own stylesheet. So tree structure look like below:Suraj Dadral wrote:
Code: Select all
BOM_object |__ BOM_content
The BOM_object has Template property. Default value of Template (App::PropertyLink) value default_bom_template.svg. The type of BOM_object.BOMContent is App::PropertyLinkList, with this user can also add n number of tables in same stylesheet.
The BOM_content is the data you produced and this BOM_content object has below properties:
- Placement: Control the position of data in BOM_object.Template. By default, you should calculate but if user want then he can override it.
- Font Style
- Font Size
- Table Lines
- Table Line Style
When the user clicks on BOM_object or BOM_content, the SVG file object inside the FreeCAD window.
Tree Structure:
Code: Select all
BOM_object
|__Template
|__BOM_content_table1
|__BOM_content_table2
Type of Template: 'TechDraw::DrawSVGTemplate'
Type of BOM_content_table1: 'TechDraw::DrawViewSymbol'
We can utilize these and add missing properties like "Font Style" and "Font Size" and maybe more as per requirements.
Sample file: https://github.com/SurajDadral/FreeCAD- ... tion.FCStd
Do we need output similar to this one.
I have some doubts.
1. Are we creating multiple tables in one shot in same template? If so, how data will be split into different tables?
According to my perception till now, I think we need one table per svg file. Please let me know if I am wrong at this point.
Thanks,
Re: GSoC Proposal: Extended functionality of Rebar Addon
Yes, reuse already existing things.Suraj Dadral wrote: ↑Tue May 05, 2020 3:30 pm For this, I think we can use TechDraw workbench objects.
Tree Structure:Type of BOM_object: 'TechDraw::DrawPage'Code: Select all
BOM_object |__Template |__BOM_content_table1 |__BOM_content_table2
Type of Template: 'TechDraw::DrawSVGTemplate'
Type of BOM_content_table1: 'TechDraw::DrawViewSymbol'
The output looks awesome!. Related to adding missing properties to TechDraw objects, here I am not sure because TechDraw objects have no Proxy. Don't know we can extend TechDraw objects to python scripted object or not. Please test it.We can utilize these and add missing properties like "Font Style" and "Font Size" and maybe more as per requirements.
Sample file: https://github.com/SurajDadral/FreeCAD- ... tion.FCStd
Do we need output similar to this one.
Right now, I suggest to go for one table per SVG to make things not complex. As TechDrawPage.Views property type is List and if any user wants to add more tables to TechDrawPage and he do it manually by adding it to Views.I have some doubts.
1. Are we creating multiple tables in one shot in same template? If so, how data will be split into different tables?
According to my perception till now, I think we need one table per svg file. Please let me know if I am wrong at this point.
Re: GSoC Proposal: Extended functionality of Rebar Addon
I also suggest to keep it separated from FreeCAD source code. During development, we can shift rebar addon to the workbench in develop branch (https://github.com/amrit3701/FreeCAD-Re ... ee/develop) and once things stable then we will merge it to rebar addon master branch.
I also using .dmg images (https://github.com/FreeCAD/FreeCAD/releases) as assets regularly updated twice a month.Are you both able to compile FreeCAD (Amrith and Suraj)
Re: GSoC Proposal: Extended functionality of Rebar Addon
yes it looks pretty cool
How can I make this myself? How do I add my own template?
How can I make this myself? How do I add my own template?
Re: GSoC Proposal: Extended functionality of Rebar Addon
ok i am fine with this.amrit3701 wrote: ↑Tue May 05, 2020 6:33 pmI also suggest to keep it separated from FreeCAD source code. During development, we can shift rebar addon to the workbench in develop branch (https://github.com/amrit3701/FreeCAD-Re ... ee/develop) and once things stable then we will merge it to rebar addon master branch.
- Suraj Dadral
- Posts: 307
- Joined: Fri Sep 07, 2018 5:32 pm
- Contact:
Re: GSoC Proposal: Extended functionality of Rebar Addon
I made this manually just to see how it looks.
To do this manually:
1. Create techdraw page using your template.
2. First BOM is created without footer by modifying svg configuration while creating through ui.
3. Second BOM is created without header data.
4. And include both manually on techdraw page.
Thanks,
- Suraj Dadral
- Posts: 307
- Joined: Fri Sep 07, 2018 5:32 pm
- Contact:
Re: GSoC Proposal: Extended functionality of Rebar Addon
I tried this as I did in case of Column and Beam reinforcement objects but didn't worked.
I found one method "TechDrawObj.addExtension( ... )", I think this will do our job.
Testing it and will let you know soon.
Thanks,