@Marxsal The reason my .\dev stuff is confusing is largely because I've been using it for stuff inside .\dev\test\ that I think would now be confusing.
If we had more than 3.25 potential users I could use it to make a nice interactive demo. But, as is, its far too time consuming to document.
The items of mine that are likely most worth having in .\dev are ...
.\dev\do-pathcheck.ps1 flexible tool to check any path to dirs or files, allows relative addressing on check plus wildcards;
.\dev\do-grabwiki.ps1 in process experimental tool to capture directory listings for wikis and bulk convert into .ini data, allows relative addressing on check and wildcards; (works through piping directory listing to file and running a regex over it).
.\dev\permissions.bat that Windows tool that may at some point have value. We'd need users to know that. (I have an update of it I'll include in my next)
My feeling is that, unless you actually use the test system, (including "P" and all "polly-test*.bat") can be removed.
@Marxsal The reason my .\dev stuff is confusing is largely because I've been using it for stuff inside .\dev\test\ that I think would now be confusing. If we had more than 3.25 potential users I could use it to make a nice interactive demo. But, as is, its far too time consuming to document.
The items of mine that are likely most worth having in .\dev are ...
.\dev\do-pathcheck.ps1 flexible tool to check any path to dirs or files, allows relative addressing on check plus wildcards;
.\dev\do-grabwiki.ps1 in process experimental tool to capture directory listings for wikis and bulk convert into .ini data, allows relative addressing on check and wildcards; (works through piping directory listing to file and running a regex over it).
.\dev\permissions.bat that Windows tool that may at some point have value. We'd need users to know that. (I have an update of it I'll include in my next)
My feeling is that, unless you actually use the test system, (including "P" and all "polly-test*.bat") can be removed.