TerosTechnology / vscode-terosHDL

VHDL and Verilog/SV IDE: state machine viewer, linter, documentation, snippets... and more!
https://terostechnology.github.io/terosHDLdoc/
GNU General Public License v3.0
571 stars 46 forks source link

Issues in the configuration #680

Open ecstrema opened 1 month ago

ecstrema commented 1 month ago

Here an aglomerate of issues related to the settings UI and implementation.

1) You currently have an array of tools, but only one is selected in the General page. All others should not be shown, and only the configuration for this tool should show up, in the same page, just below the tool selection under a section like "Tool options".

![image](https://github.com/user-attachments/assets/6a439224-9b2b-4559-85f6-1f7e0fa25c61) ![image](https://github.com/user-attachments/assets/87e7093c-2824-4dfc-aea9-6236b1fcba3a)

2) The last point also applies to the linter and formatter settings. 3) A lot of these options seem completely unrelated:

This one is actually pretty funny: ![image](https://github.com/user-attachments/assets/ff824d05-fc74-4c55-9d29-e7c8b8e94d07)

Actually, all of this is mostly trivial things, but since the documentation is very very sparse, and examples even rarer, it makes up for something that's super hard to work with, although once you get the hang of it, it works incredibly well!

My recommandation may be very radical, but that is how other extensions work, and I think it works very well.

1) Move all settings related to the user (not to the project) to vscode's own settings mechanism. 1) All binary paths (python, make, gtkwave, etc) 2) All preferences (stutter mode, schematic viewer, etc) 2) Move all tool settings to configuration files. This is often how these tools are configured anyway. 3) Is there anything remaining?

Overall, thank you for TerosHDL, it works super well, and integrates nicely with VSCode.

Have a good day!