VBS is a good thing to start with. That's Visual Basic Scripting, not for Applications, which is VBA.
VBS Doesn´t need a compiler, just the standard Wscript interpreter, which is already installed by default.
My code routine started at Python, HTML and SQL. For a Lineage2 Java-based server. The Python files are uncompiled script, so they are readable and easy to edit. The compiling is done by the Java server when the server is starting. It's placing a .Py_ file in the same directory, which makes it readable for Java to work with.
Python is not very hard, it's easy to learn. All it takes is logical thinking.
When I started VBS, I really HAD to learn it, because I wanted to create a program that can add a key to the registry which I can type at the Run... Dialog and then windows will start the path I gave to the name. These keys are stored at:
The script worked and since then I made another 10 handy scripts. My next project is a word-game.
You should start from the beginning, which is VBS.
Then when you understand that and think you know enough (which will litterally take about 3 months.) you should try understanding Python. Well, if you understand VBS at that time, Python looks very familiar.
The hard thing about Python is finding the inspiration to do something with it. I had a good push in the back, which was creating complex bugless scripts so Lineage2 players in my server could easily and safely exchange cash for fun stuff, like HUGE shields.
After Python, VBA looks like a logical step, it's got a bit more complex code than Python and it's a lot more complex than VBS.
If you think you know VBA, try doing some basics with a C# language.
Personally, I think Java is really hard. All my personal Java codings failed.
But I've seen people which can just listen to you and from that script your idea for you.
My tip for you if you want to learn Java: Don't lose interest.
If you don't know how to code something like that, think logical.
There are a lot of ways to code something.
Like just a message on the screen can be coded in at least 5 different ways.
A tip just for VBS:
If you can't write into the registry, write a file and name it key.reg, then just let the script run regedit in silent mode and direct regedit to that file.
If you have some questions, you may add me to msn. My address is in my profile. I still need some more inspiration for VBS scripts and a possible partner in scripting.
===- End of post, sorry for keeping you reading this long
Edited by IO-error, 06 December 2006 - 03:38 AM.