A bit on labels (now using this issue as a temp list for things I notice!)
- Random color should be assigned instead of just grey
- Searching should be case-insensitive
- Adding label list should be pre-populated with some existing labels
Aha! I was aware it was a debug message but found the 54 logs slightly odd. Didn't know it was support only by Chrome, good to know!
Sounds good. Will do when I get up to speed with the codebase!
A couple things that I noticed with more use:
- When I hover over the edit, it'd be nice to get some visual feedback as the response is different when I click on the pencil vs when I click on the item itself
- The edit button experience could be improved. I usually use the button to edit some quick mistake I made when I created the task and those are mostly in the title, the labels, and the date. Instead of opening the side panel, allow me to edit these things very quickly and easily by expanding the item in a similar fashion to Todoist:
-
Open a modal instead of a side panel when I click on the task. I think overall this is better UX because a full page for a task feels a bit much. If we had a modal and views to toggle between like "Comments", "Edit", and so on within that model, it would make it a lot more intuitive.
-
The edit side panel should go away once I finish saving, or at least click outside of the panel.
The colors are pretty much random and are coming from the colorpicker library - I'm not 100% sure if it supports setting them. Maybe that would require an upstream PR.
Ah. Random colors probably won't look very well most of the time, unless we optimize for them being more bright. I was thinking a fixed list from say https://material.io/design/color/the-color-system.html#tools-for-picking-colors and giving them names. Possibly allow the user to choose their own colors in addition.
I had the same thought after implementing and using it for a while. It can be set to an empty string, I think that's probably the best to do by default for now since it's not something I would guess many people are using.
Sounds like a good idea. Giving a brief description of what it is helps too.
I plan on making it a fixed width on desktop which should give it more space. Eventually it will be resizable.
Ah, perfect. Fixed on desktop sounds good and then allow resizing within certain limits.
I'm not sure if that's possible with css currently? Happy to take any hints.
Perhaps something like
div.myautoscroll {
height: 40ex;
width: 40em;
overflow: hidden;
border: 1px solid #444;
margin: 3em;
}
div.myautoscroll:hover {
overflow: auto;
}
This works for me (from https://stackoverflow.com/questions/10015389/showing-scrollbars-only-when-mouseover-div/10015883). Otherwise we could use JS.
Move "Next week" and "Next month" into an "Upcoming" page and allow me to toggle between whichever view I wish
Both views are able to set the range in between which the tasks should be shown, I think we can expand on that.
My motivation is that I would like to reduce the number of items on the sidebar to make using Vikunja really intuitive. If we have something that shows all tasks, today's tasks, and upcoming tasks (with configurable + preset date ranges), that would be the most intuitive.
Make collapsing namespaces more user-friendly with a dropdown indicator, eg "v" for opened, and " >" when closed
I'm not sure about this as it would add another icon on the right.
Knowing if a namespace is collapsed is tricky without this kind of visual feedback. It can even be added to the left of the imaginary vertical line that all nav items are aligned to.
Move sidebar items closer together vertically
Do you mean the spacing between the namespaces/lists and the general nav items or the spacing between the items themselves?
Spacing between items themselves. Looks like it's currently .75em, I think .5em works and feels more natural.
Thanks for hearing me out!