Task #7068 (closed)
Opened 13 years ago
Closed 12 years ago
Strategies for Django template use-cases
| Reported by: | wmoore | Owned by: | wmoore |
|---|---|---|---|
| Priority: | major | Milestone: | OMERO-4.4 |
| Component: | Web | Version: | n.a. |
| Keywords: | n.a. | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | 2011-11-10 (2) |
Description (last modified by wmoore)
What strategies to use to allow extension and reuse of templates and javascript.
- Provide several starting templates at different levels in hierarchy.
- Use includes for:
- html blocks
- css links
- javascript links
- Put {% block %} within javascript docs to overwrite methods? E.g. handle tree selection
- Specify id on more elements, so they can be hidden using js. E.g. simplifying Image-viewer by hiding stuff.
- Allow templates to be specified for more Django views.py methods (see Image-viewer).
- {% block toolbar %} to allow additional toolbar buttons.
Change History (4)
comment:1 Changed 13 years ago by wmoore
- Description modified (diff)
comment:2 Changed 13 years ago by jburel
- Sprint changed from 2011-10-27 (1) to 2011-11-10 (2)
comment:3 Changed 12 years ago by wmoore
- Description modified (diff)
comment:4 Changed 12 years ago by wmoore
- Resolution set to fixed
- Status changed from new to closed
Seems we have enough to be getting on with! This will serve as a reference for ideas etc, but additional strategies may be used as and when needed.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Moved from sprint 2011-10-27 (1)