Assorted UX improvements #1741
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1741
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
These are my quick insights from using Vikunja for a bit. I'm happy to have a go at a few of these once I get up to speed with Vue and the codebase but I wanted to share my initial thoughts.
Thank you for the suggestions! I've added most of them to the public roadmap to be on the same list with the rest.
A few comments:
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.
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.
I plan on making it a fixed width on desktop which should give it more space. Eventually it will be resizable.
I'm not sure if that's possible with css currently? Happy to take any hints.
Generally I'm not that happy with the current scrollbar design, maybe changing that in other ways could be a good idea.
Definitely.
Both views are able to set the range in between which the tasks should be shown, I think we can expand on that.
That probably also requires changes on the api side. I've yet to figure out how to make that useful for everyone while not bloating the ui.
This probably also requires a new api endpoint to search for both in one request but could work with the current api endpoints too.
I'm not sure about this as it would add another icon on the right.
Do you mean the spacing between the namespaces/lists and the general nav items or the spacing between the items themselves?
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.
Sounds like a good idea. Giving a brief description of what it is helps too.
Ah, perfect. Fixed on desktop sounds good and then allow resizing within certain limits.
Perhaps something like
This works for me (from https://stackoverflow.com/questions/10015389/showing-scrollbars-only-when-mouseover-div/10015883). Otherwise we could use JS.
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.
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.
Spacing between items themselves. Looks like it's currently .75em, I think .5em works and feels more natural.
Thanks for hearing me out! Usually I would add each as an issue, but I would prefer not to create issue spam as part of my first posts :P
Maybe we can do something with the
::-webkit-scrollbar
stuff to hide them unless hovered. This would be more or less progressive enhancement though since browser support is limmited (at least for now).Do you want to send PRs for a few of these?
Sounds good. Will do when I get up to speed with the codebase and setup my dev environment!
A couple things that I noticed with more use:
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.
A bit on labels (now using this issue as a temp list for things I notice!)
Searching is case-sensitive when you're using postgres, it is not when using any other db. That's something that needs to be fixed at the api-level.
I'm closing this as I feel most of these issues are resolved with the latest version(s). Feel free to reopen this issue or open a new one if you find any other problems.