lp:~makyo/juju-gui/endpoints-once

Branch merges

Propose for merging

No branches dependent on this one.

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

Juju GUI Hackers: Pending requested 2012-11-30

Diff: 114 lines (+59/-7)

2 files modified

app/app.js (+29/-5)
test/test_app.js (+30/-2)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #1084790: get_endpoints called too frequently

High

Fix Released

Link a bug report

Related blueprints

264. By Madison Scott-Clary on 2012-12-03

Clean up usage of get_endpoints in app so that it's only called when needed.

263. By Madison Scott-Clary on 2012-12-03

Clean up usage of get_endpoints in app so that it's only called when needed.

262. By Madison Scott-Clary on 2012-11-30

Clean up usage of get_endpoints in app so that it's only called when needed.

261. By Benjamin Saller on 2012-11-29

D3 Components Documentation

This make an effort to provide a high level modules writer guide. As a
concession it refers the reader to portions of the YUI event and D3 data
binding docs.

R=teknico, benjamin.saller, gary.poster
CC=
https://codereview.appspot.com/6858085

260. By Madison Scott-Clary on 2012-11-28

Ignore editor files.

Watch functions will throw noisy errors on files not part of the distribution, making debugging watched files (templates, LESS stylesheet) difficult in `make debug`; an ifValidFile function was created to ignore these and slim down useless errors. Quick slack task.

R=benji, gary.poster
CC=
https://codereview.appspot.com/6842104

259. By Madison Scott-Clary on 2012-11-27

Charm panel border improvements

From Matt C.: Shadow should be darker on darker areas in the panel (such as the charm name and search result headings), and the border should extend all the way down to the bottom of the view (was 1px short).

Per UX review, colors updated and inset box-shadow on bottom.

R=
CC=
https://codereview.appspot.com/6855049

258. By Francesco Banconi on 2012-11-27

Tests mutating URL and not removing test nodes.

One of the hotkeys tests mutated the URL.
Both tests in that test case also failed when run
in isolation, and some variables were unused.

Also fixed tests leaving elements in the DOM:
as a consequence, "Environmenton excellent provider"
was visible at the top of the page after a test run.
Now the container used by those tests is removed
after each test is run. Also removed an XXX saying
that removing the elements in afterEach can be
problematic. I've tried to reproduce the erroneus
behavior described, running the test suite several
times, without success. Anyway, removing in afterEach
what was created in beforeEach is something we do
everywhere in the tests. So, that XXX confused me
a bit, any hint?

To avoid flickering in the test page, I tried to
hide the nodes used by tests where possible.

R=
CC=
https://codereview.appspot.com/6856075

257. By Nicola Larosa on 2012-11-26

Compute documentation statistics.

Count the total number of YUIDoc documentation lines by
enhancing the output of the "bin/lint-yuidoc" command.

R=benji, gary.poster
CC=
https://codereview.appspot.com/6845085

256. By Benji York on 2012-11-23

Remove "requires" properties.

The minification process does not read the "requires" parameters defined in
"all-app-debug.js". This parameter should be defined in each custom yui object
that uses some kind of internal or external requirement. The sole use of
"all-app-debug.js" is to define the fullpath of the file that defines a given
module.

This patch removes all the existing "requires" properties from
"all-app-debug.js" and add then where they are needed.

R=
CC=
https://codereview.appspot.com/6845084

255. By Madison Scott-Clary on 2012-11-21

Fix initial creation of subordinates.

When creating a subordinate service initially, it was not being laid out properly by the pack layout, nor was it seeming to have drag events attached. Pack layout was expecting a value accessor function to return some number greater than zero when constructing its radius, which informs the x/y coordinates. Returning zero results in NaN for all three values, thus positioning the service at (0,0) and causing drag events to fail when updating the service's coordinates with dx/dy + NaN. This branch fixes this by ensuring that zero is never returned as the node's value. This fix is quick and intended to make the UI function with the current layout algorithm. Future layout algorithms, if they're designed by hand, will need to keep this in mind as well.

R=benjamin.saller, bac
CC=
https://codereview.appspot.com/6856067