~ubuntu-branches/ubuntu/wily/unity-webapps-qml/wily-proposed

« back to all changes in this revision

Viewing changes to src/Ubuntu/UnityWebApps/UnityWebApps.pro

  • Committer: Package Import Robot
  • Author(s): Ubuntu daily release, Ubuntu daily release, Alexandre Abreu
  • Date: 2014-05-14 22:31:22 UTC
  • mfrom: (1.1.30)
  • Revision ID: package-import@ubuntu.com-20140514223122-ln3ei1hz5je1tkc6
Tags: 0.1+14.10.20140514.2-0ubuntu1
[ Ubuntu daily release ]
* New rebuild forced

[ Alexandre Abreu ]
* Cleanup the structure of the QML bindings to make it clearer. No
  Changes in functionality all features are still working & same, This
  is an updated version of: https://code.launchpad.net/~abreu-
  alexandre/unity-webapps-qml/restructure-cleanup-bindings-qml-
  structure/+merge/208148 with the latest changes that got in in
  between (LP: #1288801)
* Simplifies the manifest.json handling in some instances. More
  precisely when one is using a custom model search path for the
  webapp lookup, some restrictions are being put on what is expected
  to be found in the folder among which: a common/ subfolder (even if
  the webapp doesnt require one),. one or more unity-webapps-* folders
  with manifest.json & *.user.js files in it,. More over the manifest
  files do require user scripts to be defined. This imposes a set of
  constraints over a given webapp that simply wants to use the
  container (w/o js injection). This simplifies it an allows one to
  define a manifest.json file (still with some required elements, but
  a smaller set), directly in the model search path. E.g. something
  like: {     "name": "MyWebApp",     "homepage":
  "http://www.bbc.co.uk/news/",     "domain": "bbc.co.uk",
      "includes": [] } will do, or to avoid any confusion w/ the click
  manifest.json file, one also searches for a webapp-properties.json
  w/ the same content as above.

Show diffs side-by-side

added added

removed removed

Lines of Context:
56
56
js_files.path = $$installPath
57
57
js_files.files = $$PLUGIN_JS_FILES
58
58
 
 
59
content_hub_binding_backend_js_files.path = $$installPath/bindings/content-hub/backend/
 
60
content_hub_binding_backend_js_files.files = ./bindings/content-hub/backend/content-hub.js
 
61
 
 
62
alarm_binding_backend_js_files.path = $$installPath/bindings/alarm-api/backend/
 
63
alarm_binding_backend_js_files.files = ./bindings/alarm-api/backend/alarm-api.js
 
64
 
 
65
online_accounts_binding_backend_js_files.path = $$installPath/bindings/online-accounts/backend/
 
66
online_accounts_binding_backend_js_files.files = ./bindings/online-accounts/backend/online-accounts.js
 
67
 
59
68
runtime_api_binding_backend_js_files.path = $$installPath/bindings/runtime-api/backend/
60
69
runtime_api_binding_backend_js_files.files = ./bindings/runtime-api/backend/runtime-api.js
61
70
 
62
71
INSTALLS += qmldir_file \
63
72
    qml_files \
64
73
    js_files \
65
 
    runtime_api_binding_backend_js_files \
66
 
 
 
74
    content_hub_binding_backend_js_files \
 
75
    alarm_binding_backend_js_files \
 
76
    online_accounts_binding_backend_js_files \
 
77
    runtime_api_binding_backend_js_files
67
78