Blender Import Guide - Revision history

imported>Tsukihime at 05:17, 6 February 2012

2012-02-06T05:17:21Z

← Older revision	Revision as of 05:17, 6 February 2012
(No difference)

imported>Tsukihime at 05:17, 6 February 2012

2012-02-06T05:17:21Z

← Older revision		Revision as of 05:17, 6 February 2012
Line 369:		Line 369:

	TODO		TODO
			[[Category:Tutorials]]

173.242.115.180: oops

2012-02-01T07:01:16Z

oops

← Older revision	Revision as of 07:01, 1 February 2012
(No difference)

173.242.115.180: oops

2012-02-01T07:01:16Z

oops

← Older revision		Revision as of 07:01, 1 February 2012
Line 29:		Line 29:
	*strings are handled differently		*strings are handled differently

	For both you will need to import and use the module “struct”. “struct” is a module for converting data read binary ~~from~~ file to the needed type, like integer, short, long or float.		For both you will need to import and use the module “struct”. “struct” is a module for converting data read from binary file to the needed type, like integer, short, long or float.

	==Basic things every script will need==		==Basic things every script will need==

173.242.115.180: /* Why Blender/Python? */

2012-02-01T07:00:08Z

Why Blender/Python?

← Older revision	Revision as of 07:00, 1 February 2012
(No difference)

173.242.115.180: /* Why Blender/Python? */

2012-02-01T07:00:08Z

Why Blender/Python?

← Older revision		Revision as of 07:00, 1 February 2012
Line 29:		Line 29:
	*strings are handled differently		*strings are handled differently

	For both you will need to import and use the module “struct”. “struct” is a module for converting data read from file to the needed type, like integer, short, long or float.		For both you will need to import and use the module “struct”. “struct” is a module for converting data read binary from file to the needed type, like integer, short, long or float.

	==Basic things every script will need==		==Basic things every script will need==

95.109.103.113: /* Transforming your script into a Blender add-on */

2012-01-29T16:50:53Z

Transforming your script into a Blender add-on

← Older revision	Revision as of 16:50, 29 January 2012
(No difference)

95.109.103.113: /* Transforming your script into a Blender add-on */

2012-01-29T16:50:53Z

Transforming your script into a Blender add-on

← Older revision		Revision as of 16:50, 29 January 2012
Line 351:		Line 351:
	==Transforming your script into a Blender add-on==		==Transforming your script into a Blender add-on==

	Before Blender 2.5, scripts like importers/exporters had to be placed in a special folder to be usable by Blender. Now it's still the same, but you don't need to place them manually, you can just "install" them: select them by GUI and click install and Blender will copy the script to the right place ~~manually~~. Scripts which can be installed are called "add-ons". You need to add few more things to your script in order for Blender to recognize it as a valid add-on.		Before Blender 2.5, scripts like importers/exporters had to be placed in a special folder to be usable by Blender. Now it's still the same, but you don't need to place them manually, you can just "install" them: select them by GUI and click install and Blender will copy the script to the right place automatically. Scripts which can be installed are called "add-ons". You need to add few more things to your script in order for Blender to recognize it as a valid add-on.
	Add this to the beginning of your script:		Add this to the beginning of your script:

74.120.13.132: /* Adding GUI to your script */

2012-01-29T16:37:26Z

Adding GUI to your script

← Older revision	Revision as of 16:37, 29 January 2012
(No difference)

74.120.13.132: /* Adding GUI to your script */

2012-01-29T16:37:26Z

Adding GUI to your script

← Older revision		Revision as of 16:37, 29 January 2012
Line 307:		Line 307:
	The new way of creating GUI in Blender 2.5+ has become pointlessly complicated. Before it was just a function call, now you need to create a class with bunch of variables inside. I don't think you need to learn how these stuff work. Besides, all importers can get by with the same generic file-browser GUI. I'll just tell you what you need to change to use your own name for the importer/exporter in the GUI, don't worry about the rest, just copy-paste it at the end of your script.		The new way of creating GUI in Blender 2.5+ has become pointlessly complicated. Before it was just a function call, now you need to create a class with bunch of variables inside. I don't think you need to learn how these stuff work. Besides, all importers can get by with the same generic file-browser GUI. I'll just tell you what you need to change to use your own name for the importer/exporter in the GUI, don't worry about the rest, just copy-paste it at the end of your script.

	Here's a generic importer/exporter GUI. ~~You~~ format should appear in "Info window -> File -> Import" or "Info window -> File -> Export" respectively.		Here's a generic importer/exporter GUI code. Your format should appear in "Info window -> File -> Import" or "Info window -> File -> Export" respectively.

	<pre class="codeblock">		<pre class="codeblock">
			from bpy.props import *
			from bpy_extras.io_utils import ExportHelper, ImportHelper

	class IMPORT_OT_yourformatname(bpy.types.Operator, ImportHelper):		class IMPORT_OT_yourformatname(bpy.types.Operator, ImportHelper):
	bl_idname= "import_scene.yourformat"		bl_idname= "import_scene.yourformat"
Line 317:		Line 320:
	filter_glob = StringProperty(default="*.defaultextension", options={'HIDDEN'})		filter_glob = StringProperty(default="*.defaultextension", options={'HIDDEN'})

	filepath= StringProperty(name="File Path", description="Filepath used for importing the yourformatname file", maxlen=1024, default="")		filepath= StringProperty(name="File Path", description="Filepath
			used for importing the yourformatname file", maxlen=1024, default="")

	def execute(self, context):		def execute(self, context):