HowTo:Use POV-Ray with Blender/Developers - Revision history

Maurice: /* primitives.py */

2025-11-17T14:57:59Z

primitives.py

2025-03-01T20:42:26Z

2025-01-03T11:24:32Z

Comments

2024-12-31T15:00:43Z

metadonnées de l'add-on

2024-12-31T14:59:19Z

add-on’s metadata

2024-12-29T22:36:33Z

2024-12-29T22:25:14Z

2024-12-28T15:26:03Z

2024-12-28T13:40:21Z

2024-12-28T13:39:20Z

← Older revision		Revision as of 14:57, 17 November 2025
Line 480:		Line 480:
	Display some POV native primitives in 3D view for input and output		Display some POV native primitives in 3D view for input and output

		+	The [https://refactoring.guru/design-patterns/factory-method Factory] design pattern is used for creating primitive shapes.
		+
		+	This pattern allows for flexible and scalable creation of different types of primitives without exposing the instantiation logic to other parts of the system.

	====object_mesh_topology.py====		====object_mesh_topology.py====

@@ Line 4: / Line 4: @@
    | fr=FR:HowTo:Use_POV-Ray_with_Blender/Developers
    | it=IT:HowTo:Use_POV-Ray_with_Blender/Developers
 }}

@@ Line 110: / Line 110: @@
 Single line comments begin with a hash (#) character immediately followed by one blank space and the comment starting with a capital but not ending with a dot. They can be added  after a short enough line of code (leave one blank space before the #).
-For instance, at the beginning of the file, the comment
+One of the text formatting / coding style guideline to use is [https://www.python.org/dev/peps/pep-0008/ PEP8] so, for instance, you should take care to make short enough lines throughout all the script's files of less than 79 characters and less than 72 for docstrings (see below) or comments.
-<source lang="py"># <pep8 compliant></source>
-means that one of the text formatting / coding style guideline to use is [https://www.python.org/dev/peps/pep-0008/ PEP8] so, for instance, you should take care to make short enough lines throughout all the script's files of less than 79 characters and less than 72 for docstrings (see below) or comments.
+Periodically the Blender Foundation runs checks for this pep8 compliance on blender scripts.
-Note that this very comment is a special syntax: Periodically the Blender Foundation runs checks for pep8 compliance on blender scripts, for scripts to be included in this check add this line as a comment at the top of the script.
+The tolerated line length ended up to culminate at 100 characters.
 Other rules include

@@ Line 60: / Line 60: @@
 <br/>
-===metadonnées de l'add-on===
+===Add-on's metadata===
 <source lang="py">
 bl_info = {

@@ Line 60: / Line 60: @@
 <br/>
-===add-on’s metadata===
+===metadonnées de l'add-on===
 <source lang="py">
 bl_info = {

@@ Line 13: / Line 13: @@
 <font size="+2">[[HowTo:Use_POV-Ray_with_Blender/Developers|▼ Developer's page]]</font>
 </td>
-<td width=33% align=center>[[File:POVExporterLogo.png|center|200px|link=https://extensions.blender.org/add-ons/povable]]</td>
+<td width=33% align=center>[[File:POVExporterLogo.png|center|100px|link=https://extensions.blender.org/add-ons/povable]]</td>
 <td width=33% bgcolor=#EEEEEF align=right>
 <font size="+2">[[HowTo:Use_POV-Ray_with_Blender|Go To User's page ►]]</font></td></tr>

@@ Line 46: / Line 46: @@
 </div>
-The Blender to POV-Ray add-on and vice versa (aka "Bpover") started out as a single Python file.
+The Blender to POV-Ray add-on and vice versa (aka "POV@Ble") started out as a single Python file.
 To be compliant with blender add-on packaging system this add-on had to:
 *provide some general information about the add-on: its name and version,

@@ Line 3: / Line 3: @@
    | en=HowTo:Use_POV-Ray_with_Blender/Developers
    | fr=FR:HowTo:Use_POV-Ray_with_Blender/Developers
 }}