No, the actual interface isn't just a button. :) If that were the case I'd agree that it wouldn't be worth the trouble. In general I'd rather just run things from the command line which is why this is only my 2nd attempt at using perl/tk. :)

In the actual script none of the data is hard coded. All the input gets put into the interface (text boxes, drop downs etc) and then that data is processed and used to populate the hashes/html table/etc.

None of that extra stuff was a major contributor to the speed problem however, so I kept the perl/tk stuff as simple as possible in my example.

If the speed is all just overhead and there's nothing for it than I'll have to start looking at other options. The problem seems to be output related more than anything. It's strange, but I've noticed that if I write the output to a plain text file and just open it with notepad it does seem a bit faster. I may have to settle with that, but I'd lose a lot in the formatting/spacing department.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.