Realization of custom settings for each project about qgis-searchlayers-plugin

[hamiltoncj]

Sorry I haven't responded sooner. I have been busy with a paper justifying the use of QGIS in our organization. There is the possibility that I may not be allowed to do any more QGIS plugin development.

My question is why would you want to have a variable of the layers you want to search? Why not just select them in the QGIS layer panel and search on them? I don't think the capability you are asking for would be approved to have added to Search Layers.

If you download the new i18n/searchLayers_ja.ts file you can translate , , and strings. Those I can add and update.

[yamamoto-ryuzo]

Thank you for your response.
It is perfectly fine if you answer at your own pace.

We are currently working on the search functionality, both with the search plugin we are creating and with this great plugin.
We are wondering if it would be possible to consolidate to this plugin.
The first step is to make it Japanese.

The second part is to simplify the search screen.
The reason is that we have dozens of layers that we don't need as search targets, but often only a few that we need.
In such cases, we would like to customize it because it is difficult to find the selection target in its current state.

The future proposal is also realistic and has already been implemented in our plugin.
If it suits your purpose, we would be happy to implement it.

If it looks good, I will make a pull request.

[yamamoto-ryuzo]

Thank you for your continued support regarding the translation.
Pull requests for ts files only.

[hamiltoncj]

I think the changes are reasonable. As far as I can tell the only changes you have made is to searchDialog.py and i18n\searchLayers_ja.ts. You have a different readme.md and several other files created by something, which don't affect the plugin. Do you want me to just replace the two files without you needing to do a pull request? That might prevent some unnecessary files getting merged.

[yamamoto-ryuzo]

That is correct.
In fact, I was baffled when I made a modified PULL request for another plugin in my environment and the whole thing was replaced.
I thought I should learn more about how to PULL in different working environments.
As a result, I now set up a separate repository from the PULL to modify it.

[yamamoto-ryuzo]

The search we use, which we are currently considering integrating, was recently open sourced and is in the process of being generalized.
We will consider it again when that one is completed.
https://github.com/yamamoto-ryuzo/GEO-search-plugin

[hamiltoncj]

I am not used to working with others on this so this is all new to me as well. Since I came from a C/C++ background I think there is probably a better way to manage the python code rather than using a makefile. It is all a learning process.

Are you planning on doing a pull request with those two files that have changed or do you want me to drop them into my code repo?

[yamamoto-ryuzo]

[do you want me to drop them into my code repo?]
　I'll study it next time.
First of all, I would like to make a PULL request for the realization of custom settings for each project, which is the original purpose of this project.
We will consider other feature proposals as soon as the plugin we have created is generalized.
Thank you in advance.

[yamamoto-ryuzo]

#18