Nice work.
Want a challenge? Maybe a 'super' SlimTray. Here are some ideas:
- Use an INI file for SlimTray configuration so that things like the
service name aren't hardcoded into SlimTray itself. This would be
transparent to most users, as you could still use hardcoded names in
the absence of an INI file, or else just provide an INI containing
the default names.
- Permit the control of multiple instances of SlimServer. The INI
file would need a service name, IP address or host name, HTTP port,
and perhaps a friendly name for each server instance.
- Allow the use of a non-default web browser to open the web page for
the web ui. I guess you'd do this by entering the path to the browser
EXE in the INI instead of opening a URL shortcut which will always use
the default browser.
- For convenience in restarting a SlimServer instance, add a service
'Restart' control, as in the Windows Services applet.
- Best of all would be the ability to run SlimTray on a remote
Windows machine to control the service(s) running on a separate
Windows server. I run SlimServer on a dedicated headless Windows
server, so by the time I connect to the server using Terminal
Services, using SlimTray to control the server provides little
convenience. What I could really use is a SlimTray running on my
everyday desktop machine to stop and start the services on the
server.
--
JJZolx
Jim
------------------------------------------------------------------------
JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10
View this thread: http://forums.slimdevices.com/showthread.php?t=32257
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
