chrome app make it legacy app -



chrome app make it legacy app -

how create app legacy app, can utilize options_page alternative in it?

i have angular app, , made run in chrome app, , works, need have options page, can setup variables.

{ "name": "app", "description": "descrription", "version": "0.5", "icons": { "16": "assets/images/icons/16x16.png", "48": "assets/images/icons/48x48.png", "128": "assets/images/icons/128x128.png" }, "manifest_version": 2, "app": { "background": { "scripts": ["background.js"] } }, "permissions": [ "storage", "http://*/" ] }

i warning can't utilize options in packaged app..

first off, strongly should not. legacy apps called reason: no longer supported. not able publish such app, , stop working altogether @ later date.

however, approach kind of wrong. chrome app supposed self-contained, options merged interface. shouldn't have options link buried somewhere in chrome, should display options interface in app's ui.

google-chrome google-chrome-app

Comments

Popular posts from this blog

Delphi change the assembly code of a running process -

json - Hibernate and Jackson (java.lang.IllegalStateException: Cannot call sendError() after the response has been committed) -

C++ 11 "class" keyword -