fakebackend/sandbox no op deployer watches

fakebackend/sandbox no op deployer watches

- The fakebackend and the sandbox need to just ignore calls to watch deployer
status. It's too fast and we don't want to flood the users with a bunch of
notices all at once.
- Had to rename the WatchUpdate to deployerNext since the fakebackend auto
builds the names of the handle methods based off the actual call. So it needed
to be deployerNext though I hate it's no longer worded to tie to 'watch'.

QA:

Simply deploy a bundle in sandbox mode.

- Drag/drop a yaml file into the canvas
- Deploy from the deploy button from bundle details

Note: Dragging/dropping a bundle token is not working. This is also true on
coming soon. This is due to the recent bundle.id tracking code and will be
done in a follow up.

https://code.launchpad.net/~rharding/juju-gui/bundle-sandbox-noop/+merge/196000

(do not edit description out of merge proposal)

[rharding, 2013-11-20 19:21:45]

Please take a look.

[bac, 2013-11-20 19:33:20]

LGTM with some crazy nit-picking mess.

https://codereview.appspot.com/29860044/diff/20001/app/store/env/fakebackend.js
File app/store/env/fakebackend.js (right):

https://codereview.appspot.com/29860044/diff/20001/app/store/env/fakebackend....
app/store/env/fakebackend.js:1592: This method is a noop in the fakebackend.
We've already sent the user a
noon looks too much like noob.

Pick one of 'no op' or 'no-op' throughout.

https://codereview.appspot.com/29860044/diff/20001/test/test_fakebackend.js
File test/test_fakebackend.js (right):

https://codereview.appspot.com/29860044/diff/20001/test/test_fakebackend.js#n...
test/test_fakebackend.js:740: // This is no op'd in the fakebackend since it
doens't make sense to
typo: doesn't

https://codereview.appspot.com/29860044/diff/20001/test/test_fakebackend.js#n...
test/test_fakebackend.js:741: // provide a watch status as things happen near
instantly.
grammar-o: nearly

https://codereview.appspot.com/29860044/diff/20001/test/test_fakebackend.js#n...
test/test_fakebackend.js:744: assert.fail('The watcher callback shoould never be
called.');
shoooooooould

https://codereview.appspot.com/29860044/diff/20001/test/test_fakebackend.js#n...
test/test_fakebackend.js:751: // This is no op'd in the fakebackend since it
doens't make sense to
Dang, on a roll!

https://codereview.appspot.com/29860044/diff/20001/test/test_fakebackend.js#n...
test/test_fakebackend.js:752: // provide a watch status as things happen near
instantly.
ditto

https://codereview.appspot.com/29860044/diff/20001/test/test_fakebackend.js#n...
test/test_fakebackend.js:755: assert.fail('The watcher update callback shoould
never be called.');
and again

[rharding, 2013-11-20 19:33:38]

Please take a look.

[rharding, 2013-11-20 19:42:47]

*** Submitted:

fakebackend/sandbox no op deployer watches

- The fakebackend and the sandbox need to just ignore calls to watch deployer
status. It's too fast and we don't want to flood the users with a bunch of
notices all at once.
- Had to rename the WatchUpdate to deployerNext since the fakebackend auto
builds the names of the handle methods based off the actual call. So it needed
to be deployerNext though I hate it's no longer worded to tie to 'watch'.

QA:

Simply deploy a bundle in sandbox mode.

- Drag/drop a yaml file into the canvas
- Deploy from the deploy button from bundle details

Note: Dragging/dropping a bundle token is not working. This is also true on
coming soon. This is due to the recent bundle.id tracking code and will be
done in a follow up.

R=bac
CC=
https://codereview.appspot.com/29860044