Zugg Software :: View topic

Posted: Sun Aug 26, 2007 3:28 am

In the new stormfront mode on GS4 i am not getting any of the XML tags at all now.

Posted: Sun Aug 26, 2007 3:30 am

v2.01 still sends the PLAY command and not the STORM command at login time. Sorry I forgot to fix that, but I'll put it in the next update early next week, unless there is another quick fix this weekend.

However, if it worked in 1.34 then it should still work in 2.01. I haven't changed the login sequence for Simutronics at all. All I did was add the StormFront option to the GSL dropdown selection.

Posted: Sun Aug 26, 2007 3:31 am

Oh, I should mention that it's also possible CMUD is seeing the StormFront tags, but you are not.

v2.01 supports the <tag/> format used in StormFront, and CMUD normally ignores unknown tags. You might try turning on the MXP debug mode to see the tags. In v2.01 you should be able to write MXP Triggers to fire on all of the tags now.

Wizard Joined: 14 Aug 2004 Posts: 1269

Posted: Sun Aug 26, 2007 5:30 pm

What I mean is that it treats the tags just like any other HTML/XHTML tag that isn't supported in CMUD. For example, imagine handling the text

<NewTag>Text</NewTag>

The way this should be handled by any web browser is that it should display the "Text" but not the actual tags. CMUD works just like a web browser for this...it shows Text but not the tags.

OK, now consider the text:

<NewTag>Text

What should it do now? Should CMUD display the <NewTag>? Even though there isn't yet a </NewTag> closing tag, how do we know whether or not this is a multiline tag, like <P>paragraph</P> in HTML? Unlike a web browser, CMUD doesn't have the entire "page" to parse...it just has a partial page as the text is received from the MUD. This is the issue with "scrolling HTML" support.

The way CMUD (and zMUD) have always handled this is to look at whether the MUD has put us into MXP Secure mode or not. In MXP Secure mode, CMUD assumes the MUD knows what it is doing and properly supports MXP. When a MUD properly supports MXP, then it should be sending

<not-a-tag>text

if it wants CMUD to explicitly display the < and > characters. In Secure mode, CMUD assumes that the MUD will eventually send the </newtag> closing tag, so the tag is stripped.

So, in MXP secure mode, any unknown tags are stripped (and cause MXP triggers to fire), but the text should be displayed normally. So CMUD should be gagging anything that looks like an open or closing tag, but not the text between them.

Wizard Joined: 14 Aug 2004 Posts: 1269

We're getting a bit off-topic, so moving this conversation to a more appropriate thread...