It seems to me that it is can be used to its full potential by someone familiar with what they are doing so that they don't need a shw file, but rather create them on their own from regular hacks due to the previous hacks dilemna. Some things you might have to modify for your particular code only. But as far as I can tell you couldn't really make a program that could work around that problem.
Simply put, each added hack you install becomes more and more dependant upon the previous hacks. The last one you install is the first one you uninstall (and vice-versa). Probably the best thing to do if you think you'll want a large group of hacks together is to make a giant shw file that combines those hacks into one. For network people, it's like having a bus topology; if one goes down each of the following ones go down too. Perhaps one route to take is some sort of thing that comments out the code that was taken out so if it is needed later it could be retreived. When I started doing hacks (about a week or two ago), I commented and documented every change I made, including those added to HTML sections. (I had to use a different commenting system as CGI/Perl comments don't work in HTML). I suppose that would start making scripts larger and less efficient, but the documentation is valuable. One main thing I've done so far is documenting in a separate file all the hacks I've installed and intend to install. I also rank 1-10 the difficulty experienced/estimated for installing the hack.
------------------
--DR3, Dragon Reborn the 3rd.
