On Sunday 09 December 2001 12:47, you wrote: > I wasn't aware of this. We're not supposed to be mixing tabs and > spaces at all. I'll run checksrc.py soon and at least fix that.
BTW, I've started working on a little command line tool, called "/usr/bin/webware" for the time-being, that will give component writers a single interface for common tasks such as: * list all installed components and their summary information "webware list-components" * setting up a skeleton component structure that follows the Webware component conventions. They create a properties file, pass it to the script and it will do the rest for them. "webware skeleton <properties file>" from a directory you want to turn into a component package. * checking their code to make sure that it follows the Webware guidelines. "webware checksrc Cheetah" * switching between tabs and spaces where necessary. "webware tabclean [options] UserKit" * gives some statistics about code coverage (lines of code, # of classes, # of tests, @@ comments, etc.) "webware coverage [options] PSP" * will locate and run all the unit and functional tests in a Webware component, or the entire suite. "webware test" --> run all UnitTests and FunctionalTests for all components "webware test MiddleKit" --> just for MiddleKit "webware test MiddleKit.UnitTests" "webware test MiddleKit.FunctionalTests" "webware test WebKit.FunctionalTests" ----- Do you think such a tool would be worthwhile? Each command would be implemented as separate class that parses its own options and args, etc. The main script would just dispatch the commands. Tavis _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
