Screen Templates

This page will give you an overview over the available templates, their limitations and their structure for you to use with MARK Display.

Overview

Proglove uses a template approach to display information in an easy to understand and easy to use way. Templates are pre-defined layouts on the screen to ease the integration effort and ensure the best possible user-experience. This way you can focus on refining the process for your worker and do not have to think a lot about screen layouting. Also it will give you focus to reduce the amount of datapoints you want to present to your workers.

Terminology

Term	Description
Template	Templates are pre-defined layouts on the screen to easy the integration effort and ensure the best possible user-experience.
Template ID	Template IDs are unique identifiers for each template layout, which needs to be set during the integration process.
(Template) Layout	(Template) Layouts define the general structure of screen. Example: 2 or 3 fields.
(Template) Field	(Template) Field is a field/cell within the Layout. One Layout can contain one or more fields.
Field ID	Each field is referenced by a unique ID. The order of Field IDs should follow the western writing direction (primary: left to right; secondary top to bottom
Header	Each Template field may contain a Header. Header can be used as a description of the shown content. Example: “Quantity”
Content	Each Template field contains a Content (datapoint(s)). Example: “165 pcs”.

Best practices

If you want to set a screen on the MARK Display, it is a best practise to first think about how many datapoints are really needed by the worker at the time. Then try to reduce this number down to a minimum. Usually the worker needs a maximum of three datapoints at any given time/step in the process.

When you know the amount of datapoints, pick the best fitting template from the list below. For dense information, which might even need a header to explain which datapoint is which, we recommend using the templates PG2 and PG3 for two and three datapoints respectively.

For use-cases in which you want to inform the worker about an event, we recommend using the PG1E, PG1C or PG1I templates depending on the kind of event.

For use-cases in which you want to inform the worker about an event and have to communicate information along with the event, we recommend using the PG2E, PG2C or PG2I templates depending on the kind of event.

Visual example

Example

Templates

PG	X	Y
PG = ProGLove Identifier of the company providing the template.	X = Number of Fields X Describes the number of fields which the user is able to set for unique content	Y = Secondary identifier The secondary identifier allows for special separation of templates with the same amount of fields. Think variants. E = Error C = Confirm I = Information

Limitations

For now we only support the "standard" characters of the western alphabet (big and small), numbers, most punctuation and the german "Umlaute" ä,ö,ü,Ä,Ö,Ü. Stay tuned for updates
Each header can take a maximum of 20 characters.
Each content can take a maximum of 40 characters.
On some fields the display will not automatically scale your content. Consult the list below to find out which. If auto-scaling is enabled, your provided content will be displayed as big as possible. Even considering line breaks if appropriate.
Headers will never be scaled.
Currently there is no way of creating custom templates. Stay tuned for updates

Here you can find a list of all the available templates. (Field) IDs are displayed in the purple boxes.