Some first review after the Vue merge. :) As usual itās very nice, these are mostly polishing details!
(This is a review similar to Design polishing of new event popover #1570)
presize: none;:show-no-options="false" (ref https://github.com/nextcloud/mail/pull/2131/files#diff-0c91f331a566b5adc2f044cca683b078R55, we should probably make this default in the component as it just looks bad?)Thatās all for now. :tada:
In general for Reminders and Repeat we for sure need to look more at what others like Google Calendar, Apple Calendar and Business Calendar (Android) are doing. :)
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Event title seems rather small. In the popover itās 20 px, here only 16.
The menu button by default has a grey circle, which is too much emphasis. This should only happen on hover or focus as per standard.
The "x days ago" subline is not a heading so should not be h4 but simply a p
These are all the default style of nextcloud/vue. Would you mind opening a ticket there :)
The timepicker itself is also quite strange. Difficult question how to fix that one, but at least it should start at 12:00 instead of 00:00, because 00:00 is one of the least likely times for an event to start. :)
Already fixed earlier today in https://github.com/nextcloud/calendar/pull/1563
Thanks for the valuable feedback. Will look into the rest tomorrow :)
In general for Reminders and Repeat we for sure need to look more at what others like Google Calendar, Apple Calendar and Business Calendar (Android) are doing. :)
Reminders is pretty much how it works in Google calendar. Especially that all-day and timed have different ways of entering. 5 minutes before vs. 1 day before at 9am
And Repeat is heavily inspired by macOS.
But I agree that it needs some CSS love. better spacing, etc.
Dropdown for new reminder.
Current behaviour is no properly discoverable that it automatically adapts
- [ ] Free / Busy only has 2 choices so it doesnāt need to be a dropdown. It could simply be 2 radio choices next to each other.
- [ ] Similar with "Confirmed/Tentative/Cancelled" which could be a radio choice to have all visible at the same time. Isnāt this also what Google Calendar does simply with "Attending: Yes / No / Maybe"?
- [ ] And same thing for the "When shared: Show full event / Show only busy / Hide event".
@jancborchardt Are you sure about this?
That means that we will show 8 radio buttons at a time, quite a lot.
And with all the different translations out there, we are not able to fit each set of them in a row.
It doesnāt seem to use the standard emptycontent styles? Or is this a new/separate Vue component?
There is a standard? There is at least no vue-component for it yet.
@jancborchardt Are you sure about this?
That means that we will show 8 radio buttons at a time, quite a lot.
No, thatās the stuff Iām least sure about ā letās leave it for last, if at all. :)
There is a standard? There is at least no vue-component for it yet.
If you like, feel free to adapt it based on the emptycontent styles of the files app content area e.g. for empty folders and make a component out of it. :)
[ ] The input placeholder wording should be fixed to "Add emails, users, contacts or conversations"
Why conversations?
[ ] The input placeholder wording should be fixed to "Add emails, users, contacts or conversations"
Why conversations?
I guess I thought you can add Talk conversations? Ignore if thatās not the case. :D
I filed an upstream issue to help speed up event time selection. Just thought I would reference it here.
Ok, so the upstream project for the datetime picker has added an event object to the open event. So, I believe the process to open the time picker if the time element is clicked would be:
Again, I don't have any experience with Vue, so I'm not exactly sure how to actually do any of those steps, but I'm hoping they would be straightforward.
Do we know what the process is to get the upstream changes merged into the Nextcloud fork of vue2-datepcker? Once that's done, is someone interested in implementing this, or would the project be open to a PR for it?
The author of the vue2-datepicker graciously put together a code sandbox demonstrating how to accomplish this! Here it is:
https://codesandbox.io/s/open-time-panel-8wm3g?file=/src/App.vue
So, now it looks like the only issue would be getting the changes to trickle down into the Nextcloud fork of that component. Is that process automated, or would it be a good idea for me to raise an issue somewhere?
Most helpful comment
The author of the vue2-datepicker graciously put together a code sandbox demonstrating how to accomplish this! Here it is:
https://codesandbox.io/s/open-time-panel-8wm3g?file=/src/App.vue
So, now it looks like the only issue would be getting the changes to trickle down into the Nextcloud fork of that component. Is that process automated, or would it be a good idea for me to raise an issue somewhere?