[GH-ISSUE #401] Redesign of the tags UX

kerem commented

2026-02-28 12:03:37 +03:00

Owner

Originally created by @majkinetor on GitHub (May 7, 2023).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/401

Originally assigned to: @VShawn on GitHub.

Tags UX is needlessly large and non responsive:

details

Tags UX should be completelly redesigned.

Tasks

Remove # in the name, it just spams, tags have clear UI place on both lister and launcher
Make list responsive (regression)
Context option to close tag tab (right click on tab)
Change tab order by drag and droping them (useful with #405 ALT + n)
~~Tag details with middle click~~
~~1. Tag description (to be shown in a tooltip)~~
~~2. Tag hotkey?~~
Add pin tag as context menu item instead of using a checkbox which spams a lot and is used a little
Tags should not be case sensitive
- Currently tag lists shows both lowercase and uppercase tags with different counts
- However, pinning them, you get the same view

Originally created by @majkinetor on GitHub (May 7, 2023). Original GitHub issue: https://github.com/1Remote/1Remote/issues/401 Originally assigned to: @VShawn on GitHub. Tags UX is needlessly large and non responsive: <details><summary>details</summary> ![image](https://user-images.githubusercontent.com/85767/236676707-d7e0367a-7221-4624-8212-933296f6b463.png) </details> Tags UX should be completelly redesigned. ## Tasks 1. [x] Remove # in the name, it just spams, tags have clear UI place on both lister and launcher 2. [x] Make list responsive (regression) 3. [x] Context option to close tag tab (right click on tab) 4. [x] Change tab order by drag and droping them (useful with #405 ALT + n) 5. [ ] ~~Tag details with middle click~~ ~~1. Tag description (to be shown in a tooltip)~~ ~~2. Tag hotkey?~~ 7. [x] Add pin tag as context menu item instead of using a checkbox which spams a lot and is used a little 8. [x] Tags should not be case sensitive - Currently tag lists shows both lowercase and uppercase tags with different counts - However, pinning them, you get the same view

kerem

2026-02-28 12:03:37 +03:00

closed this issue
added the
meta-enhancement

bug

general-ux

area-tags
labels

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@majkinetor commented on GitHub (May 8, 2023):

BTW, this tag list not showing in columns is something that apperaed in 1.0.beta3, in 0.4 it was not like that.

@majkinetor commented on GitHub (May 8, 2023): BTW, this tag list not showing in columns is something that apperaed in 1.0.beta3, in 0.4 it was not like that.

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@majkinetor commented on GitHub (May 8, 2023):

Actually, I dont know what I was thinking when I sad that clicking on tag could be used as a checkbox, as clicking on tag is used to activate that tag. But nevertheless, this is simple to change, we could add "pin tag" in context menu which doesn't spoil the UX as pinning is not that frequent operation.

Regarding number of columns, I think they should just be listed horizontally as much as it can be filled with current screen, there is no need to artificially introduce columns as you may have short and long tags. They could be sorted by name (like now) or frequency. This should be very easy to implement and maintain and it will be responsive relative to the screen size.

@majkinetor commented on GitHub (May 8, 2023): Actually, I dont know what I was thinking when I sad that clicking on tag could be used as a checkbox, as clicking on tag is used to activate that tag. But nevertheless, this is simple to change, we could add "pin tag" in context menu which doesn't spoil the UX as pinning is not that frequent operation. Regarding number of columns, I think they should just be listed horizontally as much as it can be filled with current screen, there is no need to artificially introduce columns as you may have short and long tags. They could be sorted by name (like now) or frequency. This should be very easy to implement and maintain and it will be responsive relative to the screen size.

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@majkinetor commented on GitHub (May 8, 2023):

Mockup:

[ Tag details             x]

name:             tag1
description:      Foo bar baz

[Delete tag]       [Pin tag] [Save]

@majkinetor commented on GitHub (May 8, 2023): Mockup: ![image](https://user-images.githubusercontent.com/85767/236863223-f83575ec-7922-488d-920f-b1a7711b906e.png) ``` [ Tag details x] name: tag1 description: Foo bar baz [Delete tag] [Pin tag] [Save] ```

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@majkinetor commented on GitHub (May 8, 2023):

Not sure if we need group by database... or even limiting view by having combo with database selection.

@majkinetor commented on GitHub (May 8, 2023): Not sure if we need group by database... or even limiting view by having combo with database selection.

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@VShawn commented on GitHub (May 9, 2023):

Mockup:

[ Tag details             x]

name:             tag1
description:      Foo bar baz

[Delete tag]       [Pin tag] [Save]

new users may not know there's a right click menu for pin.

@VShawn commented on GitHub (May 9, 2023): > Mockup: > > ![image](https://user-images.githubusercontent.com/85767/236863223-f83575ec-7922-488d-920f-b1a7711b906e.png) > > ``` > [ Tag details x] > > name: tag1 > description: Foo bar baz > > [Delete tag] [Pin tag] [Save] > ``` new users may not know there's a right click menu for pin.

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@majkinetor commented on GitHub (May 9, 2023):

If that is your worry, we can add a message 😃

@majkinetor commented on GitHub (May 9, 2023): If that is your worry, we can add a message 😃 ![image](https://github.com/1Remote/1Remote/assets/85767/6a1ba824-2680-4e97-b415-68dc142d3b20)

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@majkinetor commented on GitHub (May 16, 2023):

@VShawn can you quickly fix regression in latest 2 versions? Tag list is unusable now.

Unless you already started working on this then I will wait :)

@majkinetor commented on GitHub (May 16, 2023): @VShawn can you quickly fix regression in latest 2 versions? Tag list is unusable now. Unless you already started working on this then I will wait :)

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@VShawn commented on GitHub (May 17, 2023):

I won't working on this befor #409 is closed.

I working on #395, and then #409, and then this one :)

@VShawn commented on GitHub (May 17, 2023): I won't working on this befor #409 is closed. I working on #395, and then #409, and then this one :)

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@majkinetor commented on GitHub (May 17, 2023):

OK, that will take time then. Can you fix this quickly becuase I can't pin antyhing without too much stress any more :)

EDIT: Ah, ignore, I just realized I was stupid and scrolling horizontaly instead of using search 🙄

@majkinetor commented on GitHub (May 17, 2023): OK, that will take time then. Can you fix this quickly becuase I can't pin antyhing without too much stress any more :) ![image](https://github.com/1Remote/1Remote/assets/85767/5a91e1de-f3fb-4f7e-980d-f568498c56ae) EDIT: Ah, ignore, I just realized I was stupid and scrolling horizontaly instead of using search 🙄

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@VShawn commented on GitHub (May 18, 2023):

The tag description seems not not to be very necessary, but the cost of it is high.

For example, it requires designing a new tag table (the current tag only stores a string in connection json), and handling data synchronization of the tag table when add \ del \ rename tags, and resolving situations where there are tags with the same name but different descriptions in two databases.

Therefore, please reconsider this. If it must be done, please create a new ticket specifically for it.

And case insensitivity is rude. You should not decide for the user that they cannot use "ab" after using "AB". AFAIK green is color while Green is a name.

@VShawn commented on GitHub (May 18, 2023): The tag description seems not not to be very necessary, but the cost of it is high. For example, it requires designing a new tag table (the current tag only stores a string in connection json), and handling data synchronization of the tag table when add \ del \ rename tags, and resolving situations where there are tags with the same name but different descriptions in two databases. Therefore, please reconsider this. If it must be done, please create a new ticket specifically for it. And case insensitivity is rude. You should not decide for the user that they cannot use "ab" after using "AB". AFAIK green is color while Green is a name.

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@majkinetor commented on GitHub (May 18, 2023):

OK, tag table is natural thing to have, I didn't think you would just put tags in connections. Lets skip it.

And case insensitivity is rude.

Almost no tag system I know is case sensitive. There is nothing rude about it, its expected, especially on Windows where file names are not case sensitive. If that is so, then activation (and also # search) has a bug - if I click tag name, i should see that exact tag name, not all the variants like now:

That makes no sense and if not having case is rude, then this is maximum rude.

@majkinetor commented on GitHub (May 18, 2023): OK, tag table is natural thing to have, I didn't think you would just put tags in connections. Lets skip it. > And case insensitivity is rude. Almost no tag system I know is case sensitive. There is nothing rude about it, its expected, **especially on Windows** where file names are not case sensitive. If that is so, then activation (and also # search) has a bug - if I click tag name, i should see that exact tag name, not all the variants like now: ![image](https://github.com/1Remote/1Remote/assets/85767/2a7dbba0-8362-4c20-b4b4-a4d4ed877de7) That makes no sense and if not having case is rude, then this is maximum rude.

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@VShawn commented on GitHub (May 18, 2023):

Yes there is a problem within tag search because when I developing this feature, I wanted to enable fuzzy searching while also supporting case sensitivity.... no better solution was found.
and please consider another situation: there is a tag "abcd" in db1 and a tag "Abcd" in db2. Should we merge these two tags if the it is not case sensitive? And when displaying the tag, should it be displayed as "abcd" or "Abcd"?

I have considered case sensitivity when building the tag system from the beginning, but these 2 still bother me now. I have thought about convert all tags to lowercase, but as mentioned sometimes capitalization can change the meaning of a word.

@VShawn commented on GitHub (May 18, 2023): 1. Yes there is a problem within tag search because when I developing this feature, I wanted to enable fuzzy searching while also supporting case sensitivity.... no better solution was found. 2. and please consider another situation: there is a tag "abcd" in db1 and a tag "Abcd" in db2. Should we merge these two tags if the it is not case sensitive? And when displaying the tag, should it be displayed as "abcd" or "Abcd"? I have considered case sensitivity when building the tag system from the beginning, but these 2 still bother me now. I have thought about convert all tags to lowercase, but as mentioned sometimes capitalization can change the meaning of a word.

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@majkinetor commented on GitHub (May 18, 2023):

there is a tag "abcd" in db1 and a tag "Abcd" in db2. Should we merge these two tags if the it is not case sensitive?

What I do in my projects is lowercase them. Nobody ever complained.

As an example from the wild, Diigo which has tags as basic mechanism (you can't really use it without it, so you have hundreeds of them) lowercases them in the tag list and autocomplete, but keeps user input as it is:

Search shows lower case variants always
Its listed as it is input on the bookmark
All tags are listed lowercase in the tag list

So you could go that way, its IMO good UX as tags are listed as input on most important place and the one that you see most often - the objects having them (connections in this case).

So to recap:

Keep user input as it is
Search case insensitive
Show tag list lowercase

So tags are case insensitive during operations but shown with exact case that user set on individual connections.

@majkinetor commented on GitHub (May 18, 2023): > there is a tag "abcd" in db1 and a tag "Abcd" in db2. Should we merge these two tags if the it is not case sensitive? What I do in my projects is lowercase them. Nobody ever complained. As an example from the wild, [Diigo](https://diigo.com) which has tags as basic mechanism (you can't really use it without it, so you have hundreeds of them) lowercases them in the tag list and autocomplete, but keeps user input as it is: - <details><summary>Search shows lower case variants always</summary> ![image](https://github.com/1Remote/1Remote/assets/85767/3de43d75-2f51-4b8a-82ed-983ced1658dd)</details> - <details><summary>Its listed as it is input on the bookmark</summary> ![image](https://github.com/1Remote/1Remote/assets/85767/6881abec-73aa-4c8b-bbed-3a3c4b416b32)</details> - <details><summary>All tags are listed lowercase in the tag list</summary> ![image](https://github.com/1Remote/1Remote/assets/85767/0748464d-aafb-429b-ae9c-3567609f1049)</details> So you could go that way, its IMO good UX as tags are listed as input on most important place and the one that you see most often - the objects having them (connections in this case). So to recap: 1. Keep user input as it is 2. Search case insensitive 3. Show tag list lowercase So tags are case insensitive during operations but shown with exact case that user set on individual connections.

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@majkinetor commented on GitHub (May 24, 2023):

@VShawn, It would be good to consistently allow for context menu, not only in tags:

@majkinetor commented on GitHub (May 24, 2023): @VShawn, It would be good to consistently allow for context menu, not only in tags: ![image](https://github.com/1Remote/1Remote/assets/85767/c2a7a367-7352-4aac-a8c5-60a07a6f32aa)

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@VShawn commented on GitHub (May 24, 2023):

@VShawn, It would be good to consistently allow for context menu, not only in tags:

Yeap I woring on this now, since the 'right click ed' hijacked the mouse right click event, i need to refact this part to make context menu work

@VShawn commented on GitHub (May 24, 2023): > @VShawn, It would be good to consistently allow for context menu, not only in tags: > > > > ![image](https://github.com/1Remote/1Remote/assets/85767/c2a7a367-7352-4aac-a8c5-60a07a6f32aa) > > > > Yeap I woring on this now, since the 'right click ed' hijacked the mouse right click event, i need to refact this part to make context menu work

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@majkinetor commented on GitHub (May 25, 2023):

In latest nightly some tags do not work. Clicking them on the main list does nothing, but they can be selected from the Tags tab.

You change the case of tags on editing connection (sometimes)

Different case in bulk edit is not recognized as same tag (maybe it shouldn't though)

@majkinetor commented on GitHub (May 25, 2023): In latest nightly some tags do not work. Clicking them on the main list does nothing, but they can be selected from the Tags tab. You change the case of tags on editing connection (sometimes) Different case in bulk edit is not recognized as same tag (maybe it shouldn't though)

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@VShawn commented on GitHub (May 25, 2023):

You change the case of tags on editing connection (sometimes)
Different case in bulk edit is not recognized as same tag (maybe it shouldn't though)

The logic has become confusing, I am considering converting all tags to lowercase.

@VShawn commented on GitHub (May 25, 2023): > You change the case of tags on editing connection (sometimes) > Different case in bulk edit is not recognized as same tag (maybe it shouldn't though) The logic has become confusing, I am considering converting all tags to lowercase.

kerem commented

2026-02-28 12:03:38 +03:00

Author

Owner

@majkinetor commented on GitHub (May 25, 2023):

Its not worth complicating, so it should be done.

@majkinetor commented on GitHub (May 25, 2023): Its not worth complicating, so it should be done.

Rows
Columns

[GH-ISSUE #401] Redesign of the tags UX #1302

Tasks