Developing for Windo 7 (and Windo 8)

Not a developer? No need to worry, some of this information can be useful to normal users too.

APP TYPES: Windo ⅞ apps come in a few formats. We will list what it is, how it works, and examples.

IF (interface-fused)

IF applications run in the main interface (/session.html). Features and capabilities for those types of apps are limited as implementing scripts, styles, or document contents can break Windo ⅞. On the other hand, IF applications work very closely and directly with Windo ⅞, allowing applications to change how Windo ⅞ works. Examples:

CEF (Common Embed Format)

CEF applications run in iframes which attach to the window content div written in session. These applications give developers a lot of free room to develop; store assets, scripts, stylesheets, etc. in their own directory: (/files/apps/developer-name/app-name/).

CEF applications set a gentle barrier for session’s security, and a stronger one for app stability. CEF apps are not completely confined in their own environment as they can interact with session by calling Windo ⅞’s functions & more. For example, if we wanted our CEF app to open window 13 we simply have to execute:

parent.openWindow(13)

(call parent)                (parent function name)        (app number/function value)

magiconsole relies on using “parent” in order to run commands such as logout.

CEF applications are ideal for games and anything else that doesn’t work too closely with Windo ⅞.

ELA (externally launched apps)

ELAs do not require you to be very literate. ELAs don’t work in the Windo ⅞ environment. ELAs open as web pop ups, tabs (varying on version), and are launched from menu items in session. ELAs can be hosted on the web or locally in /files/apps/developer-name/app/

IF & CEF

There is a proposed possibility where as a developer you can mix IF and CEF applications together if you wish. As of the time this was written, there are no applications which demonstrate IF & CEF.

THIS IS THE END OF THE APP TYPES SECTION