Service Workers: Difference between revisions

From Joomla! Documentation

No edit summary
Line 18: Line 18:
<ref>https://www.w3.org/TR/appmanifest/</ref>
<ref>https://www.w3.org/TR/appmanifest/</ref>


# 1.
1.system/manifest: $document->addCustomTag('<link rel="manifest" href="' . $base . '/index.php?option=com_ajax&plugin=joocialWebpushManifest&format=raw">');
system/manifest: $document->addCustomTag('<link rel="manifest" href="' . $base . '/index.php?option=com_ajax&plugin=joocialWebpushManifest&format=raw">');


#2. ajax/manifest: Generator class
2. ajax/manifest: Generator class
2.1 template - params
 
2.2 wam/ component listener plugin
  2.1 template - params
2.3 json output
 
  2.2 wam/ component listener plugin
 
  2.3 json output
#3. Service Worker Geneation: event hub
3. Service Worker Geneation: event hub
3.1: wam/ listener plugin: JDocument->addServiceWorker
 
3.2: JS Hub initilization
  3.1: wam/ listener plugin: JDocument->addServiceWorker
 
3.2: JS Hub initilization

Revision as of 17:41, 18 November 2017

Service Worker Specification

This is a discussion document to work out the best practice to implement Progressive Web App manifest files and the implementation of service workers.

The idea is to support the manifest and service worker generation dynamically. The scope it to support the following features:-

Offline Navigation Advanced Cache Splash screen Lazy (Background) Loading Web Push Notifications Theming Home Screen Management

Web App Manifest

[1]

1.system/manifest: $document->addCustomTag('<link rel="manifest" href="' . $base . '/index.php?option=com_ajax&plugin=joocialWebpushManifest&format=raw">');

2. ajax/manifest: Generator class

 2.1 template - params
 2.2 wam/ component listener plugin
 2.3 json output

3. Service Worker Geneation: event hub

 3.1: wam/ listener plugin: JDocument->addServiceWorker

3.2: JS Hub initilization