Redesign summary view

[edan-bainglass]

This PR is one in several that will address #1042

Here, I introduce a bullet list alternative format for the summary report (no actual bullets). The format is defined in qeapp.yml as summary_format: list and can be overridden by the user in a config file (see #1007 for info regarding file). summary_format takes list or table.

I also adjust the style such that the data download widget is to the right of the summary instead of below. This is true for either selected format.

Lastly, I add "Workflow properties" and "Structure properties" sections to the summary.

---

[edan-bainglass]

If anyone has an older container (with an older AiiDA version, say, 2.5ish), can you please verify that you still get the notification regarding the unavailability of the raw data download feature?

[codecov]

Codecov Report

Attention: Patch coverage is 68.31683% with 32 lines in your changes missing coverage. Please review.

Project coverage is 67.58%. Comparing base (68cdb8d) to head (c6e1725).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
..._qe/app/result/components/summary/download_data.py	16.66%	20 Missing ⚠️
src/aiidalab_qe/common/time.py	72.22%	5 Missing ⚠️
...idalab_qe/app/result/components/summary/summary.py	84.00%	4 Missing ⚠️
...aiidalab_qe/app/result/components/summary/model.py	90.90%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1044      +/-   ##
==========================================
- Coverage   67.65%   67.58%   -0.07%     
==========================================
  Files         117      118       +1     
  Lines        6498     6543      +45     
==========================================
+ Hits         4396     4422      +26     
- Misses       2102     2121      +19     

Flag	Coverage Δ
python-3.11	67.58% <68.31%> (-0.07%)	⬇️
python-3.9	67.60% <68.31%> (-0.07%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[AndresOrtegaGuerrero]

why dont you try with from IPython.core.display import HTML and create the tables , like that you have more flexibility in the appearance.

Also since the tab of picking the settings was Basic settings, you should keep the same instead of using Main settings

[edan-bainglass]

why dont you try with from IPython.core.display import HTML and create the tables , like that you have more flexibility in the appearance.

No idea what you're referring to 😅

Also since the tab of picking the settings was Basic settings, you should keep the same instead of using Main settings

This was a specific request by Giovanni. See issue.

[AndresOrtegaGuerrero]

why dont you try with from IPython.core.display import HTML and create the tables , like that you have more flexibility in the appearance.

No idea what you're referring to 😅

You can make an HTML object and create a table and to display it , it has better visuals than the ipywidget.HTML.
The table gave this kind of separation that was nice , plus a highlight , but indeed they were to big the cell size.
My opinion of the visuals is that is a lil too simple , plus everything looks to close to each other.

Also since the tab of picking the settings was Basic settings, you should keep the same instead of using Main settings

This was a specific request by Giovanni. See issue.

Ok , then we should keep it consistent in the configuration step , and name it main settings as well (instead of basic)

[AndresOrtegaGuerrero]

@edan-bainglass I can confirm you that the notification for aiida 2.5 works

[edan-bainglass]

Thanks @AndresOrtegaGuerrero 🙏

[edan-bainglass]

@giovannipizzi @cpignedoli alternative...

Both list and table are now valid choices for a new summary_format configuration key, which thanks to #1007, is now user-configurable via a local config file. Currently defaulting to list, though the table view is quite clean in my opinion (suggested by @AndresOrtegaGuerrero).

Also, "Main settings" is inconsistent with "Basic settings". Best we uniform this. Do you agree, and if so, preference?

[giovannipizzi]

Thanks! Both are good, table is OK as the dark color is not too dark/prominent. But as the list might get longer, maybe the list is OK. I agree with uniforming basic/main,maybe "main" is better but both are are ok.

[edan-bainglass]

Thanks! Both are good, table is OK as the dark color is not too dark/prominent. But as the list might get longer, maybe the list is OK. I agree with uniforming basic/main,maybe "main" is better but both are are ok.

Okay then. Leaving list as the default. Will also reduce the vertical padding in the table a bit more. And I think I'll stick to "basic". Thanks!

---

For reference

[edan-bainglass]

Adding more info requested in #1042

and

[edan-bainglass]

@AndresOrtegaGuerrero could you please review once more? 🙏

[AndresOrtegaGuerrero]

@edan-bainglass Thank you! In my test everything works. I did notice an issue I mentioned in #1045, where we sometimes fail to indicate whether the full workflow completed successfully. However, I’m thinking this might not be the right place to address it—what do you think?

[AndresOrtegaGuerrero]

Just dont forget to solve the conflict

[AndresOrtegaGuerrero]

LGTM! Thank you @edan-bainglass

[AndresOrtegaGuerrero]

@edan-bainglass It just crossed my mind now, should we report the properties computed ?

[edan-bainglass]

@edan-bainglass Thank you! In my test everything works. I did notice an issue I mentioned in #1045, where we sometimes fail to indicate whether the full workflow completed successfully. However, I’m thinking this might not be the right place to address it—what do you think?

Indeed, unrelated. Thanks for opening the issue.

[edan-bainglass]

@edan-bainglass It just crossed my mind now, should we report the properties computed ?

I suppose so? Doesn't hurt. I'll add it 👍

[edan-bainglass]

@edan-bainglass It just crossed my mind now, should we report the properties computed ?

I suppose so? Doesn't hurt. I'll add it 👍

@AndresOrtegaGuerrero not sure where and how to best represent the computed properties. For now, I'll merge without it. Let's discuss and PR this later.