Web Version Client Side
The web version of TTP 3.0 is a Single Page Application (SPA) built with HTML5, Knockout and jQuery. This is an open standard and the benefits are that it is not reliant on plugins, performs across most recent devices and operating systems (Windows, Mac, iOS and Android) including tablets and phones. The architecture of the web version also means that the code can be re-factored and the entire application re-engineered for specific clients if need be.
Currently supported browsers are: Internet Explorer 9+; Edge; Safari Desktop; Safari Mobile; Firefox4+; Google Chrome 14+; Opera.
If you choose to host your TTP books on your own server, you will need to run Windows Server 2008+, IIS 7+ and Windows SQL Server 2008+. There are detailed server configuration instructions.
Turning the Pages is not CPU-dependent and the main constraint will be bandwidth as it serves many images in quick succession for each user (all the pages of a book download as thumbnails at book launch, plus 6 high-resolution pages). This means you should be conservative in using TTP on a VM if many other services are running on the server that would consume port bandwidth. For storage purposes, you should calculate in the region of 500k per page or 2500k for Deep Zoom books.
The kiosk version runs under Windows 7/Vista/8/10 and requires Microsoft .NET framework 3.5 SP1+. Additionally .NET 4.6.1+ is required to utilise the latest kiosk version which has the updated UI and 4k page image support. Follow the installation guide for more information. By default, the TTP Content Management System generates kiosks that have no external dependencies. Media are local and the database contents are exported as local XML. This means a kiosk can be copied to a memory stick and run anywhere. It is possible, however, to configure kiosks to draw assets and metadata from a central server, which may be desirable if content is frequently changing. Contact us for more information.
TTP Content Management System
The CMS is a standalone application that runs under Windows. By default it is configured to generate both web and kiosk versions and therefore requires a database connection. This can be the Armadillo TTP server, or one of your own. In either case, the CMS has to be configured to upload to that server which is done before we supply the CMS to you.