Service position should be maintained across usages
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-gui |
Fix Released
|
High
|
Benjamin Saller | ||
Bug Description
Intended to be after bug 1083807: The service positions in the environment view should be maintained across usages.
This bug is intended to represent a minimum implementation of the feature. Simply store annotations for service positions in Juju. The most recent annotation to Juju wins. When you start a new GUI, the old positions are loaded and immediately used.
See bug 1096230, bug 1096270 and bug 1096273.
multiple simultaneous connections are not part of this bug except to keep things minimally sane. Notably:
- While you are dragging a service, position updates from other viewers do not affect you (and when you release a service, you become the most recent annotation).
- When a client receives a new position for the service over the wire, it moves there immediately. "Gliding" to position is a nice to have and should be implemented separately if at all, at this stage.
Related branches
- Juju GUI Hackers: Pending requested
-
Diff: 1142 lines (+498/-315) (has conflicts)9 files modifiedapp/app.js (+6/-1)
app/models/models.js (+0/-1)
app/store/notifications.js (+12/-13)
app/views/environment.js (+21/-0)
app/views/topology/service.js (+249/-146)
test/test_environment_view.js (+44/-5)
test/test_service_module.js (+2/-2)
test/test_topology.js (+14/-2)
undocumented (+150/-145)
| description: | updated |
| summary: |
- Service position should be shared across all viewers of a Juju - environment + Service position should be maintained across usages |
| Changed in juju-gui: | |
| assignee: | nobody → Benjamin Saller (bcsaller) |
| milestone: | none → 0.1.4+build.311 |
| status: | Triaged → In Progress |
| Changed in juju-gui: | |
| status: | In Progress → Fix Released |
