Pokki overview

Overview

Interface

has four interface elements that users may interact with;

Icon an icon located in the Pokki area of the usr's taskbar.

clicking on this icon opens and closes your app.

App window a window which is displaed when the user

clicks on your app's icon.this is the primary interaction point for your application.

you define both the size and the content of the window

Badge  a small badge displayed over the  top-rightdispl

corner of your app's icon ,,Inside the badge is a number which you may set and

clear through a JS API

Context menu    displayed when a user right-clicks

on your app's icon, Using our JS API you can dynamically add context items and liten for a callback

Architecture

Each Pokki app is a collection of files stored in a single directory;

Manifest file (manifest.json) that contains metadata about your app

HTML window page file

(Optional) HTML background page file

Any files include by the HTML pages (images, js,css)

19  29 42  256  versions of the app's icon in PNG format

Any directoy structures used to hold the files

core components of app app are the two web pages

window page  an HTML file used to define the app window contents

contents and handle user interaction

Background page,  an optional HTML file which is always runing without an interface,

used to determine when an app's badge should be updated.

while each page runs independently and does not share DOM or javascript contexts

they may communicate with each other using a remote procedure call method in the Pokki API or

share data using their unified local sotrage . this allows for a reduction in duplicated data trnsfer and procesing betwwen pages.

Sandboxed

All pokki apps run in a sandboed architecture

is built on the notion of very limited privilege processes.

Can't access files or data on the user's computer

Can't access antoher app's local storage

is isolated , so if it crashes it does not affect Pokki or Windows

Packaging and Delivery System

We have built a centralized  and secure delivery system for Pokki apps

Whenever you publish your app it is reviwed by the pokki before it can be distr

distributed . Upon approval your app's package and signed on the server,

scrambling any sensitie data you defined in your manifest and

can now be distribued and installed by a user.

When a user initiates the intall of a Pokki app, Pokki commnicates whit the okki server using HTTPS and SHA-Q to ensure

whicl app to install

The loction of the app package to download

Post download verification of th e package

verification of the app once it's unpacked and ready to be install

Auto Upadte

Pokki automatically checks for updates of the engine and its installed apps at startup and every

subsequednt 24 hours , If a new version iof either is found

Technology

Pokki is built on the following technologies

Chromim for app sandboxing

WebKit for layout and rendering

V8 for JS engine

var ua = window.navigator.userAgent;

standard JS APIS

HTML5 and other emerging APIS

Audio element

Video element

Canvas

WebGL

Full-screen

Web Storage

Web SQL Database

Web Workers

Web Scokets

 

Webkit

Web App Compatiblity

While a Pokki app is very similar to a traditional web app,

it's not running gin a tradional browser,  We have done a lot to make this utterly seamless for your existing web app  but its important to understand these differences

 

Not Really a browser

and as such Pokki catches window.location changes andwindow.open

calls and fires an event that you can listen for in your app.

Cross-origin XHR works

Web Sheets for Secure Login

exposes Web sheet   are embedded browsers that are solely intended to facilicate secure login

implications form the file protocol

the window and background pages cannot read or write cookies and as such we recommend using local storage for client storage

that asid if you load an ifram or web sheet .. cookies work as expected and are

file:///somedomain.com/asset.js

Disabled APIs

window.alert()

window.confirm()

window.prompt()

你可能感兴趣的:(view)