I'm going to throw my vote in for Gtkperl as well. You can find a very nice tutorial for it
here.
I'm also going to vote against using HTML/web-browsers. I love HTML, but I think there is a limit
to stretching a technology into an area that it wasn't designed to handle. If you want to send a few sets of large data, HTML is great. If
you are sending many packets of small data (such as when you want an instant response to, oh, say, a volume change), HTML is horrible.
Of course, the best way to do it is to write your code into a module/API, and call it from a wrapper script. Thus you might
make Gtkperl your first interface, but it only takes a few lines in a CGI script to run it from HTML, and if the next guy to come along
decides that he likes your functionality, but hates the interface, he can rewrite it in Perl-Tk without starting over from scratch.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.