Windows Mobile 6.5 Widget Runtime Framework

Windows Mobile 6.5 introduced a dedicated web widget runtime framework that allowed developers to build and execute standalone, web-based applications using standard web technologies. This article details the specific runtime engine included in the operating system, the technical standards it utilized, and how it executed web widgets on mobile devices without requiring a full desktop-style browser interface.

The Windows Mobile Widgets Engine

The framework included in Windows Mobile 6.5 is the Microsoft Widgets Engine (commonly referred to as the Windows Mobile Widgets runtime). Built directly into the OS, this runtime allowed lightweight client-side applications—known as Windows Mobile Widgets—to run as standalone programs independent of the primary browser window.

Underlying Technology and Web Standards

The widget runtime was powered by the updated Internet Explorer Mobile 6 rendering engine. By leveraging this browser core, the framework supported modern web development technologies of its era, including:

  • HTML/XHTML: For defining the user interface structure.
  • Cascading Style Sheets (CSS): For styling and dynamic layouts.
  • JavaScript / JScript: For logic, interactivity, and asynchronous network requests (AJAX).
  • Document Object Model (DOM): For dynamic manipulation of on-screen elements.

Packaging and W3C Compliance

Microsoft aligned the Windows Mobile 6.5 widget architecture with the W3C Widgets 1.0 specification. Web-based widgets were distributed as archive packages using the .wgt file format, which were essentially standard ZIP archives containing:

  1. config.xml: An XML configuration manifest specifying widget metadata, security permissions, icons, author information, and the entry point (start file).
  2. HTML Pages: The primary entry point (typically index.html) and any sub-pages.
  3. Assets: Associated JavaScript files, CSS stylesheets, and media assets.

When an end user launched a .wgt package, the Windows Mobile Widgets runtime parsed the configuration file, rendered the local HTML markup via the IE Mobile 6 engine, and executed the application in its own chromeless window.