months ago I did a toy project to explore one automation consept for our work environment. The idea is that we had an archaic tool that took a "batch" file and executed it. Problem was that no two jobs required the same batch files and manually editing those files was error prone. So, I created a Tk GUI to automate this process. In a zealous swing, I extended this tool to also execute that batch file on the hardware and parse the resulting output. As of right now, the program is over 2000 lines of code.
It didn't take management long to see the usefulness of this tool and the advantages it had over the original way. This of course, is great! However, as I stated earlier, this was just an exercise, and as such, new functionalities were added piece by piece to the already long program. I know that soon it will be decided to "productize" my tool for our customers, yet the program is just a fix-on-top-of-a-hack style. So I am asking for your guidance on how to better organize it.
I found one reference on PerlMonks to this question 62740, but it doesn't actually answer any questions. I think what I would like to do is break my program up into modules, but I can't seem to figure out how to do it cleanly. It is a GUI tool with added threads, socketted communication, and intra-tool communication links (bound tags) dynamically activated based on results, using plenty of global variables. Given this mess, can you recommend some reading to help me better transform the tool from its current version to a maintainable version. Thanks in advance.
In reply to reworking a large program by gri6507
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |