staticxjam uses a test-driven approach. Try to write tests for every bug that you submit or fix and for any feature that you might add.
There are lots of things to do:
* make staticxjam to look at the timestamps of all the files and dependencies and determine if a new file needs to be build (like make). staticxjam already does check the timestamp on copytasks. * cache (save) the DOM for menu, header and copyright and not reload it for every file. * add command line options for every config file option * add something like "exclude extensions" to config file. Good default excluded extensions would be ~ and bak. * change the xml output mode and make a decent writer. * make some swing interface, count the files and make a nice progress bar.
This file was generated using xjam.
Many thanks to Patrick Riley (SIMS, U.C. Berkeley)
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
Thanks to sourceforge for the hosting.