TreFile Template - Revision history

Exca at 10:57, 21 March 2007

2007-03-21T10:57:43Z

2007-03-16T15:02:13Z

‎Note

2007-03-16T10:46:43Z

‎Note

2007-03-15T20:41:50Z

‎Note

2007-03-15T18:53:48Z

‎Note

2007-03-15T18:53:30Z

‎Note

2007-03-15T18:52:50Z

‎Note

2007-03-15T15:07:16Z

2007-03-15T14:28:04Z

‎TSF - '''Tre Sub File (Purpose)'''

2007-03-15T13:37:04Z

@@ Line 28: / Line 28: @@
 |identifier used for later reference
 |}
-Here is a list of the different templates at your disposal (yes colors suck a bit atm, you can change them, [http://en.wikipedia.org/wiki/List_of_colors look here for palette]):
+Here is a list of the different templates at your disposal:
-{| class="wikitable"
+{{field types}}
-|{{sbyte}}
-|sbyte
-|{{byte}}
-|byte
-|{{bool}}
-|bool
-|-
-|{{short}}
-|short
-|{{ushort}}
-|ushort
-|-
-|{{int}}
-|int
-|{{uint}}
-|uint
-|{{float}}
-|float
-|-
-|{{long}}
-|long
-|{{ulong}}
-|ulong
-|{{double}}
-|double
-|-
-|{{ansistring}}
-|ansistring
-|{{unicodestring}}
-|unicodestring
-|}
 =Note=

@@ Line 67: / Line 67: @@
 *snow> We can fix the mistakes, but I dont want to be changing templates to a new colour scheme 6 months into the project.
 *exca> also, i'd like to point out that if you edit the [[Packet_Template]] upper left table (the one with types), as stated in the PM I sent you, you'll see that the types are not templated at the moment, hence why i started mines in the first place. So if you're ok with that i'll modify the list keeping the current colors and adding the new types while modifying a bit some names that makes no direct sense: for example, the byte type does not exist in C++, uint64 does not either and long are probably 32bits (unless running a 64bits OS which i sprobably not the case for SWG). In an other way i defined my types templates using the C# types (not appropritate for C++ code as same types does not share the same values). Maybe we should statuate about the values in a more pragmatic way when describing files and protocols. Here's the info we need about each field to describe them correctly cross language:
-*number of bytes:1, 2, 4, 8, n or 2n (1/2/4/8/n/N ?)
+**number of bytes:1, 2, 4, 8, n or 2n (1/2/4/8/n/N ?)
-*little or big endianess (L/B ?)
+**little or big endianess (L/B ?)
-*signed or unsigned (U ?)
+**signed or unsigned (U ?)
-*integer, real or string (I/R/S ?)
+**integer, real or string (I/R/S ?)
 I have yet no precise idea of a clear way to write it. Just ideas. What do you all think?

@@ Line 64: / Line 64: @@
 =Note=
 *Snow> Exca, look at the existing templates for the colour scheme, it's already been defined for all the values you're looking at...
-*Exca> if you're talking about this: [[Packet_Template]] my opinion is: it contains mistakes, not all the types are defined, and an uint is not an int.
+*exca> if you're talking about this: [[Packet_Template]] my opinion is: it contains mistakes, not all the types are defined, and an uint is not an int.
 *snow> We can fix the mistakes, but I dont want to be changing templates to a new colour scheme 6 months into the project.

← Older revision		Revision as of 20:41, 15 March 2007
Line 65:		Line 65:
	*Snow> Exca, look at the existing templates for the colour scheme, it's already been defined for all the values you're looking at...		*Snow> Exca, look at the existing templates for the colour scheme, it's already been defined for all the values you're looking at...
	*Exca> if you're talking about this: [[Packet_Template]] my opinion is: it contains mistakes, not all the types are defined, and an uint is not an int.		*Exca> if you're talking about this: [[Packet_Template]] my opinion is: it contains mistakes, not all the types are defined, and an uint is not an int.
		+	*snow> We can fix the mistakes, but I dont want to be changing templates to a new colour scheme 6 months into the project.

@@ Line 64: / Line 64: @@
 =Note=
 *Snow> Exca, look at the existing templates for the colour scheme, it's already been defined for all the values you're looking at...
-*Exca> if you're talking about this: [Packet_Template] my opinion is: it contains mistakes, not all the types are defined, and an uint is not an int.
+*Exca> if you're talking about this: [[Packet_Template]] my opinion is: it contains mistakes, not all the types are defined, and an uint is not an int.

← Older revision		Revision as of 18:52, 15 March 2007
Line 64:		Line 64:
	=Note=		=Note=

−	Exca, look at the existing templates for the colour scheme, it's already been defined for all the values you're looking at...	+	Snow> Exca, look at the existing templates for the colour scheme, it's already been defined for all the values you're looking at...
		+	Exca> if you're talking about this: [Packet_Template] my opinion is: it contains mistakes, not all the types are defined, and an uint is not an int.

← Older revision		Revision as of 15:07, 15 March 2007
Line 61:		Line 61:
	\|unicodestring		\|unicodestring
	\|}		\|}
		+
		+	=Note=
		+
		+	Exca, look at the existing templates for the colour scheme, it's already been defined for all the values you're looking at...

@@ Line 2: / Line 2: @@
 ==TSF - '''Tre Sub File (Purpose)'''==
 {| class="wikitable"
-|Understood at||{{0P}}||{{25P}}||{{50P}}||{{75P}}||{{100P}}
+|Understood at
 |}
 {{Box_TREformats|TSF ''format''|