Missing components for the Tryal UI library

As we update Tryal.AI models to reflect a new web ready format, we need to consider what was missed in the initial development of Tryal UI. Tryal UI's prototype was designed to break the back of the most difficult challenges facing online Q&A exam systems.

We are currently missing the following

Multichoice component - Rendering multiple possible choices is essential particularly in support for non-edexcel format GCSEs (read as AQA). This is a fairly trivial expansion of existing components
LaTeX render component - It might make sense to in-house a rendering component for LaTeX maths strings, considering that we already do a lot of heavily lifting on the back of LaTeX having our own parser, renderer and tech core surrounding that might reduce future tech debt. Alternatively, a cheap polyfill that converts LaTeX to MathML would be useful for end-user developers in rapid prototyping phase
Table Component - This is possibly a novel design issue, wherein a few questions have table or table like structures which either are for display or for answer purposes (see for example line equation tables)
List Component - This is a fairly trivial issue. Some questions consist of list like lines, such as "here are 4 numbers". Because we glue LaTeX between each element of the list, it makes it needlessly hard to render on web. It makes sense to have a component for rendering this, if only for completeness
Image Component - As API 2.0 comes to Tryal.AI we are expanding support to graphical questions!!! We're doing this through the use of base64 image strings (for now). Although the bandwidth push is not ideal, it's much quicker to implement than a CDN level asset distribution system

We will update this list as new components are required to represent specific elements

tryal-ai / tryal-ui

Missing components for the Tryal UI library #2