|Pathologically Eclectic Rubbish Lister|
Some pre-project questionsby Moron (Curate)
|on Feb 22, 2007 at 16:02 UTC||Need Help??|
Moron has asked for the
wisdom of the Perl Monks concerning the following question:
Hi, I am about to start a Perl project which raises a couple of questions beyond my experience.
The first is, suppose the main Perl functionality occurs on a (unix) server, but the servers could be inaccessible for practical purposes except via Windows boxes. So I need to have a Windows client that enables non-expert users to make configuration changes and browse the systems data on the server side. My nearest competitor uses a Java client for this purpose. It is unlikely I can use an intranet approach because some customers may not allow a webserver to run on the target machine. What is the best Perl way of creating a Windows GUI client for a Unix server? Can Perl/Tk be made pretty enough to compete with Java?
The second is, the end-product has to be sold rather than given away. Does that mean I can't publish ANY of it on CPAN? Does it mean I have to use PAR? Is there a way I could package the client and server software onto a single iso-disk with the intention being that the Windows installation process does the installation ALSO on the unix server?
Thanks in advance!
Free your mind