lightweight/right-tree
1
0
Fork 0
Code Issues 17 Pull requests Projects Releases Packages Wiki Activity Actions

Add forest section diagram to the results table #23

New issue
Closed
opened 2021-11-18 11:55:46 +13:00 by danalambert · 3 comments
danalambert commented 2021-11-18 11:55:46 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link
  1. How should the informational forest graphic be displayed in the output, this is not described in the spec? Could the user click/hover over the column containing the forest position to see the image (how would we make this obvious to the user though)?

(WW suggested answer:

We only show the "Forest Section" diagram for informational purposes. It need not be present in the output display at all.)
If it is straightforward, I would follow their suggestion of hovering over the column containing forest position to show that graphic. We have a new one which shows the epiphyte.

Add the forest section diagram to the results table as a tooltip when the user hovers over the column containing forest position.

> 2. How should the informational forest graphic be displayed in the output, this is not described in the spec? Could the user click/hover over the column containing the forest position to see the image (how would we make this obvious to the user though)? > > (WW suggested answer: > > We only show the "Forest Section" diagram for informational purposes. It need not be present in the output display at all.) > If it is straightforward, I would follow their suggestion of hovering over the column containing forest position to show that graphic. We have a new one which shows the epiphyte. Add the forest section diagram to the results table as a tooltip when the user hovers over the column containing forest position.
danalambert commented 2021-11-26 11:10:35 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

assigned to @danalambert

assigned to @danalambert
danalambert commented 2021-11-30 10:33:30 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

mentioned in merge request !28

mentioned in merge request !28
danalambert commented 2021-12-07 10:08:55 +13:00 (Migrated from gitlab.catalyst.net.nz)
Copy link

assigned to @alistairmcintyre and unassigned @danalambert

assigned to @alistairmcintyre and unassigned @danalambert
alistairmcintyre (Migrated from gitlab.catalyst.net.nz) closed this issue 2021-12-07 10:14:10 +13:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v1.0.1
No results found.
Labels
Clear labels   
Bug

A software bug we've noticed. (These may not necessarily be show-stoppers)

  
Client: Biosphere Capital

   
Client: Central Hawkes Bay District Council

   
Client: Forward Works Viewer

   
Client: Kea/Kākā Databases

   
Client: Otorohanga District Council

   
Stage: Blocked

Something is causing us to be unable to currently fix this issue.

  
Stage: Doing

An issue that's assigned and being worked on

  
Stage: Peer review / Staging

An issue waiting to be given the all clear for production deployment.

  
Stage: Ready

For tickets that have been quanitifed, have acceptance criteria, and can be safely moved to the To Do column.

  
Stage: UAT AT

Work waiting to be deployed to production.

No labels
Bug
Client: Biosphere Capital
Client: Central Hawkes Bay District Council
Client: Forward Works Viewer
Client: Kea/Kākā Databases
Client: Otorohanga District Council
Stage: Blocked
Stage: Doing
Stage: Peer review / Staging
Stage: Ready
Stage: UAT AT
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lightweight/right-tree#23
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?