Well, I don't know, but this definitely rings bells with me coming from a Windows NT drag-and-drop background to Perl and Unix culture.

I think that the drag and drop metaphor works really well for some things: and ad hoc copying files is still one of them. But nowadays apart from some copying, directory browsing, and deleting directories (because I can never remember the *^$%! command to delete a directory tree but Explorer lets me do it with a couple of clicks!) I tend to use command line instead.

My point? Oh yes, that I think that running executable content might be something that's best left out of the drag-and-drop metaphor. What if you click on the wrong files? What if you drag them onto the wrong icon? (That Click, hold, drag, release sequence is intuitive but I get it wrong surprisingly often... - well, maybe that's just me) Do you need control over which order the scripts run? or what happens to the output or error messages?

If you are running a group of scripts that you run regularly you might be better off writing a .bat file to call them and pipe the output to a log file.

I think if you really wanted drag-and-drop execution, it might be worth looking into Windows Scripting Host (which supports Perl) as I think this does allow more control over order, logging etc.

Cheerio!
Osfameron