Property list - Revision history

Cholmondely: Tagged as Legacy scripting

2021-08-09T09:38:01Z

Tagged as Legacy scripting

Milo: fix syntax (missing slash in closing array tag) in XML dictionary format example

2020-06-20T13:22:38Z

fix syntax (missing slash in closing array tag) in XML dictionary format example

Diziet Sma: /* Conversion */

2014-01-18T03:43:04Z

‎Conversion

Diziet Sma: /* Conversion */

2014-01-18T03:42:10Z

‎Conversion

Diziet Sma: /* Conversion */

2014-01-18T03:41:21Z

‎Conversion

Eric Walch: Updated an outdated link

2013-03-17T13:33:31Z

Updated an outdated link

Diziet Sma: Added Linux-friendly version of script

2013-01-25T20:34:21Z

Added Linux-friendly version of script

Eric Walch: typo

2012-07-16T11:13:20Z

typo

Eric Walch: boolean: added casing info

2012-05-07T07:46:19Z

boolean: added casing info

Eric Walch: typo

2011-08-31T21:20:23Z

typo

← Older revision		Revision as of 09:38, 9 August 2021
Line 125:		Line 125:

	[[Category:Oolite]]		[[Category:Oolite]]
		+	[[Category:Legacy scripting]]
	[[Category:Oolite scripting]]		[[Category:Oolite scripting]]

@@ Line 43: / Line 43: @@
 In OpenStep format, dictionaries are contained in braces, with key and value separated by <code>=</code> signs and each pair followed by a semicolon: <code>{length = 42; width = 36.5; "long name" = "this is a thing with a really quite long name"; attributes = (hairy, muscular);}</code>.
-In XML format, dictionaries are contained in <code>&lt;dict&gt;</code> tags, with keys specified by <code>&lt;key&gt;</code> tags and immediately followed by values with whatever tag is appropriate for the value type: <code>&lt;dict&gt;&lt;key&gt;length&lt;/key&gt;&lt;integer&gt;42&lt;/integer&gt; &lt;key&gt;width&gt;&lt;real&gt;36.5&lt;/real&gt; &lt;key&gt;long name&lt;/key&gt;&lt;string&gt;this is a thing with a really quite long name&lt;/string&gt; &lt;key&gt;attributes&lt;/key&gt;&lt;array&gt;&lt;string&gt;hairy&lt;/string&gt;&lt;string&gt;muscular&lt;/string&gt;&lt;array&gt;&lt;/dict&gt;</code>.
+In XML format, dictionaries are contained in <code>&lt;dict&gt;</code> tags, with keys specified by <code>&lt;key&gt;</code> tags and immediately followed by values with whatever tag is appropriate for the value type: <code>&lt;dict&gt;&lt;key&gt;length&lt;/key&gt;&lt;integer&gt;42&lt;/integer&gt; &lt;key&gt;width&gt;&lt;real&gt;36.5&lt;/real&gt; &lt;key&gt;long name&lt;/key&gt;&lt;string&gt;this is a thing with a really quite long name&lt;/string&gt; &lt;key&gt;attributes&lt;/key&gt;&lt;array&gt;&lt;string&gt;hairy&lt;/string&gt;&lt;string&gt;muscular&lt;/string&gt;&lt;/array&gt;&lt;/dict&gt;</code>.
 == Root element ==

@@ Line 114: / Line 114: @@
 == Conversion ==
