[DeepIron]

swdw, I think one issue you might run across is 'versioning'... If the project stays a moving target for any length of time, which is likely considering it's nature, and unless you were releasing major 'milestone' releases, I'm not sure how you'd manage content. Changing single modules in the project shouldn't necessitate downloading the whole enchilada...

I think packaging the "final" or major releases into self-installing .zips or .exes would be beneficial as an end product, but I would advise using holding off until then. The other issue, as you point out, is cluttering the registry with entries, many of which would remain after an un-install. I use a Registry cleaner after every program un-install and it always finds entries left behind.

Another option is use a versioning system, and track individual "modules". I've used CVS and SVN on projects in the past to great success but that process might be total overkill for RFB...

Ok, just thinking out loud here... I assume you have web storage or access to a public server somewhere? Perhaps organizing the project into folders representing each "module" and the getting a thread stickied at the top would suffice. You could announce any version changes to individual modules in the thread (similar to what Excalibur Bane is doing), but keep the link pointing to only one file name. This way, you only have to upload the changed files and not change the filename constantly. Not perfect, but an idea...

Once the project is debugged sufficiently, making a .zip or .exe would be cool...