Re: 'Fake' input?
"Malachi Clark" <[email protected]> Thu, 25 Aug 2005 20:58:52 -0700 (PDT)
| Newsgroups | gmane.comp.games.mud.client.lyntin |
|---|---|
| Message-ID | <[email protected]> |
> On 8/25/05, Eugene <[email protected]> wrote: > >> On Wed, 24 Aug 2005 17:37:37 -0700 (PDT) >> "Malachi Clark" <[email protected]> wrote: >> >>> Is there a command (or similar) that will enable me to >>> "fake" input from the mud? <...> >>> If there isn't a command already, should I just use the >>> hooks to create my own? Just wanted to ask before I go off reinventing >>> the wheel. >> >> No, there is no such a thing. For me, it was always easier >> to run quick-and-dirt "server-like" script via netcat (on Linux) and >> connect to it with the client. YMMV. > > Such a command would be useful for another reason also - though > perhaps not so applicable to muds... I used to use lyntin for an IRC > client. On IRC, the server sends you a message when someone else says > something, but when you say something the server gives you no indication > that it happened. So, obviously, my #sub command which formats incoming > messages nicely isn't going to work when I talk - I have to make an alias > and stick in a #showme to format my messages nicely. But then this still > isn't great because my messages don't get #highlight'd (and I'm forced to > have "# " at the front of my format style to match #showme). So yeah, I > often thought about a simulate command but I never worked out how I'd > implement it. > > Isn't there a hook that we could use to simulate or "fake" data to lyntin in such a way that lyntin wouldn't be able to tell the difference between "real" mud data and "fake" mud data. It would be VERY helpful for testing to have a module like this. I would be happy to write it, if I could figure out where/how it needs to hook in. Malachi ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf