Trex Tester

Hello Trex
      <%systemstyles%>
      Hello From Trex
      I wanted to see if I could get it working in a few minutes, and it turns out that yes, as long as there wasn't any walking needed, I could get it done right off. Tomorrow morning I'm going to write a simple new walk routine.
        function isAlpha (ch)
          return (((ch >= 'a') && (ch <= 'z')) || ((ch >= 'A') && (ch <= 'Z')))
        function isNumeric (ch)
          return ((ch >= '0') && (ch <= '9'))
        function random (lower, upper)
          var range = upper - lower + 1
          return (Math.floor ((Math.random () * range) + lower))
        function getRandomPassword (ctchars)
          var s= "", ch;
          while (s.length < ctchars)
            ch = String.fromCharCode (random (33, 122));
            if (isAlpha (ch) || isNumeric (ch))
              s += ch
          return (s.toLowerCase ())
        for (var i = 0; i < 100; i++)
          document.write (getRandomPassword (8) + ", ")
My site
  Nice page 1
    contents of Nice page 1
  Nice page 2
    contents of Nice page 2
  subway
    Nice page 3
      contents of Nice page 3
  Nice page 4
    contents of Nice page 4
  content-type test
    function testing () {
      alert ("This is a test.");
      }
This is a test
This is a test
What is trex.root
  It's a Frontier tool that is primarily a web server responder.
    http://frontier.userland.com/stories/storyReader$1028
  On each request that comes into Denver, it checks to see if it's one of the domains it's hijacking. If so, it serves it.
    Those domains are in config.trex.prefs.domains.
    They are domains that would normally be served by worldoutline.root
  Nodes are all html type
    They are all assumed to be of nodetype HTML. If they are not, we call that an error. That's the only type we handle. (Need to verify this.)
  There is very little processing done on this content
    The text is generated by calling html.directory.getRawHtml.
    Then it's run through a table of system macros. Right now there's only one such macro, systemstyles, but it would be very easy to add more.
      Core routine here is string.tableReplace. That must be available on whatever machine this running on.
    Then it processes macros that are implemented in scripts.
      The scripts it handles are in worldOutlineSuite.macros.
      But only a very small number of these are used.
      They usually involve outlines. It's the way we include text from other outlines. With various interpretations.
      However, this is not open-ended. We only call a few of them.
    Then we look for the Content-Type attribute, and use it as the content-type header for the HTTP request.
  About this doc
    It is being edited in Concord but it is not being served by trex.root.
    All part of a bootstrap! :-)
getCanonicalName ("Hello From Hollywood")
  helloFromHollywood
Another test
  Yo yo
I am now going to try to undo something
  I have entered a headline
  The next headline will disappear
What is trex.root
  It's a Frontier tool that is primarily a web server responder.
    http://frontier.userland.com/stories/storyReader$1028
  On each request that comes into Denver, it checks to see if it's one of the domains it's hijacking. If so, it serves it.
    Those domains are in config.trex.prefs.domains.
    They are domains that would normally be served by worldoutline.root
  Nodes are all html type
    They are all assumed to be of nodetype HTML. If they are not, we call that an error. That's the only type we handle. (Need to verify this.)
  There is very little processing done on this content
    The text is generated by calling html.directory.getRawHtml.
    Then it's run through a table of system macros. Right now there's only one such macro, systemstyles, but it would be very easy to add more.
      Core routine here is string.tableReplace. That must be available on whatever machine this running on.
    Then it processes macros that are implemented in scripts.
      The scripts it handles are in worldOutlineSuite.macros.
      But only a very small number of these are used.
      They usually involve outlines. It's the way we include text from other outlines. With various interpretations.
      However, this is not open-ended. We only call a few of them.
    Then we look for the Content-Type attribute, and use it as the content-type header for the HTTP request.
  About this doc
    It is being edited in Concord but it is not being served by trex.root.
    All part of a bootstrap! :-)