Task #10352 (new)
Opened 12 years ago
Last modified 9 years ago
Viewport 'view' & 'model' separation
| Reported by: | wmoore | Owned by: | wmoore |
|---|---|---|---|
| Priority: | major | Milestone: | Unscheduled |
| Component: | Web | Version: | n.a. |
| Keywords: | n.a. | Cc: | web-team@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
As described by #10270, the current viewport UI code should be separated from the UI. This will enable (for example) multiple viewport UIs displaying the same data, or use of the server communication without any viewport (E.g. just rendering panel) etc.
Workflow outline:
- Duplicate the existing ome.viewport.js and ome.viewportImage.js so we have a reference of existing behaviour / code while we refactor.
- Create a test page that runs the 'old' viewport alongside the refactored 'new' viewport plugin. This will allow us to call all the same methods on both viewports and compare the UI as well as test that the models stay in sync (by comparing query strings generated from both)
- Create a new jQuery plugin that takes an instance of the viewport 'model' and builds a UI that keeps in sync with it.
Change History (1)
comment:1 Changed 9 years ago by jamoore
- Milestone changed from Future to Unscheduled
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
