Refactoring of the PORTABLE mode?

[lars18th]

Hi @cyd01 ,

Even KiTTY is the best PuTTY fork even created, the effort to maintain it's huge. So perhaps, it's time to do some joint-effort to "encapsulte" the changes in modules.

For example, the PORTABLE mode could be managed with a simple transparent registry storage. And some other PuTTY forks are maintaining this. For example this one: http://jakub.kotrla.net/putty/ The maintainer of it shares (for every new PuTTY release) the modified winpgnt.c and winstore.c files. So, if you encapsulte this as a "patch", then you don't need to worry about changes on every new PuTTY releases. When the "new" patch will be available you only need to incorporate it.

For other changes, perhaps it will also possible to encapsalute them in different modules. Then each module can be maintained in a different branch. And then the KiTTY project will be a list of multiple joins of theses branches. The objective is to provide a more small group of changes for every additional functionality, each on his branch. This will make more affordable the developing the changes. As only one branch with a specific functionality requires to be tested.

What you think about this?