The licensed use of Zeepe lets a web page author/developer define the attributes of a window - its size, position, state, shape and any alpha-blend to the desktop - on the page, so that when that page's content is delivered to a Windows client PC on which the free (1.25Mb) Zeepe runtime is installed, it will appear not in the browser but in that defined window.
And that will happen locally, or when that content is delivered over the web or across an intranet.
Naturally there's a great deal more - unfettered access to resources on the local machine, cross-domain working, 2-way comms & control across multiple windows (discrete, or as part of an integrated UI), absolute control over printing et al - and that's all described on the Zeepe site and in the SDK.
(For a speed feel, take a quick trip through the history of "What's New" version-on-version. It's really, really impressive :-)
But them's the bones, and THAT is why Zeepe is so important in this era of fast-growing 'in-browser' functionality. It's the final small - but highly mature - piece of the jigsaw that will quickly turn any browser-hosted web application into a first-class citizen on the Windows desktop.
Jerry Mead ~ CEO, MeadCo
Update: Just as a follow-up - and to give everyone a better initial feel for Zeepe - I fired up a few different Zeepe-based apps on my desktop and snapped it.
The basics to take away from this image are that
(a) all of these apps have been opened on my desktop directly from one or other of our sites across the Net
(b) each is authored as a single DHTML document.
Yet if they all come across like 'real' Windows apps, it's because that's exactly how they look, feel and behave.
BTW there's nothing shown in this pic that isn't 100% built on the page using DHTML + Zeepe, and that includes all menubars, toolbars, rebars & the like (albeit that these scriptable controls aren't DHTML, they are *local* to the OS).