Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Firefly
-
Labels:
-
Story Points:1
-
Epic Link:
-
Sprint:SUIT Sprint 2018-08, SUIT Sprint 2018-09
-
Team:Science User Interface
Description
Two suggestions (only!) for the footprint menu in Firefly:
- Make it hierarchical, so that, e.g., all the HST instrument footprints appear in a submenu. (I would like to have at least three footprints for LSST, for instance.)
- Make its content part of the application configuration, e.g., controlled via the suit package for LSST or the ife package for IRSA. The Firefly repo could still contain a standard set of footprint files, but more could be added in the application, and even some of the standard ones suppressed, perhaps?
Attachments
Issue Links
- is blocked by
-
- Done
Activity
DM-15828 will address the second part of this ticket.
At the Firefly CCB meeting today, it was noted that this ticket is addressed by code already merged and deployed on irsadev.
I've had a look. It definitely addresses the hierarchical submenus, and I like the result!
Looking at the code, I'm a bit concerned about the special-casing of Spitzer in the code in visualize/ui/MarkerDropDownView.jsx that injects the "All" entry into submenus. We'll have other missions/facilities that don't have an "All" entry; it's how I plan to lay out the LSST submenu, for instance.
It should be part of the per-mission application-level configuration to state whether an "All" is provided or not.
With this point in mind, and without any comment on this matter in the ticket, I'm unclear about whether Part 2 of the Description above has been implemented. If not, it should be split off as a separate ticket. I feel that making the footprint menu application-configurable is going to be pretty important for LSST and, I'd guess, perhaps for SOFIA.