lp://staging/ubuntu/utopic-proposed/unity-webapps-qml
- Get this branch:
- bzr branch lp://staging/ubuntu/utopic-proposed/unity-webapps-qml
Branch merges
Related bugs
Related blueprints
Branch information
Recent revisions
- 43. By PS Jenkins bot
-
[ Alexandre Abreu ]
* Fix content hub getpeers() (LP: #1398916)
* Dont expect the content hub to be installed in a desktop
environment. (LP: #1395524) - 42. By Michael Vogt
-
* debian/control:
- update libqt5webkit5-qmlwebkitplugin -> qml-module-qtwebkit
(fixes a multiarch install failure) - 40. By PS Jenkins bot
-
[ Ubuntu daily release ]
* New rebuild forced[ Alexandre Abreu ]
* Simplify the click webapp definition for things like overrides etc. - 38. By PS Jenkins bot
-
[ Alexandre Abreu ]
Fix issue with qmlplugindump using 100% cpu Fix and expanded AP
tests to properly test the installed webapps case (LP: #1300957) - 36. By PS Jenkins bot
-
[ Ubuntu daily release ]
* New rebuild forced[ Olivier Tilloy ]
* Do not override existing message handlers. Oxide has this nice
feature that it automatically attaches the instantiated message
handler to the webview anyway, so this line was useless. (LP:
#1323735) - 35. By PS Jenkins bot
-
[ Ubuntu daily release ]
* New rebuild forced[ Alexandre Abreu ]
* Bindings for the download manager (LP: #1295842) - 34. By PS Jenkins bot
-
[ 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.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://staging/ubuntu/utopic/unity-webapps-qml