HowTo:Edit Missions:Python:Bindings - Revision history

pyramid at 10:28, 22 April 2008

2008-04-22T10:28:33Z

pyramid at 13:46, 21 April 2008

2008-04-21T13:46:33Z

pyramid at 09:10, 21 April 2008

2008-04-21T09:10:08Z

pyramid: /* VegaStrike C++ Funcions */

2008-03-28T15:52:40Z

‎VegaStrike C++ Funcions

Pirx at 18:16, 28 May 2005

2005-05-28T18:16:55Z

202.50.187.13 at 05:38, 23 March 2005

2005-03-23T05:38:37Z

202.50.187.13 at 02:39, 23 March 2005

2005-03-23T02:39:35Z

202.50.187.13 at 02:35, 23 March 2005

2005-03-23T02:35:49Z

Pirx: added categories

2005-03-21T15:21:01Z

added categories

202.50.187.13 at 05:44, 21 March 2005

2005-03-21T05:44:08Z

@@ Line 30: / Line 30: @@
 Feel free to add to the descriptions or to ask me about any that are unclear. I give you as follows the VS functions C++ names so you get type information as well!
-Note that these comments are also included in <code>[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/vegastrike/src/universe_util.h?rev=HEAD&content-type=text/vnd.viewcvs-markup src/universe_util.h]</code>
+Note that these comments are also included in '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/vegastrike/src/universe_util.h?view=markup src/universe_util.h]'''
 ===[[HowTo:Edit_Missions:Python:Bindings:Python|VegaStrike Python Funcions]]===
@@ Line 36: / Line 36: @@
 Many of these functions return <code>Unit *</code> (for python just Unit) However there is a very critical difference between a Python <code>Unit</code> and a C++ <code>Unit *</code>. If you have a Python <code>Unit</code> you may keep it across frames... it may turn null (check with <code>isNull()</code>), but you can still keep it.... (if it dies is when it turns null)... in C++ if you keep a <code>Unit *</code> across a frame you WILL cause random segfaults (bad things, hard to find) but ya...Python it's safe to keep <code>Unit</code>'s returned by functions...just be aware that between frames they may die and then bet tested <code>Null</code> with <code>isNull()</code>.
-The following comments are done with the python class as the arguments are clearly listed in '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/modules/stub/VS.py?rev=HEAD&content-type=text/vnd.viewcvs-markup modules/stub/VS.py]''' function :-)
+The following comments are done with the python class as the arguments are clearly listed in '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data4.x/modules/stub/VS.py?view=markup modules/stub/VS.py]''' function :-)
 [[Category:HowTos|Edit Missions:Python:Bindings]]
 [[Category:Development|Edit Missions:Python:Bindings]]

@@ Line 1: / Line 1: @@
 ==Vegastrike Utility Functions==
 Now that you can run complex python scripts that could even play minesweeper at the prompt, you probably want to interact with Vegastrike directly and "do" stuff like make ships, set objectives, and generally give the player a hard time.
@@ Line 46: / Line 38: @@
 The following comments are done with the python class as the arguments are clearly listed in '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/modules/stub/VS.py?rev=HEAD&content-type=text/vnd.viewcvs-markup modules/stub/VS.py]''' function :-)
-----
 [[Category:HowTos|Edit Missions:Python:Bindings]]
 [[Category:Development|Edit Missions:Python:Bindings]]

@@ Line 1: / Line 1: @@
 {{NAV_Manual |
 | previous=[[HowTo:Edit_Missions:Python:AI_scripts|AI Scripts]]
-| up=[[HowTo:Edit_Missions|Edit Missions]]
+| up=[[Development:Missions|Edit Missions]]
 | next=[[HowTo:Edit_Missions:Python:Summary|Python Summary]]
 }}
@@ Line 49: / Line 49: @@
 {{NAV_Manual |
 | previous=[[HowTo:Edit_Missions:Python:AI_scripts|AI Scripts]]
-| up=[[HowTo:Edit_Missions|Edit Missions]]
+| up=[[Development:Missions|Edit Missions]]
 | next=[[HowTo:Edit_Missions:Python:Summary|Python Summary]]
 }}
 [[Category:HowTos|Edit Missions:Python:Bindings]]
 [[Category:Development|Edit Missions:Python:Bindings]]

@@ Line 36: / Line 36: @@
 ===[[HowTo:Edit_Missions:Python:Bindings:CPP|VegaStrike C++ Funcions]]===
-Feel free to add to the descritptions or to ask me about any that are unclear. I give you as follows the VS functions C++ names so you get type information as well!
+Feel free to add to the descriptions or to ask me about any that are unclear. I give you as follows the VS functions C++ names so you get type information as well!
 Note that these comments are also included in <code>[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/vegastrike/src/universe_util.h?rev=HEAD&content-type=text/vnd.viewcvs-markup src/universe_util.h]</code>

@@ Line 16: / Line 16: @@
 </pre>
