wx is very cross-platform friendly, but I agree that it has a steeper learning curve. Not sure you can do much on any Win < 2K.
If the server is acting as a clearinghouse, i.e., the events are reported to it first, the GUI should not have any problems reporting them. If you are in a hurry, that's the first change I'd make: route the messages through a port on the server. Then the GUI becomes much simpler.
As far as elegance, either way you need to have a resident daemon/process queue with a known address to gather messages. Whether that's an adjunct to your existing server or another process, the function needs to be provided.
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.