MXP syntax is so similar to HTML, why not go the extra one-tenth of a mile and add Pueblo HTML parsing? It's just scanning for the "Pueblo enhanced" line, sending "PUEBLOCLIENT", seeking out xch_mudtext, and then parsing everything outside of xch_mudtext tags almost the same way as MXP. Pueblo is an inferior client, but so many M*s are enhanced to use it, and you've already practically got a whole HTML parser. Just some food for thought.
MXP and Pueblo HTML
Posted by Fwongo on Mon 18 Jun 2001 05:19 PM — 4 posts, 20,468 views.
I must admit that it hadn't occurred to me, but you are probably right. :)
I'll try it out today with PennMUSH, and if I can make it work - I'll put it in.
Mind you, I don't intend to support every last bit of Pueblo (such as font changes, inline bitmaps and so on), but insofar as it can be done easily, I'll see what I can do.
I'll try it out today with PennMUSH, and if I can make it work - I'll put it in.
Mind you, I don't intend to support every last bit of Pueblo (such as font changes, inline bitmaps and so on), but insofar as it can be done easily, I'll see what I can do.
Quote:
MXP syntax is so similar to HTML, why not go the extra one-tenth of a mile and add Pueblo HTML parsing?
MXP syntax is so similar to HTML, why not go the extra one-tenth of a mile and add Pueblo HTML parsing?
OK - I've done that in version 3.11. Still testing it but it should be released soon.
I've tested it on PennMUSH and it looks quite good.
If you know of a particular MUSH/MUCK/whatever that you would like to see it work on, tell me the address so I can make sure there aren't too many surprises. :)
If you could check out how it works on Elendor MUSH (elendor.sbs.nau.edu: 1893), it'd be nice. Elendor is supposed to make quite a lot of use of Pueblo, and it'd be interesting to see how the way it uses it works with MUSHclient (especially since I am not sure whether all of the usage is standard, since Elendor is a heavily modified Penn).