Currently the CONFIG command of WinBuilder works fine for unhandicapped people: It shows a html formular which can be changed by the user.
Unfortunatelly this formular is not detected by screen readers like NVDA.
When the blind user wants to change something in the configuration he has to find and edit certain XML file(s). That can become a hard job.
I wrote a small batch plugin.cmd as wrapper to an executable jar PluginEx.jar.
PluginEx.jar and it's library pluginhandler.jar are included in Win7PE version 2013.12.29 and above.
To use plugin.cmd, start a windows command session, CD to downloads\300-Win7PE in your WinBuilder directory, and execute the batch with the necessary argument(s).
Here the currently provided commands:
"refresh" rebuilds settings.xml and settings.html after installing / deinstalling a plugin.
"plugin plugins" lists all available plugins. The list is visible to NVDA
"plugin activeplugins" lists all plugins which will be added to the next build. The list is visible to NVDA
"plugin components" lists all available components. The list is visible to NVDA
"plugin usedcomponents" lists all components which will be added to the next build. The list is visible to NVDA
In the following lines myPlugin and myComponent have to be replaced by the real names, like e.g NVDA
"plugin activate myPlugin" or "plugin deactivate myPlugin" will cause myPlugin beeing encluded / excluded in the next build.
"plugin use myComponent" or "plugin unuse myComponent" will cause myComponentbeeing encluded / excluded in the next build.
If somebody needs some other important config choices in the wrapper, please let me know.
I intentionally did not include ALL config details. I do not like something filled with in the actual case unneeded features.
BTW: Here the Windows batch plugin.cmd is published. IMO batches for Linux and Mac OS are not sencefull, because AFAIK NVDA and JAWS are currently only available for Windows.