BHoM / BHoM/Excel_UI

Enable way to view BHoM warnings/notifications about code confidence etc. in Excel UI

Open
#319 0 comments 0 reactions 0 assignees View on GitHub
severity:low type:feature type:question
Dominant language
C#
Stars
5
Forks
5
PR merge metrics
No merged PRs in 30d

Description

#### Description:

Following great implementation of both [prototype labels](https://github.com/BHoM/Grasshopper_Toolkit/pull/634) and [dataset confidence warnings](https://github.com/BHoM/Grasshopper_Toolkit/pull/644) in Grasshopper -

Will be good to plan a similar approach for Excel.

This is naturally trickier - as mechanisms for adding notes and decorations to individual cells in Excel are much more limited (and will potentially be much more obstructive in terms of UX) than components in GH.

Good to gather thoughts and ideas here about best approach - even for initial MVP to get going and at least flag to user.

My first thought is to go with adding a notification icon into the BHoM Ribbon. This could ideally just show a small bubble with a number stating "X warning/notices". The user can click to get a simple list summarising the warnings in their Excel sheet.

I don't know - something like this
![image](https://user-images.githubusercontent.com/15924573/139084553-9ca2b0bb-cfe8-4dc4-88ed-34794cea1716.png)

Thoughts on this?
Would agree UX will not in first instance be as slick as Grasshopper - but would hope is easier to implement and would be keen to get something going so users have visibility.

FYI @adecler @kayleighhoude @IsakNaslundBh - welcome your thoughts in this area as well as anybody else's

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the linked Grasshopper prototype labels and dataset confidence warnings, then compare their approach with the Excel UI constraints described here. Define an initial Excel MVP, such as a BHoM Ribbon notification count with a clickable warning summary, and document the UX and implementation scope before coding.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.