Web Version Client Side
Currently supported browsers are: Internet Explorer 9; Internet Explorer 10; Safari Desktop; Safari Mobile; Firefox4+; Google Chrome 14+; Opera. For Internet Explorer 6, 7 and 8 we recommend the use of the Google ChromeFrame plugin if users don’t want to use a more recent browser. ChromeFrame can be downloaded from here. We have a browser-detection script that clients may want to deploy to offer users of IE 6, 7, and 8 other options.
The web version also supports multi-touch and this is particularly effective on iOS and Windows 8 devices. The application is optimised for use on screens with a minimum resolution of 1024 x 768 pixels.
If you choose to host your TTP books on your own server, you will need to run Windows Server 2003+, IIS 6 and Windows SQL Server Express+. There are detailed server configuration instructions here.
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.
Kiosks run under Windows XP, 7, Vista or 8 and require the .NET 3.5+ framework, which may not be installed by default under Windows 8. That framework can be downloaded from here. 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 freqently changing. Contact us, if you’d like this set up.
TTP Content Management System
The CMS is 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.