And the documentation just keeps comming...

git-svn-id: svn://svn.code.sf.net/p/magicseteditor/code/trunk@598 0fc631ac-6414-0410-93d0-97cfa31319b6
This commit is contained in:
twanvl
2007-08-03 15:35:09 +00:00
parent dfe1140444
commit 2a2935de48
12 changed files with 130 additions and 8 deletions
+13
View File
@@ -21,6 +21,19 @@ When the value is longer then a single line it can be written indented on the fo
> T: Draw a card
> WW: Gain 1 life
--Order--
Usually the order in which keys appear in a file doesn't matter.
However some keys, like @mse version@ and @type@ must come first because they influence how the following keys are interpreted.
--Includes--
A heirachical file can contain a reference to another file:
>>>include file: <em>filename</em>
Where filename must be an absolute [[type:filename]].
That file is included literally into the current one; except for indentation, the included file never escapes from the level the 'include file' line is on.
--Example--
For example, a [[type:set]] might look like this:
>game: magic
+1
View File
@@ -9,6 +9,7 @@ The following types are stored in [[file:package]]s in the:
* [[type:symbol font]]
* [[type:export template]]
* [[type:locale]]
* [[type:include]]
The following types are stored in [[file:package]]s that can be located anywhere:
* [[type:set]]
Binary file not shown.

After

Width:  |  Height:  |  Size: 56 KiB

+19
View File
@@ -0,0 +1,19 @@
Style triangle
<img src="style-triangle.jpg" style="float:right;" alt=""/>A central idea of MSE is the separation of data and styling.
Consider a single card, say "Forest".
This card could be printed in an old set, for example Fifth Edition, using an old style frame.
The ''same'' card can also be put into a new fram in for instance Ninth Edition.
So the card (the data) is independent of the style, but both are based on the same game (description), i.e. Magic.
This distinction is made on two levels.
The three different types of packages, [[type:game]], [[type:stylesheet]] and [[type:set]].
They contain three different things, [[type:field]]s, [[type:style]]s and [[type:value]]s.
This is illustrated in the diagram on the right and in the following table.
| Description Looks Data
| High level [[type:Game]] [[type:Stylesheet]] [[type:Set]]
| [[type:Card]]
| Low level [[type:Field]] [[type:Style]] [[type:Value]]