-Technically the XML plists are the best, but they are only fully supported on Mac systems. Without a plist editor, the plists are not as easy to read or write as OpenStep plists. However, those editors are only easily available for the Mac. Windows and Linux users will have to rely on text editors to edit those plists. Therefore it is advised to write everything in open step format.<br>
+Technically the XML plists are the best, but they are only fully supported on Mac systems. Without a plist editor, the plists are not as easy to read or write as OpenStep plists. However, those editors are only easily available for the Mac. Windows and Linux users will have to rely on text editors to edit those plists. Therefore it is advised to write everything in open step format.
 Converting xml to open step can be done by a python script, written by Cdr. Jettison: [http://www.box.net/shared/g79rnfx4jcp1do35liin download python conversion script] ('' xml plist must be free of comment for the script to work'')

@@ Line 114: / Line 114: @@
 == Conversion ==
-Technically the XML plists are the best, but they are only fully supported on Mac systems. Without a plist editor, the plists are not as easy to read or write as OpenStep plists. Those editors are only easily available for the Mac. Windows and linux users will have to rely on text editors to edit those plists. Therefore it is advised to write everything in open step format.<br>
+Technically the XML plists are the best, but they are only fully supported on Mac systems. Without a plist editor, the plists are not as easy to read or write as OpenStep plists. However, those editors are only easily available for the Mac. Windows and Linux users will have to rely on text editors to edit those plists. Therefore it is advised to write everything in open step format.<br>
 Converting xml to open step can be done by a python script, written by Cdr. Jettison: [http://www.box.net/shared/g79rnfx4jcp1do35liin download python conversion script] ('' xml plist must be free of comment for the script to work'')

@@ Line 114: / Line 114: @@
 == Conversion ==
-Technically are the XML plist the best, but they are only fully supported on Mac systems. Without a plist editor, the plists are not as easy to read or write as OpenStep plists. Only for the mac are those editors easy available. Window and linux users will rely in text editors to edit those plists. Therefore it is advised to write everything in open step format.<br>
+Technically the XML plists are the best, but they are only fully supported on Mac systems. Without a plist editor, the plists are not as easy to read or write as OpenStep plists. Those editors are only easily available for the Mac. Windows and linux users will have to rely on text editors to edit those plists. Therefore it is advised to write everything in open step format.<br>
 Converting xml to open step can be done by a python script, written by Cdr. Jettison: [http://www.box.net/shared/g79rnfx4jcp1do35liin download python conversion script] ('' xml plist must be free of comment for the script to work'')

@@ Line 5: / Line 5: @@
 A property list is an abstract structure which can be represented files using at least five different formats. Since Oolite uses two different implementations of property list support, one on Mac&nbsp;OS&nbsp;X and another on other platforms, it can’t consistently read all these formats.
-Two formats are recommended for Oolite: the traditional [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Articles/OldStylePListsConcept.html  OpenStep format], which is easy to read, and the [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Articles/XMLPListsConcept.html XML format], which is more flexible. The other formats are Apple binary format (which can be read by both implementations, but is not human-readable), and the GNUstep text and binary formats, which are not supported under Mac&nbsp;OS&nbsp;X.
+Two formats are recommended for Oolite: the traditional [http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/PropertyLists/Introduction/Introduction.htmll  OpenStep format], which is easy to read, and the [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Articles/XMLPListsConcept.html XML format], which is more flexible. The other formats are Apple binary format (which can be read by both implementations, but is not human-readable), and the GNUstep text and binary formats, which are not supported under Mac&nbsp;OS&nbsp;X.
 While the OpenStep format does not support all the data types used by Oolite – specifically, it does not support [[#integer|integers]], [[#real|reals]] or [[#boolean|booleans]] – Oolite can in most cases automatically convert [[#string|strings]] to these types starting with Oolite 1.69. (If you find an exception, please report it.) As such, the types can be used interchangeably. In prior versions of Oolite, some types, especially booleans, could not be converted automatically, so XML format was required for some property lists.

@@ Line 27: / Line 27: @@
 === boolean ===
-A boolean is either of the values ''true'' or ''false''. In XML format, the tags <code>&lt;true/&gt;</code> and <code>&lt;false/&gt;</code> can be used. OpenStep format does not support booleans. However, as of Oolite 1.69, a number of different methods can be used to represent them: any of the strings <code>"true"</code>, <code>"yes"</code> or <code>"on"</code> may be used to represent ''true'', and any of the strings <code>"false"</code>, <code>"no"</code> or <code>"off"</code> may be used to represent ''false''. Also the uppercase variants of these keywords can be used as casing is ignored for these booleans.  Additionally, the number 0 is interpreted as ''false'' and any other number as ''true'' (but see [[#fuzzy boolean|fuzzy boolean]] below). The recommended form is to use <code>"yes"</code> and <code>"no"</code> to keep a consistent syntax that is not cunfusing.
+A boolean is either of the values ''true'' or ''false''. In XML format, the tags <code>&lt;true/&gt;</code> and <code>&lt;false/&gt;</code> can be used. OpenStep format does not support booleans. However, as of Oolite 1.69, a number of different methods can be used to represent them: any of the strings <code>"true"</code>, <code>"yes"</code> or <code>"on"</code> may be used to represent ''true'', and any of the strings <code>"false"</code>, <code>"no"</code> or <code>"off"</code> may be used to represent ''false''. Also the uppercase variants of these keywords can be used as casing is ignored for these booleans.  Additionally, the number 0 is interpreted as ''false'' and any other number as ''true'' (but see [[#fuzzy boolean|fuzzy boolean]] below). The recommended form is to use <code>"yes"</code> and <code>"no"</code> to keep a consistent syntax that is not confusing.
 Previous versions of this page indicated that numbers could be used as booleans in OpenStep-format property lists in any version of Oolite. This is incorrect and such usage will not work with versions prior to 1.69.

@@ Line 116: / Line 116: @@
 == Conversion ==
 Technically are the XML plist the best, but they are only fully supported on Mac systems. Without a plist editor, the plists are not as easy to read or write as open step plists. Only for the mac are those editors easy available. Window and linux users will rely in text editors to edit those plists. Therefor it is advised to write everything in open step format.<br>
-Converting xml to open step can by done by a python script, written by Cdr. Jettison: [http://www.box.net/shared/g79rnfx4jcp1do35liin download python conversion script] ('' xml plist must be free of comment for the script to work'')
+Converting xml to open step can be done by a python script, written by Cdr. Jettison: [http://www.box.net/shared/g79rnfx4jcp1do35liin download python conversion script] ('' xml plist must be free of comment for the script to work'')
 ==Links==