comment on

I'd like to second tachyon's suggestion of using a second program for the configuration and re-reading the config when the program wakes up. If you're trying to stay with the Windows way, the right place to store the settings is in the registry, probably under HKEY_LOCAL_COMPUTER\Software\YourCompany\YourApp\Settings.

Then you can change your service to use those settings, and write a separate Perl/Tk front-end program to change the settings (and control the service) without breaking the already-working code.

I think that adding HTTP::Daemon to the mix is more complicated than you need for a few parametes, unless of course you're already comfortable with it. The Widget demos in ActiveState should get you 75% of the way to a Tk-based settings screen.

Regarding changing the E-mail modules you are using, or switching to OO-style: If it ain't broke, don't fix it.

--
Spring: Forces, Coiled Again!

In reply to Re: converting a command-line program to one with a "pretty" interface by paulbort
in thread converting a command-line program to one with a "pretty" interface by punkish

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.


go ahead... be a heretic
	PerlMonks