Well, Xmas is quickly approaching and I thought well what
better time to tell EP, err, Santa I mean rather about my TWX Wish List! As
well if anybody else has any idea’s please feel free to post them here

1.  I wish
that there were two more commands one similar to waitFor and another
similar to waitOn; though function as setTextLineTrigger, except
maintaining the ease and convenience of use as waitFor and waitOn.
2.  wish
that there were a setTextTrigger and setTextLineTrigger command that
functioned like a goSub routine, you set the trigger it activates runs
through a sub and then returns and continues just under the trigger wait.
3.  I wish
there were a command to active the triggers to meet the “pause”
requirement, without having to mock the pause to activate the triggers.

4.  I wish
the popup windows worked better and included more options to use them,
i.e. interactive radio, select, and forum boxes, allow windows to be
reopened after closed out if user defined (enable/disable) setting is
activated or not, allowing spacing in the window header, font styling,
more controlled text formatting, etc.


Disclaimer: This List may be freely added to or modified at any time,
before, during, or after this current Xmas and/or any future (or for that
matter past) Xmas.  If you happen to be offended by the word Xmas, then my deep apologies, as i am truly sorry that sometime during your upbringing you were somehow turned into a wannabe communist fascist two tailed neophyte-sperm socialist!

I'd like to ask santa for a waitfor/waiton cmd with a parameter to time-out or branch upon timing out. ie:

waiton "(?=" :gohere 2000


Oh. And before I forget.. I'd like to throw in:

setTextLineANSITrigger Woot :Woot #27 & "[1;36m<Computer deactivated>"
pause
:Woot
echo "**" & ANSI_14 & "NOW! I can reset my IG**"
send " b y "

Yea an ANSI trigger, well I did forget about that one, that is a really good one, SPOOF=kthxbye!

Hehe, you guys... you are funny guys.

TWX 2.04Final is coming along nicely. It would be coming along faster if RiverRat and Kaus would just concede rev's solo and admit my win

I am planning a New Year's update on or around Jan 1. But it will be bug fixes and only minor enhancements. But who knows... any really good ideas *might* warrant implementation... so let's hear what else you've got.

Um, to be really worth considering, your idea needs to be something that either can't be accomplished with the current TWX, or can't be accomplished easily. I add this because some of the feature requests I see are possible now, but require 2 or 3 lines of code instead of 1. These requests aren't likely to make the cut

Would it be helpful to address some of these requests that don't make the cut with advice on accomplishing the same result with currently available commands?
... like LoneStars 1st request:

setDelayTrigger timeout :timeout 20000
waitOn "(?="
...
:timeout
killTrigger waitOn1
goto :gohere

Few people know that you can kill a waitOn, so examples like this may be just as helpful as implementing some of these ideas.

+EP+

At the University, I have taken courses in 3 programming languages. They were always fairly simple to pick up. The only thing missing from TWX from a 'learning it' stand point is a set of lessons for specific scripting tasks that use every increasing feature/structure complexity.

Any chance of a "Learning TWX in 20 lessons" tutorial? Each lesson with a scripting assignment and a description of the syntax and usaged needed to complete the assignment.

C

He has been teaching TWX to others, just been onhiatus, some of us have had to wait till R/L things let the classes restart. Hopefully they will.

From the little programming that I do.. an duse to do in VB.. I'd like to toss into the Ring a couple string parsing functions (Visiual Basic Vernacular):
Left(String, Length)
Right(String, Length)
..perhaps the TWX equiv could be:
Left $Source $Dest $Length

Lone

Edit:  For completeness, a silly example...
setVar $String "World Hello!"
getLength $String $len
setVar $idx 1
while ($idx <= $len)
Left $String $Str $idx
Right $Str $Str 1
echo $Str
add $idx 1
end

left() already exists in terms of cuttext, right() is just a charflipped left(), which wouldn't be hard to write at all.

The ansi trigger would have it's uses but more useful, IMO, would be a setConstant command. You could setConstant FIGHITANSI as the code for fighit and just compare.

A timeout would be helpful, mostly because it's good practice to have a timeout and doing a timeout for every single important waitFor/waitOn is a bulky workaround.

I would like to see a getInput NUMBER restriction. Every time I get numbers in a menu (which is every menu I write, more or less) I need to check that it's a number and take appropriate actions if it isn't. Be nice if I had some way of controlling the acceptable input chars so I could simply limit that before they type it. Maybe an alternate way of doing that would be to specify $ACCEPTEDCHARS and $LENGTH instead.

But all of that is fairly trivial and yea, can be done the long way. For real features that would be exceptionally cool, a getDistance and getCourse that handles avoids. A built in BFS w/ accessible arrays. A way to spit out menu output and internal menu stuff (like bubbles) to a file or array for later processing.

Hmm...

I only have two thing for TWX:

Stop crashing upon exit.

Store the port number for "listening" based on the game being played and established at setup.

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

Agreed ; ) Would be nice.

I know he has but I meant a a set of lessons and scripting assignments written down. Even if they were just posted on here, one lesson at a time. They would then be available all.

Think about how it would affect the new users of TWX if they could come to a forum here and just start with Lesson 1, and work through the whole thing at their own speed just like any other computer language learning experience.

Imagine if the assignments for the lessons resulted in a set of basic scripts that the new user could use while playing? Finish the 20 lessons in the forums and have a set of basics scripts available for game play.

I, for one, would be willing to do whatever it takes to help get a project like that started.

C

Problem is lessons like that are hard to teach in text. You have to make it presentation format... which is why the lessons, to date, have been via conference (Skype) so EP could answer questions when they come up.

You are talking about 'lectures' not 'lessons and scripting assignments'. Any questions about the lessons could be answered by anyone with the knowledge on the forums. I am not saying its not a hard project, I am saying that if you want to help ANY newbie learn to script in TWX, then this would be helpful. Why should every new person have to re-invent the wheel?

C

Your first assignment to test in a game could be to send a text string to the server as fast as possible - maybe "C B Y" for instance. Helps when someone photons you with over 20k moves.

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

What? So now this becomes smack talk? I expected better of you in this forum

C