Web client first cut

[Don Brown]

I completed the first cut at the twx bbs web site and client. As you
can see in the updated spec:
http://code.google.com/p/twxproxy-ep/wiki/TWXBBSSpecification

the telnet app sits in the middle, augmented by the surrounding web
page. I also have the applet <-> web page communication bit working
so that the web page can be notified for HIPS messages and vice versa.
In this first cut, the current sector, as parsed from the command
line, is sent from TWX Proxy -> Java Telnet app -> HTML status panel.
Since the Java bit is only the center telnet app, the rest is built
using plain HTML, CSS, and JavaScript, making it very easy to
customize even for each player.

You'll notice at the top there are the buttons that execute scripts.
I'm thinking I'll add incoming HIPS support to TWX Proxy, then with
the namespace "twxproxy", allow direct script execution commands like:

twxproxy.runScript={
"name":"1_Port.ts",
"dest":444,
"runs":20
}

Of course, that will mean the scripts will have to be able to accept
named arguments directly, so we'll see how that'll work. The fallback
is to just script the key strokes, but I'd like to avoid that as the
direct approach is cleaner and more flexible.

Don

[EP]

For our immediate purposes, the scripts could be modified to grab
their starting values using loadVar. The loadVar reads directly from
the [Variables] section of the database's .cfg file, so this could be
a simple fix for now.

In your above example, the runScript procedure could first write
$dest=444 and $runs=20 to the cfg file, then launch the modified
1_Port.ts script.


Still, enabling script argument support would scale better.


+EP+

[Don Brown]

Hmm...that would work, since we will be limiting one player to a
twxproxy instance. I have the web client now connected correctly to
the front-end proxy, so adding in embedded twxproxy is the next step.

Don

[Don Brown]

I should add, for anyone that wants to give it a go in the next few
days, my development instance should be mostly available for testing:

http://www.twdata.org:8080

Choose game A, and the username and password is "bob".

At this point, the applet is connecting to the front-end proxy, but
that proxy isn't embedding twxproxy yet, so all connections share the
same twxproxy instance.

Don