Re: CF: Step #1 of Perl/Tk client

[krisb@ender.ring.org]

	The PERL client would be able to work on M$-Windows in a similar
way to a Tcl/Tk client.

	The two primary reasons for a PERL client:
1. (very!) Open Source.  People could patch it or add features quickly.
2. Automation, Automation, Automation!

	For example, imagine running a second character from the PERL
client, that did what you "told" it to do!

'tell jimmy north

Imagine the possibilities...

=)

-Kris

On Fri, 29 Jan 1999, Christian Stieber wrote:

> Hm...
> 
> it seems people are working on all sorts of weird clients. I know
> about a Java client, a tty-client, now a Perl client, and I'm
> pretty sure someone is working a C64 client or at least sn sh client.
> 
> However, the question I have is: is _anyone_ working on a client
> that will allow _more_ people to play crossfire? Such as a M$-Windows
> client or a MacO$ client? Wouldn't this be much more useful than a
> weird client collection? The Java client seems to be the only one
> that has the potential to serve as a client for people that don't
> have clients for their platform, but native clients are always better.
> 
> Christian
> 
> 
> -- 
> Christian Stieber        http://www.informatik.tu-muenchen.de/~stieber
> -
> [you can put yourself on the announcement list only or unsubscribe altogether
> by sending an email stating your wishes to crossfire-request@ifi.uio.no]
> 

-
[you can put yourself on the announcement list only or unsubscribe altogether
by sending an email stating your wishes to crossfire-request@ifi.uio.no]