diafero wrote: Oh, and what about Linux support? I won't be able to really use it otherwise as I have to test distros before distributing them
Edit: numbering corrected.
Ah, we're getting to that topic ahead of time. I wanted to start discussing "the future".
Presently the scripts are VBscript and use Windows-dependent resources. This choice was made because, since the game is Windows-only, most of our users (Uru players) all must have some kind of Windows environment, even if it's a VM or Wine, and all WIndows users have the VB scripting engine.
For now, I'd say the easiest way for testing the scripts in Linux would be to use Wine or a Windows VM. I can make you a VM that you can use with the free VMWare viewer.
I was planning to release version 1 in VBscript, let beta-testers go at it for a while, and then make a decision about version 2.
There are several possibilities for the future:
1- Stay in VBscript
pros: it works, nothing to install for users, low maintenance
cons: works only on Windows
2- Translate into Python
pros: true programming language, works on all platforms
cons: lots of work and testing again, users must install Python, and I'd have to learn Python.
3- Translate into C++ and turn it into a libPlasma tool using the libPlasma library instead of other libPlasma tools.
pros: true programming language, works on all platforms
cons: lots of work and testing again, users must install libraries, and I'd have to learn C++ again
4- Translate into Java and integrate into Drizzle
pros: simplest for users, takes care of both distribution and installing, most viable solution, works on all platforms
cons: lots of work and testing again, for me and for Dustin. Drizzle gets bloated. Have to basically re-code libPlasma into java. I'd have to learn Java (bleh)