Templates
All about Templates (aka proto-maps)
You can think of templates as being like Lego bricks: modular pieces to build upon.
Templates are like Maps or fragments of Maps. They have the same basic structure as a set of Nodes, Links and Objects. We have made them much more flexible than the limited set of templates that could be inserted into an OLab3 map.
In principle, you could make any Map into a Template, using the ‘Save as Template’ icon in the Map Designer.
But there are downsides to making really complex Templates. It is generally better to create a complex Map by inserting smaller templates into it, piece by piece.
You can start your Map design from a Template, such as the Starter Template.
Then you can insert more small Templates into your Map as you need them. You may need to re-centre your Designer viewport so that the new Template is not dropped on top of a bunch of existing Nodes -- this can be quite messy.
You can also create new Templates by saving an existing map or fragment as a Template, using the ‘Save as Template’ icon in the Map Designer.
Although they are not quite the same as other Objects, you can still apply a scope to a Template. Generally these will be server-level and course-level scope for most authors. It does not make much sense to create Templates with map-level scope. Only core devs will be able to create Templates with Global scope.
- 1.Templates are usually simpler and not intended to be played by themselves.
- 2.Maps must have at least one Root Node so that they can be played.
- 3.Templates often will not have a Root Node so that they can be more cleanly inserted into an existing map.
- 4.If there are Questions embedded in a Template, they will usually be server-level in scope.
- 5.We do not recommend embedding Counters in a Template. While it can be done, it often causes confusion.
- 6.There may be a Theme attached to a Template
Last modified 3yr ago