User Story #10270 (new)
Opened 11 years ago
Last modified 9 years ago
Web Image Viewer refactor — at Initial Version
| Reported by: | wmoore | Owned by: | wmoore |
|---|---|---|---|
| Priority: | major | Milestone: | 5.x |
| Component: | Web | Keywords: | n.a. |
| Cc: | cneves, cxallan | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Following discussion with Carlos on re-working image viewport to improve re-usability / configuration etc.
Some overall goals
- jQuery 'plugin-ify'. E.g. $("div").viewport("zoom", 1.0)
- Separate UI components from other code / logic:
- client state (rendering settings, Z, T etc)
- event handling / notifications
- Keep existing functionality as is (although a few improvements were also discussed)
We aim to have a core class that is simply initialised with a reference to the 'server' prefix (E.g. 'webgateway') and can then be initialised with an Image-Id, fetch Image json etc. This will have all the methods to edit this state, E.g. setChannelColor() etc. and notify listeners.
UI code will be moved into jQuery plugins that are initialised / bound to the core state class, update it and listen to changes as necessary.
These jQuery plugins could be viewportImage, rendering panel etc.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
