We keep finding demand for modules that transfer a batch file to or from a remote location. Rather than create redundant code, we thought it would be a good idea to create a sharable module for handling file transfer mechanisms. But we only got as far as a little bit of helper code before we realized that we would have to code the config fields into each "user module" (what we call the modules that use the FileTransfer module). There're multiplying points-of-failure there because each config field that has to be created can be different from the others.
What we really need is a way consistently to generate the needed admin config fields.
- Generating actual XML seems like the wrong thing to do.
- In our team we discussed creating custom frontend_models in the FileTransfer module, and that's the direction we're headed in now, but that will require us to manually code all the widgets and everything for the frontend and handle the POST specially in the backend. All of that seems unnecessary since we're just trying to duplicate procedures that Magento does anyway.
What we want is to guarantee config consistency across any module that uses a component of the FileTransfer module. Any suggestions?