Expand Plugin API

[taooceros]

#220

Expand IPublicAPI for plugin users to use.

1. StringMatcher.FuzzySearch()
2. Http.GetAsync & Http.GetStreamAsync & Http.DownloadAsync
3. Add & remove ActionKeyword

Detail Implementation require further discussion.

[taooceros]

@Flow-Launcher/team any idea?

[Zeroto521]

add some hooks, see jjw24/Wox#194

I want to be hook master.

[taooceros]

add some hooks, see jjw24/Wox#194

I want to be hook master.

emmm I am not sure what do you mean for hook...... Do you mean that we should allow plugin to do more things besides querying?

[jjw24]

why we exposing action key word methods?

[taooceros]

why we exposing action key word methods?

To allow plugins to have more than one actionkeyword. Currently, although we allow mutiple keywords, only internal plugins can utilize it because external plugin has no access to their actionkeywords.

[taooceros]

Also, plugins won't be available to change action keywords for other plugin since they don't know the id of other plugin.

[Zeroto521]

Exposed the system calling function process.

There would have a hook called before_user_query.
It means to do something before the query.
A simple example is that it could be used to log querying words.

[taooceros]

Exposed the system calling function process.

There would have a hook called before_user_query.
It means to do something before the query.
A simple example is that it could be used to log querying words.

Like registering an event that will be triggered before querying? But why don't we do the job when querying? to bypass the action keyword restriction?

[jjw24]

why we exposing action key word methods?

To allow plugins to have more than one actionkeyword. Currently, although we allow mutiple keywords, only internal plugins can utilize it because external plugin has no access to their actionkeywords.

more than one action keyword like in websearch plugin?

[taooceros]

why we exposing action key word methods?

To allow plugins to have more than one actionkeyword. Currently, although we allow mutiple keywords, only internal plugins can utilize it because external plugin has no access to their actionkeywords.

more than one action keyword like in websearch plugin?

Yes, and in Explorer plugin.

[Zeroto521]

You should not do a stack of things in one place. And some hooks better could have global authority. before_all_user_query could do something before each plugin.

…

在 2021年1月9日，15:03，taooceros ***@***.***> 写道：  Exposed the system calling function process. There would have a hook called before_user_query. It means to do something before the query. A simple example is that it could be used to log querying words. Like registering an event that will be triggered before querying? But why don't we do the job when querying? — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[jjw24]

i think i have also done some changes on this stringmatcher migration but got distracted. I might merge them in if feasible and ok

[taooceros]

You should not do a stack of things in one place. And some hooks better could have global authority. before_all_user_query could do something before each plugin.

Do you want it to be activated for plugins? Like an event, allowing plugin to do something here, that will be triggered before plugin querying every time user is querying. Or it is simply something that we just do in Flow.

[taooceros]

@Zeroto521 Let's move that discussion to #267 , since this pr is majorly focusing on the APIs lie in IPublicAPI.