41
I'm currently working on a module that allows one to track song submissions of members. It's fairly specialized, and I don't really intend the module for anything by my site. But, I would be releasing the module (and the source -- GPL) to the XOOPS community for others to hack with.
How here's the situation. Since it's much easier for me to work with minimal files for the time being and not having to worry about doing cross-platform & cross-language aspects of the module, I'm coding that way -- for now. The reality is that once I get the module functional, I intend to go back and clean up some of these things: Moving some of the instruction blocks to the language file, directory separator place holders, and so on.
My question is actually a very simple one to answer. I realize that this might be a somewhat backwards approach. But it's one that makes life less crazy for me. Supposing I finish the module and it's fully functional but requires Linux (or Unix based OS) and English, should I release it at that point? Or would you rather I wait until it's all sorts of cross-platform and cross-language (except that I won't do the translation) compliant?
How here's the situation. Since it's much easier for me to work with minimal files for the time being and not having to worry about doing cross-platform & cross-language aspects of the module, I'm coding that way -- for now. The reality is that once I get the module functional, I intend to go back and clean up some of these things: Moving some of the instruction blocks to the language file, directory separator place holders, and so on.
My question is actually a very simple one to answer. I realize that this might be a somewhat backwards approach. But it's one that makes life less crazy for me. Supposing I finish the module and it's fully functional but requires Linux (or Unix based OS) and English, should I release it at that point? Or would you rather I wait until it's all sorts of cross-platform and cross-language (except that I won't do the translation) compliant?
