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
Better UI for adding form fields #1070
Comments
Can we unify the UI for adding these extra fields with the UI for adding a new tag generally (the [+] in "Additional tags")? |
Yes, good idea, these should look the same. I am going to rework the "new tag" UI a bit early next week to be more in-line with some of the other changes I've been making. |
Here's what I'm thinking right now, patterning on the 'more' button on the grid. By default we surface a number of common preset forms, and then allow searching for more: Collapsed: Expanded: I tried an alternative style that matched the 'more' button on the tag editor, but not as into it. |
I was thinking of having a single field search box, absolutely positioned at the bottom, that either adds known fields, or if nothing matches, a new "Additional" tag (so it would replace the + button at the bottom of additional fields). The search results would be in a pop up above the search box (since it's at the bottom). If we're ambitious we could do a transition animation from a selected search result to the added field/tag. I think we should also try making the additional tags have the same round rect look as the other fields, with "Additional Tags" as the label on top and the tag list as the form below. |
I'd like to hear your rationale around unifying the UI for the tag editor and the preset form fields. To me, there continues to be value in keeping these two different ways of tagging features completely separate and parallel. Not only should the tag editor continue to be hidden, it should also include all the tags, including those captured in the preset form. As it is, I find the decision to hide tags from the tag editor that are captured in the preset form unintuitive. Our target audience should be users who are never (or at least not when they start) going to use the tag editor or understand what a "tag" is, and at the same time, we should allow full control over tags through the tag editor for users who know what they are doing. |
⇢ #2365 |
Unlabeled icons were fine with less than 6, but not a scalable approach.
The text was updated successfully, but these errors were encountered: