You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I notice that you have a titleblock editor for your pages. Can you tell me where the source code of this editor is, and whether it would be possible to re-utilize in other applications? Does it depend on many pieces of QElectroTech, or would it be possible to easily use in another program?
I am one of the contributors to https://github.com/FreeCAD/FreeCAD. In this project we have the TechDraw Workbench to generate 2D technical drawings from 3D models. The templates used in this workbench are simple SVG files. Currently there is no easy way to create your own template with a custom titleblock; the process is entirely manual: you create it with something like Inkscape, and optionally edit the XML to have editable fields.
Having a dedicated titleblock and template creator would be something that would bring more user friendliness to TechDraw, and it's a feature often requested in the forum along with automatically filling the information of the titleblock.
I am not good at C++ but I can get in contact with the TechDraw main developer so that he can take a look at this. FreeCAD is programmed in C++ and Qt5, so I think it should be possible to integrate parts of QElectroTech without many problems. In addition, if the source files of the titleblock editor use standard functions from C++ and Qt5, then we may be able to translate those to pure Python, and this would be simpler to integrate.
An issue, however, is the license; FreeCAD uses the LGPL2 license, while QET uses GPL2. In this case, we would not copy the exact files from QET; some changes would be necessary so that the code is not a derivative work (so it can be licensed as LGPL2). An alternative is that the files from QET are re-licensed as LGPL2 so that they can be used directly inside FreeCAD. All source files of the base FreeCAD system must be LGPL2 compatible (also MIT and BSD are fine).
The text was updated successfully, but these errors were encountered:
7: LGPLv2.1 gives you permission to relicense the code under any version of the GPL since GPLv2. If you can switch the LGPLed code in this case to using an appropriate version of the GPL instead (as noted in the table), you can make this combination.
If you can switch the LGPLed code in this case to using an appropriate version of the GPL instead (as noted in the table), you can make this combination.
We know this, but we won't relicense FreeCAD code to GPL2; it must remain LGPL2 as FreeCAD can also be used as a library, so LGPL2 is more flexible.
Hi, I notice that you have a titleblock editor for your pages. Can you tell me where the source code of this editor is, and whether it would be possible to re-utilize in other applications? Does it depend on many pieces of QElectroTech, or would it be possible to easily use in another program?
I am one of the contributors to https://github.com/FreeCAD/FreeCAD. In this project we have the TechDraw Workbench to generate 2D technical drawings from 3D models. The templates used in this workbench are simple SVG files. Currently there is no easy way to create your own template with a custom titleblock; the process is entirely manual: you create it with something like Inkscape, and optionally edit the XML to have editable fields.
Having a dedicated titleblock and template creator would be something that would bring more user friendliness to TechDraw, and it's a feature often requested in the forum along with automatically filling the information of the titleblock.
I am not good at C++ but I can get in contact with the TechDraw main developer so that he can take a look at this. FreeCAD is programmed in C++ and Qt5, so I think it should be possible to integrate parts of QElectroTech without many problems. In addition, if the source files of the titleblock editor use standard functions from C++ and Qt5, then we may be able to translate those to pure Python, and this would be simpler to integrate.
An issue, however, is the license; FreeCAD uses the LGPL2 license, while QET uses GPL2. In this case, we would not copy the exact files from QET; some changes would be necessary so that the code is not a derivative work (so it can be licensed as LGPL2). An alternative is that the files from QET are re-licensed as LGPL2 so that they can be used directly inside FreeCAD. All source files of the base FreeCAD system must be LGPL2 compatible (also MIT and BSD are fine).
The text was updated successfully, but these errors were encountered: