Hector, I been thinking how about some type of utility that will processall
files in wc5 including subdirs and print out a list of files that are not stock files? Perhaps even version analysis were possible to help preventand
eliminate potential problems? With current version we are not able toplace
*wcx files in their own directories so the root of wc5 has becomecluttered
with useless and potentially problem causing *wcx's. Perhaps a cleanup utility of some sort would go a LONG way in helping to organize the mess.
Are custom paths for wcx's in the near future?
I think it would be useful to provide custom paths for things such as:files;
+ Logs (activity.*, *.log)
+ WCX (*.wcx)
The following suggestion would require sysops to rewrite/modify batch
however for those of us who would like to clean up our installationto
directory much easier, maybe offering a way to set these paths if we wish
use them for seperate directories; otherwise default them to the standard \wc5 directory.
+ Executables (*.exe, *.hlp, *.cnt, *.chm) put in \wc5\bin
+ Library Files (*.dll) put in \wc5\lib
I'm just used to having an application folder that really don't containmuch
of anything and all parts of a program are seperated into their component type directories (binary files in \bin, library files in \lib, etc);however
making such a change like this would potentially mean a largearchitectural
change to Wildcat! which isn't all too important at the moment based onsome
of the other things I'd like to see available (such as multi-web virtual domain support and other HTTP/1.1 compatible functionality).
But I'm sure that over time Hector's going to continue to move us in the right direction in order to keep Wildcat! on top :-)
|Riverside County, California
|15 (0 / 15)