|
blkno1 Novice
Joined: 26 May 2002 Posts: 30 Location: USA
|
Posted: Wed Mar 31, 2004 12:57 am
Best way to.....? |
Just curious as to how you all (personally) go about makeing a trigger or scripting in general? Do you do it from the commandline? Or do you use the settings editor? Is one way easier?
-jim |
|
|
|
DeathShadow Adept
Joined: 11 Nov 2000 Posts: 228 Location: USA
|
Posted: Wed Mar 31, 2004 1:53 am |
I use the settings editor 99% of the time. I like to use the syntax checker. Also easier to put the settings in a class folder from the settings editor.
|
|
|
|
Vijilante SubAdmin
Joined: 18 Nov 2001 Posts: 5182
|
Posted: Wed Mar 31, 2004 4:14 am |
I use the Settings Editor continuously, even to build more complex scripts for answers to people's questions here. It is just too easy to end up missing a }, ), or " when working with the command line format. Once it goes missing it is often even harder to find when using the command line format instead of the editor.
|
|
|
|
Kjata GURU
Joined: 10 Oct 2000 Posts: 4379 Location: USA
|
Posted: Wed Mar 31, 2004 6:29 pm |
Heh, I'm most likely in the minority, but I usually create a script right here in the forum along with the color codes. Once I'm finished and want to test it, I copy it from the forum post and paste it into the Command Line. Then, I fix any bugs with the Settings Editor.
If it's a script that I'm writing for me, then I usually use the Settings Editor from the start. |
|
|
|
LightBulb MASTER
Joined: 28 Nov 2000 Posts: 4817 Location: USA
|
Posted: Wed Mar 31, 2004 7:13 pm |
It sounds like I'm really in the minority. If I'm writing scripts for myself, I usually use the command line for triggers, aliases, variables, and macros. I use the Settings Editor for buttons and directions, and sometimes for editing/troubleshooting existing settings. I'll also occasionally use the Settings Editor for long, involved triggers or aliases with lots of subscripts (IFs and LOOPs).
When doing scripts for others, I usually create scripts right here in the forum and then paste it to the command line for testing. Unless I experience problems, I frequently don't even look at the Settings Editor. I usually don't add forum codes until I've finished any testing I want to do, but once I've added them I use the Preview window to copy what I have in the forum.
Personally, I find the command line easier for most settings. The Value portion of settings uses the same syntax as the command line, so it doesn't actually require learning anything extra, and the command line won't tell me I have a syntax error when I do something legitimate but unexpected (which I somehow manage fairly often). Multi-line scripts can be created directly at the command line using CTRL-ENTER. |
|
|
|
Hibio Beginner
Joined: 19 Mar 2004 Posts: 22
|
Posted: Wed Mar 31, 2004 8:08 pm |
I use the editor since I have so many trigs/variables/classes, I rather just click on the class to create something new instead of having to type our and remember all the classes/trigs/variables when i can seem most of them
Beside, at times some trigs/aliases/scripts simply involve the usage of {} and () too often, better to have the editor that can check for you.. like emac vs. vi on this account.. |
|
|
|
|
|