Give user the option to reload the config viewlet

Give user the option to reload the config viewlet

After a charm has been changed on a service, the config may or may not have different/more/fewer options, but those changes may have occurred out of view (same as sticky-headers problem), so give the users the option to reload the config viewlet.  This also cancels the notification.

As before, to QA, create a service, then run `app.db.services.item(0).set('charmChanged', true)` in the JS console.

https://code.launchpad.net/~makyo/juju-gui/upgrade-reload-inspector/+merge/187883

(do not edit description out of merge proposal)

[matthew.scott, 2013-09-26 19:29:38]

Please take a look.

[jeff.pihach, 2013-09-26 19:39:04]

Thanks for getting this done! Please see my questions below.

https://codereview.appspot.com/13986043/diff/1/app/templates/inspector-header...
File app/templates/inspector-header.handlebars (right):

https://codereview.appspot.com/13986043/diff/1/app/templates/inspector-header...
app/templates/inspector-header.handlebars:26: {{displayName}} has just been
upgraded to <span data-bind="charm"></span>. Configuration options may have
changed; <a class="rerender-config">reload</a> the inspector to view any
changes.
When they hit this button I'm sure they would expect the warning message to also
go away.

https://codereview.appspot.com/13986043/diff/1/app/views/inspector.js
File app/views/inspector.js (right):

https://codereview.appspot.com/13986043/diff/1/app/views/inspector.js#newcode929
app/views/inspector.js:929: this.model.set('charmChanged', false);
What happens if mr/mrs user just closes and opens the inspector again? Will this
be true? Maybe we should think of a different appraoch to set it to false.

[jeff.pihach, 2013-09-26 20:19:23]

QA NO GO
See comment below for resolution.

https://codereview.appspot.com/13986043/diff/1/app/views/inspector.js
File app/views/inspector.js (right):

https://codereview.appspot.com/13986043/diff/1/app/views/inspector.js#newcode931
app/views/inspector.js:931: viewlet.render(this.model, viewlet.options);
This viewlet's render method creates a new container every time it's called -
you will need to check for an existing container in the DOM first.

[matthew.scott, 2013-09-27 20:37:27]

Please take a look.

[matthew.scott, 2013-09-30 16:10:38]

Please take a look.

[jeff.pihach, 2013-09-30 16:33:57]

LGTM Thanks again for all the iterations on this!
QA OK

[matthew.scott, 2013-09-30 16:54:06]

*** Submitted:

Give user the option to reload the config viewlet

After a charm has been changed on a service, the config may or may not have
different/more/fewer options, but those changes may have occurred out of view
(same as sticky-headers problem), so give the users the option to reload the
config viewlet.  This also cancels the notification.

As before, to QA, create a service, then run
`app.db.services.item(0).set('charmChanged', true)` in the JS console.

R=jeff.pihach
CC=
https://codereview.appspot.com/13986043

https://codereview.appspot.com/13986043/diff/12001/app/views/environment.js
File app/views/environment.js (right):

https://codereview.appspot.com/13986043/diff/12001/app/views/environment.js#n...
app/views/environment.js:195: '.rerender-config': {click: 'rerenderConfig'},
D'oh, I'll rename these to reloadInspector or something.