lp:~rharding/juju-gui/new-controls

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:juju-gui/experimental at revision 792

Richard Harding: Approve on 2013-07-02

Diff: 672 lines (+365/-121)

12 files modified

app/index.html (+6/-4)
app/modules-debug.js (+4/-0)
app/subapps/browser/views/view.js (+43/-19)
app/templates/browser-search.handlebars (+0/-1)
app/widgets/charm-search.js (+3/-49)
app/widgets/viewmode-controls.js (+170/-0)
lib/views/browser/main.less (+0/-15)
lib/views/stylesheet.less (+20/-0)
test/index.html (+1/-0)
test/test_browser_app.js (+18/-5)
test/test_browser_search_widget.js (+1/-28)
test/test_viewmode_controls_widget.js (+99/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

793. By Richard Harding on 2013-07-03

remove block of css no longer needed

792. By Richard Harding on 2013-07-03

Update from trunk

791. By Richard Harding on 2013-07-02

More @event docs

790. By Richard Harding on 2013-07-02

update per review

789. By Richard Harding on 2013-07-02

lint

788. By Richard Harding on 2013-07-02

sync

787. By Richard Harding on 2013-07-02

Start of the work to split up the search and viewmode controls

786. By Richard Harding on 2013-07-02

Pull huws ui work

785. By Benji York on 2013-07-01

make drag and drop work with non-sandbox backends

R=matthew.scott
CC=
https://codereview.appspot.com/10834043

784. By Richard Harding on 2013-07-01

Update the downloads to be total vs recent.

- Update the json data files per the new api payload.
- IGNORE then updated .json files in the test suite.
- Update the model to include a new downloads attribute matching the api
response.
- Update the charm-token to display downlods vs the recent values.

QA Known Issues
----------------

Currently the new api is only available in staging.jujucharms.com. This means
that all download counts show as undefined when doing QA against the
production back end.

Since the browser is currently not visible to general users and the lack of
the attribute does not throw errors of any kind, it's considered safe to land
as the back end code is done and just needs to be deployed.

R=benji, curtis
CC=
https://codereview.appspot.com/10832043