Nick wrote:
"It was a design decision, not an implementation flaw, that it works the way it does."
I didn't mean to imply that I felt your software was flawed.
It was just a thing I think would be cool, that I felt fit
in the suggestions topic.
Nick wrote:
"There are some nice programs around (I use PuTTY) that handle character mode just fine, including support for colour, UTF-8 and so on."
Indeed, but the MUSHclient UI and other features like triggers
and such make MUSHclient-with-charmode a superior choice over
those other options.
Nick wrote:
"The extra things MUSHclient gives you, like saving your previous command, or logging lines, won't really work if you don't have lines in the first place. For example, how could it save a previous command if you type something, hit tab, and the server completes the line for you? MUSHclient wouldn't know the completed command."
Forgive me if I sound argumentative, that is not my intent, but
in my opinion this is not sufficient deterrent. An optional
character mode would not be helpless to record how the server
responds to a tab, for example, and append it as the completed
command. Naturally, recording the history of a cursor crawling
around a fullscreen editor is "out of scope" of anything reasonably
expected of a mud client these days, but the rest of it doesn't
seem awfully challenging if the client is able to recognize
"sent return", "sent tab", and identify received characters.
Nick wrote:
"Anyway, you don't have to convince me - the source code is available, and anyone that wants to can make the appropriate changes if they feel like it."
I understand if you don't feel like it...*that* is certainly
sufficient deterrent :)
-Crat
http://dead-souls.net
|