@problem@
	@problemtype@
		description
	@;problemtype@
	@name@
		tutorial_0_basic_syntax
	@endname@
	@preamble@
		x = 5
		text = "the variable x"
	@;preamble@
	@content@
		This is a simple example of a "problem file" for the MECK system. Every such file (which should have the file ending ".xmu") needs to specify a problem type (in this case 'description') as well as the name of the problem ("tutorial_0_basic_syntax") and the content of the problem.
		
		There are currently six available problem types: 'description', 'embedded', 'truefalse', 'dragdrop', 'upload' and 'essay'. The most common and most versatile problem type is the 'embedded' type, which will allow for combining multiple answer fields, possibly of different kinds, at any position within the main problem text. The 'description' type used here does not contain any questions or answer fields, but is meant for providing additional information in the exam, (a table of contents for example). The other problem types are introduced in later tutorials.
		
		The name of the problem will be used in the identifier of the problem in the moodle question bank. It will also be appended to the output file name in certain cases.
		
		Before the acutal content, an optional 'preamble' block can be inserted for any problem type. This preamble is executed as Python code every time the problem file is compiled. In particular, you can easily assign variables; in this case, for example, the variable with the name "x" is assigned the value 5.
		
		The actual content, i.e. this text, determines what will be shown in the moodle question after importing the compiled xml file into a moodle quiz. Within the content, you can directly access any variables defined in the preamble. For example,
			@text@ has the value @x@
		will show up as "the variable x has the value 5" after compilation. More generally, all code between two "at" symbols whill be evaluated by a Python interpreter; the return value will then be converted into a string and placed in the the corresponding position within the content.
		
		You can see an approximation of the compiled content if you enable the debug mode; in that case, an html file called "debug.html" will be created in the output directory. The debug mode can be activated and deactived by editing the "MECK.cfg" file found in the "config" folder, by using command line arguments or by adding a 'config' section to the problem file (see Tutorial 7).
	@;content@
@;problem@