lp:~bcsaller/juju-gui/viewlets-behaviors

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

900. By Benjamin Saller on 2013-07-26

pull out optional callback handler

899. By Benjamin Saller on 2013-07-26

ugh, merge wildcards from trunk, how did that fail before

898. By Benjamin Saller on 2013-07-26

stub behavior support, single flag in viewlet config, tracking in databinding (viewlets w/o containers) and in manager where they don't render/show

897. By Benjamin Saller on 2013-07-26

factor out config and ghost, minimal verification

896. By Benjamin Saller on 2013-07-26

merge trunk

895. By Benjamin Saller on 2013-07-26

factor out config module

894. By Benjamin Saller on 2013-07-26

wip, extract overview to module

893. By Gary Poster on 2013-07-25

Fix subordinate behavior in Juju Core

The biggest change here is that we update service data with the charm subordinate flag, because juju core does not include that information in the service. This includes a test.

Other changes here are fly-by.
- The yui3-skin-sam class on the body was causing issues by adding styles unnecessarily. I put it on the subapp-browser, where it is sufficient.
- The sandbox sends is_subordinate, not subordinate, for charms. I'm not sure if that is correct, but for now I changed charm.js to handle it. I'd welcome opinions on pushing this back down into the pyjuju sandbox, where I could test it. I'm kind of inclined to do that, actually, but I want to get this branch proposed.
- I made a few changes to the inspector code to handle subordinates a bit better, particularly in the ghost inspector. the ghost inspector has no tests at all, and we have a card for adding them, so I did not try to tack that effort on to this branch.
- I made a small tweak to charm-panel.js so that new services start looking like subordinates immediately.
- I added a small hack that came in handy to track down behavior in a handlebars template. Just add {{debugger}} in the template and you will have a breakpoint there. handy. hopefully not too dangerous! We definitely don't want to check in a template that uses this, and the linter won't check our template code...

R=benji
CC=
https://codereview.appspot.com/11804043

892. By j.c.sackett on 2013-07-25

Updates charm view to use Charm model.

To make it easier to clean up and phase out the old API, the charm views (which
have previously worked on parsed JSON) are updated to use the Charm model and
the old API. This makes it much easier to translate to the new API, and further
down the road, the BrowserCharm model.
-Charm view uses Charm model and loadByPath
-CharmCollection view, which appears to be unused now that the old search is
gone, is deleted.

R=matthew.scott, jeff.pihach
CC=
https://codereview.appspot.com/11831043

891. By Jeff Pihach on 2013-07-24

Fixed inspector unit list sorting bug

In order to fix the sorting bug with our current D3 version
we need to render all unit lists at once and then hide/show
when units are in those lists.

This also includes a driveby fix for https image and having
the unit lists closed by default

R=matthew.scott, gary.poster
CC=
https://codereview.appspot.com/11351046