You have a problem – 64kb leaves you just enough room for an 8-bit, low-density image in your application. But you wanted to take advantage of native resolution with dazzling crystal-clear graphics. Or, maybe you wanted to embed an MP3 file or JPEG photo in your Palm application executable. It’s time for a revolution in resource management. Resource², a component designed specifically for Saguaro, is your solution. If you know how to use fread() or ReadFile(), you already know how to use Resource². Thanks to the sophisticated features of Resource², every resource in your executable can be read/used as if it were a file stored in VFS. Unlike other resource managers, Resource² reads resources with zero overhead making it the most practical solution for mobile/embedded devices. And, with its multiplatform design – supporting Palm OS, Tapwave, Windows Mobile, and Windows Mobile Smartphone – you can finally say goodbye to the hassles of resource management across multiple platforms.

Use the provided utility, Resource Packager, to build resource packages.(1) Much like a file archive, a resource package is a collection of multiple files stored as a single file on disk. Resource Packager does everything necessary to squeeze large resources within the tight confines of mobile operating systems – such as splitting a resource package into 64KB sections to make it compatible with Palm OS. Just drag your resource files into Resource Packager, select Export As Resource Package, and rebuild your application binary. Resource management has never been this easy.

  • Written entirely in C (Win32-style) for ease of use and portability.
  • Resource access is similar to VFS file access. Simply call R2ReadResource() to read the contents of a resource.
  • Resource reading has zero memory overhead. On Palm OS, a R2_RPKG_DBCACHE flag is provided to optimize performance on NVFS-based devices. In this case, a read-ahead cache (no larger than 64KB) is used.
  • Resource contents can be read into dynamic memory and, on Palm OS, storage/feature memory.
  • Includes Resource Packager, a utility designed to build resource packages.(1)
  • Supports both ANSI and Unicode for Win32(2) applications.
  • Delivered as CodeWarrior 9.3-compatible static 68k library (*.lib) for Palm OS 5.
  • Delivered as CodeWarrior 9.3-compatible static ARM library (*.a) for Tapwave Zodiac and Visual C++ 6 compatible static x86 library (*.lib).
  • Delivered as eMbedded Visual C++ 3 compatible static libraries (*.lib) for Pocket PC 2000, Pocket PC 2002, and Microsoft Smartphone 2002.
  • Delivered as eMbedded Visual C++ 4 compatible static libraries (*.lib) for Windows Mobile 2003 and Windows Mobile 2003 for Smartphone.
  • Delivered as Visual Studio 2005 compatible static libraries (*.lib) for Windows Mobile 2003, Windows Mobile 2003 for Smartphone, Windows Mobile 5.0, and Windows Mobile 5.0 for Smartphone.
  • Palm OS 5
  • Tapwave Zodiac (TNA applications)
  • Pocket PC 2000 (ARM, MIPS, SH3, x86 Emulator)
  • Pocket PC 2002 (ARM, x86 Emulator)
  • Windows Mobile 2003 (ARM, x86 Emulator)
  • Windows Mobile 5.0 (ARM, x86 Emulator)
  • Microsoft Smartphone 2002 (ARM, x86 Emulator)
  • Windows Mobile 2003 for Smartphone (ARM, x86 Emulator)
  • Windows Mobile 5.0 for Smartphone (ARM, x86 Emulator)
  1. Resource Packager (used to build resource packages) requires Microsoft Windows 9x/2000/XP/Vista. Other operating systems are not supported at this time. (If you use an Intel-powered Mac, you may use Parallels or Boot Camp to run Windows.)
  2. Implies support for Pocket PC 2000, Pocket PC 2002, Windows Mobile 2003, and Windows Mobile 5.0 – and all Smartphone variations.