Task #6574 (closed)
Opened 8 years ago
Closed 7 years ago
Configurable way to add buttons to menus
| Reported by: | jamoore | Owned by: | atarkowska |
|---|---|---|---|
| Priority: | minor | Milestone: | OMERO-4.4.7 |
| Component: | Web | Version: | n.a. |
| Keywords: | n.a. | Cc: | bhcho@…, murphy@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by jmoore)
Primary use case was permitting OMERO.searcher to be implemented without patching (i.e. forking) the main code base. This holds for the rest of #6572 as well.
Change History (1)
comment:1 Changed 7 years ago by jmoore
- Cc bhcho@… murphy@… added
- Description modified (diff)
- Milestone changed from Unscheduled to OMERO-4.5
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Ivan, the following was put into place in 4.4 to make button/menus extensible. Let us know if this (along with the docs) are not enough to get OMERO.searcher ported to 4.4
In webclient we have 2:32 will/jabber # Add links to the top header: links are ['Link Text', 'link'], where the url is reverse("link") OR simply 'link' (for external urls) "omero.web.ui.top_links": ["TOP_LINKS", '[]', json.loads], # E.g. '[["Webtest", "webtest_index"]]' 2:32 will/jabber in settings.py