Now installing the gadget is only possible with a single path to the configuration and settings page:

• {NS_PROJECT}:Ultraviolet/configuration.json
• {NS_PROJECT}:Ultraviolet/Preferences

Since different language projects have completely different schemes for creating pages for gadgets, and some may not have one at all, the inability to configure the path to settings and configuration does not allow adaptive deployment of a gadget in a local project.

In my opinion, the path to the configuration should be specified in the variable that is defined when calling the gadget. And the path to the settings is already inside the configuration itself.