As I wrote yesterday, I have found how to edit the sidebar.vocx wrote: ↑Wed Oct 31, 2018 6:35 pm I'd like to continue using Userdocnavi, as it's a nice way to jump around the tools in the online wiki. This makes sense to me, unless you can update the left sidebar, as discussed in the other thread https://forum.freecadweb.org/viewtopic. ... 57#p265957
Working on the documentation (was: Arch Window - Glass Panel Area etc in Python Script?)
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Re: Working on the documentation (was: Arch Window - Glass Panel Area etc in Python Script?)
Re: Working on the documentation (was: Arch Window - Glass Panel Area etc in Python Script?)
I found that as well, the issue is not finding about it, but actually changing it. Do you have permissions to do it? Are you going to do it?NormandC wrote: ↑Thu Nov 01, 2018 4:24 amAs I wrote yesterday, I have found how to edit the sidebar.vocx wrote: ↑Wed Oct 31, 2018 6:35 pm I'd like to continue using Userdocnavi, as it's a nice way to jump around the tools in the online wiki. This makes sense to me, unless you can update the left sidebar, as discussed in the other thread https://forum.freecadweb.org/viewtopic. ... 57#p265957
Always add the important information to your posts if you need help. Also see Tutorials and Video tutorials.
To support the documentation effort, and code development, your donation is appreciated: liberapay.com/FreeCAD.
To support the documentation effort, and code development, your donation is appreciated: liberapay.com/FreeCAD.
-
- Veteran
- Posts: 2611
- Joined: Tue Feb 21, 2012 8:07 pm
- Location: Torino - Italy
Re: Working on the documentation (was: Arch Window - Glass Panel Area etc in Python Script?)
About navigation, please take a look at https://forum.freecadweb.org/viewtopic. ... 57#p266266
and give me an opinion, thank you.
Sorry if I cross the discussions, but this seems more read.
Renato
and give me an opinion, thank you.
Sorry if I cross the discussions, but this seems more read.
Renato
Re: Working on the documentation (was: Arch Window - Glass Panel Area etc in Python Script?)
material is another module without a workbench. https://github.com/FreeCAD/FreeCAD/tree ... d/Materialyorik wrote: ↑Wed Oct 31, 2018 5:39 pmA module is an application extension (we're talking about code, basically). A workbench is a special functionality of FreeCAD. Most of the FreeCAD modules also define a workbench with the same name, but not all (the Addon Manager is an example of a module that doesn't define a workbench).
Re: Working on the documentation (was: Arch Window - Glass Panel Area etc in Python Script?)
I don't think it makes sense to make a distinction between a module and a workbench based on the GUI alone. The user doesn't really care about that. That is important for the developer who wants to add a functionality to FreeCAD. But the user just wants to use the interface to do things he sees in front of him or her. That is, only FreeCAD developers should talk about "modules" in the specific sense of the code, while the rest, and the documentation, should talk about workbenches.bernd wrote: ↑Thu Nov 01, 2018 8:36 pmmaterial is another module without a workbench. https://github.com/FreeCAD/FreeCAD/tree ... d/Materialyorik wrote: ↑Wed Oct 31, 2018 5:39 pm A module is an application extension (we're talking about code, basically). A workbench is a special functionality of FreeCAD. Most of the FreeCAD modules also define a workbench with the same name, but not all (the Addon Manager is an example of a module that doesn't define a workbench).
Always add the important information to your posts if you need help. Also see Tutorials and Video tutorials.
To support the documentation effort, and code development, your donation is appreciated: liberapay.com/FreeCAD.
To support the documentation effort, and code development, your donation is appreciated: liberapay.com/FreeCAD.
- kkremitzki
- Veteran
- Posts: 2511
- Joined: Thu Mar 03, 2016 9:52 pm
- Location: Illinois
Re: Working on the documentation (was: Arch Window - Glass Panel Area etc in Python Script?)
I still think that, in principle, going forward with this is a good idea, but not in its current form. vocx, keeping in mind that the work you propose will have some administrative burden which should be minimized, perhaps it's a good idea to try to reformulate your proposal based on SMART criteria? I.E. specific, measurable, achievable, relevant, time-bound. And it wouldn't hurt to try to reduce the size and time of your proposal to try to conform to those criteria as much as possible. If things go well, we can just repeat the process.