Translations:Workbench creation/8/en: Difference between revisions

From FreeCAD Documentation
(Importing a new version from external source)
 
(Importing a new version from external source)
Line 1: Line 1:
You can choose any license you like for your workbench, but be aware that if you wish
You can choose any license you like for your workbench, but be aware that if you wish to see your workbench integrated into and distributed with the FreeCAD source code at some point, it needs to be LGPL2+ like the example above. See [[Licence|Licence]].
to see your workbench integrated into and distributed with the FreeCAD source code at
some point, it needs to be LGPL2+ like the example above.
The FreeCAD.addImportType() and addEXportType() functions allow you to give the name
and extension of a file type, and a python module responsible for its import. In the
example above, an "importOwn.py" module will handle .own files. See [[Code snippets]]
for more examples.

Revision as of 21:18, 30 August 2019

Information about message (contribute)
This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.
Message definition (Workbench creation)
You can choose any license you like for your workbench, but be aware that if you wish to see your workbench integrated into and distributed with the FreeCAD source code at some point, it needs to be LGPL2+ like the example above. See [[License|License]].

You can choose any license you like for your workbench, but be aware that if you wish to see your workbench integrated into and distributed with the FreeCAD source code at some point, it needs to be LGPL2+ like the example above. See Licence.