-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(UI): Display item updates as a dropdown #669
Conversation
0452660
to
96046ee
Compare
- project store as been updated to manage updates - updates are stored in session storage to limit memeory footprint - card quick action have been introduced to have one click delete and browse history - on click on an item update an event is emitted, the view listens to it and calls the store to update the list of `PresentableItem` reactivelly
96046ee
to
3c0a7a4
Compare
In the video, the "Updated about 17 hours ago" for a dozen histories of the item does not help the user track them? Maybe write the full log somewhere? |
Awesome stuff!! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found a small graphical bug:
2024-11-05T12_11_49_screen_record.mp4
To reproduce, open the menu, then quickly move the mouse away and then back
This is (to me ^^) not a bug. You did not close explicitly closed the drop down but moved your mouse outside of the actions which appears only on hovering. Hence actions dim out but there state persists. What behavior would you expect ? |
Indeed it does'nt help but it's only due to my test dataset in which all updates have been generated in the same second. In a real context the dates should be very different. Would you like to add a number of something ? It was in the initial design but @tuscland said that giving version number to item update maybe confusing. |
What's strange is that if move my mouse away, the dropdown disappears (so in my mind I think "okay, the dropdown is gone now") and then it's open again even though I haven't clicked anything. I would expect to either keep it open, or keep it closed. Another way of saying this is: I think moving the mouse far enough away should "explicitely" close the dropdown. |
This "log naming" thing could be transformed into a separate more global issue? We will face the same with historization of cross-validation, we want something to identify the runs, and maybe give some comments about the run name:
WDYT of creating a new separated issue? |
Note that naming a version was not in the spec. Think about managing versions for all items. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hello!
I categorized my review in three parts:
Things I loved ❤️
- I love that the item bin is now easily accessible!
- I like the easy switch to latest version, it's helpful
Questions:
- about version naming. I see that it's something discussed above. maybe we could call them iteration and just give them increasing numbers?
- didn't the plus button of items used to be orange?
cf this screen shot for the plus:
Change requested:
- The warning logo, when I'm viewing an old item is way too small. I didn't understand what it was at first.
- Same for the icons of the right of items, they are a bit too small imo.
- The "tick" in toaster doesn't seem aligned
About naming the iterations/versions/whatever instead of having "17 min ago" is important to me because I want to be able to find back which item i've seen the day before. If I find interesting to see iteration number 5, I want to be able to show it again to the rest of my team of whatever the following day, it must be easy to find if back. |
|
Nope, the idea is that views are orange and items blue. |
Accordion item actions are now 1.14rem. |
I would still need all the icons (warning + branches + bin) to be a bit bigger please.
Very good for me! It's not pushed yet, is it? (at least it doesn't display in my navigator) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Matthieu, this will enable our next release tomorrow :) !!
- project store as been updated to manage updates - updates are stored in session storage to limit memeory footprint - card quick action have been introduced to have one click delete and browse history - on click on an item update an event is emitted, the view listens to it and calls the store to update the list of `PresentableItem` reactivelly UI preview: https://github.com/user-attachments/assets/e156e38c-ec3f-4cb9-a461-7dbc9d2df61f
PresentableItem
reactivellyUI preview:
history.mp4