Again, I am offering to solve this problem; to write something that could possibly create standalone patches from Impulse updates... but I haven't had a single response...
mdst8_wp
I really could probably just write something that turns Impulse updates into standalone patches...
Any developers have thoughts on what I said at the top of page 11?
Oh, it certainly can be more tedious than an automated system, depending on the perspective of the user (since you have to manage things manually, instead of simply clicking "Update"). But "powerusers" tend to like the control, and the lack of yet another program piled onto their computer. Update standalones can simply be backed up.
Well one common methodology is to simply release successive updates that only update from the second latest version. So you'd have to run 1.00->1.01, 1.01->1.02, etc. Nowhere near as tedious as it sounds, and easy to do. Could always release one that patches from 1.00 to latest, and from second latest to the current latest.
Confused as to what it is that makes developing the standalone patches difficult. Couldn't you, at the least, simply tar up all the data files and executables for the old version and the new, and simply provide us with a list of what was tarred, and the .diff file? Along with other files that may have been added, of course. It really shouldn't be too complicated I'd think. If there's something I'm overlooking, please let me know. If this is for some kind of we