Skip to content

The ViewTouch graphical interface: Pages

No0ne558 edited this page Oct 24, 2025 · 12 revisions

πŸ—οΈ ViewTouch Architecture & Interface System

🏷️ What is ViewTouch?

ViewTouch is a USA trademark referring to several components:


πŸ“„ Page Structure

πŸͺŸ X Window Foundation

  • Each 'page' = An X Window containing ViewTouch 'buttons'
  • Built-in textures: Background and surface textures coded directly for optimal performance
  • Network transparent: All pages work seamlessly across networks

🎯 PoS Software Uniqueness

Point of Sale software has unique requirements that few other applications share:

The graphical user interface is incomplete and must be completed by (or for) each user.

Key Characteristics:

  • πŸ“„ Page-centric: Everything revolves around pages and buttons
  • 🎯 User completion: Interface must be customized for each venue
  • 🧠 Intuitive design: Layout determines ease of use
  • πŸ”§ Authoring tools: Users can maintain their own interfaces

πŸ“ File System & Page Types

πŸ”’ System Pages (DO NOT MODIFY)

  • Purpose: Core system functionality
  • Location: /usr/viewtouch/bin/vt_data
  • IDs: Numbers less than zero
  • Content: Expansive collection of essential system pages
  • Language Support: F2 key enables translation to other languages

Download vt_data here

🎨 User-Created Pages (CUSTOMIZE THESE)

IDs: Numbers greater than zero

Required Page Types:

  • πŸͺ‘ Table Pages: Represent physical table layouts (tables.dat)
  • πŸ“‘ Tab Library Pages: Navigation helpers
  • πŸ“‡ Index Pages: Menu organization
  • 🍽️ Menu Item Pages: Food & beverage listings (menu.dat, zone_db.dat)

✏️ Interface Editing System

πŸ” Access Requirements

  • Login ID: 42 (Developer/Editor default)
  • Edit Mode Toggle: F1 key
    • Press F1 β†’ Enter Edit Mode
    • Press F1 β†’ Exit & Save changes
    • Press F11 β†’ Exit & Discard changes (emergency revert)

πŸ’‘ Editing Best Practices

  • Save Frequently: Press F1 twice to save, then re-enter Edit Mode
  • Tools: Intuitive, versatile, and easy to learn
  • Support: Initial setup + tutoring provided

πŸ“š ViewTouch Editing Documentation

πŸ“– Internal Documentation

ViewTouch documentation is largely internal to the application.

Access: System page explaining the integral editing tools

πŸŽ“ Learning Process

  1. Initial Setup: Restaurant table layout and menu provided
  2. Tutoring: 1-2 hours of personal training on tool usage
  3. Independence: Users learn to build and refine their own pages/buttons

🌐 Remote Viewing & Administration

πŸ“Ί Remote Page Viewing

View pages across networks using SSH with X forwarding:

ssh -X ipaddress /usr/viewtouch/openterm

Use Case: Support technicians can view any client's ViewTouch displays directly on their desktop.

πŸ–¨οΈ Remote Printer Administration

Monitor and administer PoS printers via CUPS through SSH port redirection:

ssh -L 6310:localhost:631 ipaddress

Browser Access: Set URL to localhost:6310 for full CUPS web interface.


πŸ›οΈ Architecture Summary

Component Purpose Location ID Range Editable
System Pages Core functionality vt_data < 0 ❌ No
Table Pages Table layouts tables.dat > 0 βœ… Yes
Menu Pages Food/beverage items menu.dat > 0 βœ… Yes
Zone Pages Menu organization zone_db.dat > 0 βœ… Yes

ViewTouch's architecture uniquely combines:

  • πŸ—οΈ X Window System foundation for network transparency
  • πŸ› οΈ Integrated authoring tools for user customization
  • 🌐 Remote administration capabilities
  • πŸ“± Touchscreen-optimized interface design

This foundation enables rapid deployment of customized Point of Sale solutions across diverse hospitality environments.

Clone this wiki locally