There's a PerlTray sample in the ActiveState Perl Dev Kit 5.0 that pulls the current threat level from the Homeland Security webpage. Cute, but Windows only though...
I've not used perl2exe, but have used PerlApp in the Perl Dev Kit by ActiveState. It has worked very well for my needs: the client I currently work for installs perl on every machine, but it is the original pre-activestate version bundled in the NT Resource Kit. I need to use a more modern version for something, but they wouldn't agree to upgrade. Hence PerlApp.
Ideally, I would upgrade all the machines, and have a shared site library for additional modules, but if until then, or for sites where you can't rely on perl being everywhere, PerlApp and perl2exe do a good job...
Vi(m) can be used on Windows - I use it all the time.
Vim can be used as the editor in Visual Studio.
Fedora Core supports this - you can install via VNC. you can set a password, and you can configure it to connect to a listening VNC Viewer.
You only need the monitor to kick off the install and configure your NIC.
Have a look in the release notes, about a quarter of the way down.
Cheers,
There's a PerlTray sample in the ActiveState Perl Dev Kit 5.0 that pulls the current threat level from the Homeland Security webpage. Cute, but Windows only though...
That's the wrong model (the SL-5500).
I've not used perl2exe, but have used PerlApp in the Perl Dev Kit by ActiveState. It has worked very well for my needs: the client I currently work for installs perl on every machine, but it is the original pre-activestate version bundled in the NT Resource Kit. I need to use a more modern version for something, but they wouldn't agree to upgrade. Hence PerlApp.
Ideally, I would upgrade all the machines, and have a shared site library for additional modules, but if until then, or for sites where you can't rely on perl being everywhere, PerlApp and perl2exe do a good job...
...The UK has known about the delay for ages now. It was ;an nounced at the beginning of August...