-then edit that file and replace with (newline)(space)(space) and you have a sample python stub so you can find out every mission that vegastrike exports.
+... then edit that file and replace with (newline)(space)(space) and you have a sample python stub so you can find out every mission that vegastrike exports.
-we try to keep these stubs as up to date as possible. Anyhow this lets you test your missions at the prompt by adding the two directories
+We try to keep these stubs as up to date as possible. Anyhow this lets you test your missions at the prompt by adding the two directories
 <pre>
- import sys
+import sys
- sys.path = sys.path + ['/home/blah/data/modules']
+sys.path = sys.path + ['/home/blah/data/modules']
- sys.path = sys.path + ['/home/blah/data/modules/stub']
+sys.path = sys.path + ['/home/blah/data/modules/stub']
- import VS
+import VS
- ...
+...
 </pre>
@@ Line 36: / Line 36: @@
 ===[[HowTo:Edit_Missions:Python:Bindings:CPP|VegaStrike C++ Funcions]]===
-Feel free to add to the descritptions or to ask me about any that are unclear. I give you as follows the VS functions C++ names so you get type information as well! Note that these comments are also included in '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/vegastrike/src/universe_util.h?rev=HEAD&content-type=text/vnd.viewcvs-markup src/universe_util.h]'''
+Feel free to add to the descritptions or to ask me about any that are unclear. I give you as follows the VS functions C++ names so you get type information as well!
 ===[[HowTo:Edit_Missions:Python:Bindings:Python|VegaStrike Python Funcions]]===
-Many of these functions return Unit * (for python just Unit) However there is a very critical difference between a Python Unit and a C++ Unit *. If you have a Python Unit you may keep it across frames... it may turn null (check with isNull()), but you can still keep it.... (if it dies is when it turns null)... in C++ if you keep a Unit * across a frame you WILL cause random segfaults (bad things, hard to find) but ya...Python it's safe to keep Unit's returned by functions...just be aware that between frames they may die and then bet tested '''Null''' with '''isNull()'''.
+Many of these functions return <code>Unit *</code> (for python just Unit) However there is a very critical difference between a Python <code>Unit</code> and a C++ <code>Unit *</code>. If you have a Python <code>Unit</code> you may keep it across frames... it may turn null (check with <code>isNull()</code>), but you can still keep it.... (if it dies is when it turns null)... in C++ if you keep a <code>Unit *</code> across a frame you WILL cause random segfaults (bad things, hard to find) but ya...Python it's safe to keep <code>Unit</code>'s returned by functions...just be aware that between frames they may die and then bet tested <code>Null</code> with <code>isNull()</code>.
 The following comments are done with the python class as the arguments are clearly listed in '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/modules/stub/VS.py?rev=HEAD&content-type=text/vnd.viewcvs-markup modules/stub/VS.py]''' function :-)
@@ Line 50: / Line 52: @@
 | next=[[HowTo:Edit_Missions:Python:Summary|Python Summary]]
 }}
-[[Category:HowTo|Edit Missions:Python:Bindings]] [[Category:Development|Edit Missions:Python:Bindings]]
+[[Category:HowTos|Edit Missions:Python:Bindings]]

← Older revision		Revision as of 02:39, 23 March 2005
Line 36:		Line 36:
	===[[HowTo:Edit_Missions:Python:Bindings:CPP\|VegaStrike C++ Funcions]]===		===[[HowTo:Edit_Missions:Python:Bindings:CPP\|VegaStrike C++ Funcions]]===

−	~~[[HowTo:Edit_Missions:Python:Bindings:C_plus_plus\|VegaStrike C++ Funcions]]~~
	Feel free to add to the descritptions or to ask me about any that are unclear. I give you as follows the VS functions C++ names so you get type information as well! Note that these comments are also included in '''src/universe_util.h''' ''Add link to CVS!''		Feel free to add to the descritptions or to ask me about any that are unclear. I give you as follows the VS functions C++ names so you get type information as well! Note that these comments are also included in '''src/universe_util.h''' ''Add link to CVS!''

@@ Line 34: / Line 34: @@
 I will try to give a brief description here...
-===[[HowTo:Edit_Missions:Python:Bindings:C_plus_plus|VegaStrike C++ Funcions]]===
+===[[HowTo:Edit_Missions:Python:Bindings:CPP|VegaStrike C++ Funcions]]===
 Feel free to add to the descritptions or to ask me about any that are unclear. I give you as follows the VS functions C++ names so you get type information as well! Note that these comments are also included in '''src/universe_util.h'''  ''Add link to CVS!''

← Older revision		Revision as of 15:21, 21 March 2005
Line 49:		Line 49:
	\| next=[[HowTo:Edit_Missions:Python:Summary\|Python Summary]]		\| next=[[HowTo:Edit_Missions:Python:Summary\|Python Summary]]
	}}		}}
		+	[[Category:HowTo\|Edit Missions:Python:Bindings]] [[Category:Development\|Edit Missions:Python:Bindings]]