interact.airmedia.org chat

[Karen Lewellen]

Hi there,
You know, I have always heard that it would take an entire re-write of 
the code for lynx the cat to have Java script or even Java enabled.  I am 
no programmer, but if i were I would do this as marketing it as a welcome 
alternative to some of the more  troublesome browsers would be  a breeze. 
many have heard of Lynx, although few keep up with its changes even into 
the ssl stages.  I would even help a programmer get paid to do  the work 
if I knew a programmer willing to do it.
In any case.


Actually you were a great help, as you have confirmed what we already 
know.  Webcrossing has in  been in the past several days re-working the 
chat client, it is not in place at air yet,  to remove  the Java setup and 
replace it with javascript.  we do know the difference, grin.  Given that 
my setup of both links and e-links  are on shellworld, and that even 
e-links here has trouble with javascript places, i needed to  be sure that 
it was not my setup having the conflict.
webcrossing has setup a Unix box running the freebds <misspelling> server with links to 
test their re-created  chat client.  I am told that actually both options 
are enabled, Java and Java script, but that the former is creating a 
conflict.
The last test option they sent me worked flawlessly with links  and it has 
only the javascript not the Java.
If you want to be complete in your research, I  can send you privately the 
link and password to this demo.  it is not on the air site.
Thanks again for confirming that it is not my setup.
Karen

On Fri, 7 Oct 2005, Lorenzo Taylor wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sorry for the thread, but I lost the previous message.
>
> OK.  I tried both links2 and elinks with interact.airmedia.org, ad we have a
> much bigger problem than I first thought.  The chat client used by this site is
> not using javascript.  It's a java applet.  There is a lot of confusion about
> this since the names java and javascript are quite similar.  Unfortunately for
> all of us, they are two entirely different things.  The major differences for
> the purpose of this topic is that links2 and elinks are somewhat capable of
> handling javascript.  Neither will even touch java.  So we are now down to three
> possible solutions:
>
> 1.  ditch the applet, which is the best way to go for accessibility, but is
> probably not something they can or will do.
> 2.  Create an IRC or Jabber gateway that will access the java-based chat client
> and allow users to connect to it through more accessible means, this is now the
> intermediately difficult solution, as I will discuss below.
> 3.  write an entirely new text-based browser or extend the capabilities of
> links2 or elinks to be able to run java applets.  This is harder than it looks,
> since it would require that a java virtual machine be installed on the system
> which would handle the java code itself.  The problem is that java applets are
> generally graphical in nature, and getting them to run on a text console would
> require not only a total rework of the browser, but also a total rework of the
> java virtual machine so that it could render the graphical interface using
> curses or some other text-based library.  I'm not saying this is impossible by
> any means, it's just far beyond the scope of my expertise, and by far the most
> difficult solution from a programming standpoint.
>
> Sorry I couldn't be of more help.
>
> Lorenzo
> - --
> Living your life is a task so difficult, it has never been attempted before.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
>
> iD8DBQFDRgyPG9IpekrhBfIRAicOAJ9ia94rb+v1RdTDAwG80zzrzN1VxgCgg5kD
> p4WzWNrjYqIMQoWuT7XkntI=
> =phi9
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>