Invalid backend content for the bindings
Bug #1288801 reported by
Alexandre Abreu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unity-webapps-qml |
Fix Released
|
Medium
|
Alexandre Abreu | ||
| unity-webapps-qml (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
The backend qml/js file contents for the bindings is invalid and outdated.
Related branches
lp:~abreu-alexandre/unity-webapps-qml/fix-1288801
- Alberto Mardegan (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- David Barth (community): Approve
-
Diff: 3792 lines (+1593/-1837)16 files modifiedexamples/api-bindings/alarm/main.qml.in (+1/-0)
examples/api-bindings/content-hub-exporter/main.qml.in (+1/-0)
examples/api-bindings/content-hub/main.qml.in (+1/-0)
examples/api-bindings/content-peer-picker/main.qml.in (+2/-1)
examples/api-bindings/content-peer-picker/www/js/app.js (+17/-16)
examples/api-bindings/online-accounts/main.qml.in (+1/-0)
examples/api-bindings/online-accounts/www/index.html (+5/-0)
examples/api-bindings/online-accounts/www/js/app.js (+11/-0)
src/Ubuntu/UnityWebApps/UnityWebApps.js (+1/-1)
src/Ubuntu/UnityWebApps/UnityWebApps.pro (+13/-2)
src/Ubuntu/UnityWebApps/UnityWebApps.qml (+13/-6)
src/Ubuntu/UnityWebApps/UnityWebAppsBackendComponents.js (+0/-1668)
src/Ubuntu/UnityWebApps/bindings/alarm-api/backend/alarm-api.js (+246/-0)
src/Ubuntu/UnityWebApps/bindings/content-hub/backend/content-hub.js (+568/-33)
src/Ubuntu/UnityWebApps/bindings/online-accounts/backend/online-accounts.js (+684/-109)
src/Ubuntu/UnityWebApps/bindings/online-accounts/client/online-accounts.js (+29/-1)
| Changed in unity-webapps-qml: | |
| assignee: | nobody → Alexandre Abreu (abreu-alexandre) |
| status: | New → In Progress |
| importance: | Undecided → Critical |
| Changed in unity-webapps-qml: | |
| importance: | Critical → High |
| importance: | High → Medium |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in unity-webapps-qml (Ubuntu): | |
| status: | New → Fix Released |
| Changed in unity-webapps-qml: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
This bug was fixed in the package unity-webapps-qml - 0.1+14.
---------------
unity-webapps-qml (0.1+14.
[ 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:/
alexandre/
structure/
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://
"includes": [] } will do, or to avoid any confusion w/ the click
manifest.json file, one also searches for a webapp-
w/ the same content as above.
-- Ubuntu daily release <email address hidden> Wed, 14 May 2014 22:31:22 +0000