-
-
Notifications
You must be signed in to change notification settings - Fork 449
Grouping in Plugin Store #1457
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
Grouping in Plugin Store #1457
Conversation
if installed and no update, should we not just hide it from store? |
It is an issue that has been considered. I concluded that it was better not to hide. my reasons...
The proposals were "hide it" or" label it," but I think this is a proper compromise since I order it down and labeled it. It is a matter of policy determination. If there are other opinions, I can be reflected. I think it's okay to hide it. It doesn't matter to me. |
/* Label Data for Plugin Store */ | ||
public bool LabelNew { get; set; } | ||
public bool LabelInstalled { get; set; } | ||
public bool LabelUpdated { get; set; } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's move this to a viewmodel for plugin store.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How to? I'm not good at organizing things like this.
|
||
namespace Flow.Launcher.Converters | ||
{ | ||
public class BoolToVisibilityConverter : IValueConverter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I remember these's a buildin boolconverter (used by @Sparrkle before). So let's use that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I remember I saw it. but where is it?
- remove comment
- Add sources - Hide Updated label when LabelNew
Ok makes sense 👍 |
- Adjust Strings
…auncher into InstalledLabel5
I noticed I was wrong plugin store label plan. |
- Changed 'New' logic. - Fix order - Adjust Strings
|
At this point I'd like to keep the |
This task is no longer required? |
It required. |
I rewrite description and testcase things. check the top of this page please. |
<system:String x:Key="updatebtn">Update</system:String> | ||
<system:String x:Key="LabelInstalledToolTip">Plug-in already installed</system:String> | ||
<system:String x:Key="LabelNew">New Version</system:String> | ||
<system:String x:Key="LabelNewToolTip">This plug-in has been updated within the last 7 days</system:String> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe use "plugin" instead of "plug-in". We use "plugin" in all other texts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK.
Just added 3 commits:
|
New Version
What's the PR
Test Cases
### Old Version ### **What's the PR** - New / Installed / Updated Label in Plugin Store. - Based Plugin Search PR. so this pr should merge when done plugin Search PR. - It was implemented in the form of adding a value to the list using the for syntax. (LabelNew=true...)Label Type
Test Cases
Remain Tasks