<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I would vote against play_html5 as an option as the regexp isn't as easy to verify and if we update to html6 them what?<br><br>Pgogy Webstuff - <a href="http://www.pgogywebstuff.com">http://www.pgogywebstuff.com</a><div>Makers of web things of a fair to middling quality</div></div><div><br>On 12 Apr 2013, at 16:04, Tom Reijnders <<a href="mailto:reijnders@tor.nl">reijnders@tor.nl</a>> wrote:<br><br></div><blockquote type="cite"><div>
  
    <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
  
  
    Some questions, before I commit,<br>
    <br>
    1. Julian, do you already have a different name for 'site' or shall
    I commit site for the moment?<br>
    2. Do we have consensus over the engine name? html5? javascript?
    xenith?<br>
    <br>
    Now I have 'html5'  in the GUI, but 'javascript' in the code,
    because I think that is better w.r.t. flash.<br>
    <br>
    The major reason I ask is that if we want to create the
    play_html5_560 play_flash_560 (not sure that's a good idea, I prefer
    that people have to put in a bit more effort to choose an engine
    different than the author wanted, so play_560?engine=html5)<br>
    <br>
    Still even if we leave it at the engine=.... what will we call the
    engines? <br>
    <br>
    I prefer flash/javascript<br>
    <br>
    Tom<br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">Op 12-4-2013 16:48, Julian Tenney
      schreef:<br>
    </div>
    <blockquote cite="mid:12C67A1EEC419342AF5E59DA31562C3F0C4FB23955@EXCHANGE1.ad.nottingham.ac.uk" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"\@SimSun";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle21
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Oh,
            OK, sorry I was thinking you wanted to add XML as an option
            to the runtime dropdown. I don’t think that’s the right
            place for it, but I might have misunderstood,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" lang="EN-US">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" lang="EN-US"> <a class="moz-txt-link-abbreviated" href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">xerte-dev-bounces@lists.nottingham.ac.uk</a>
                [<a class="moz-txt-link-freetext" href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">mailto:xerte-dev-bounces@lists.nottingham.ac.uk</a>] <b>On
                  Behalf Of </b>Pat @ Pgogy<br>
                <b>Sent:</b> 12 April 2013 14:19<br>
                <b>To:</b> For Xerte technical developers<br>
                <b>Subject:</b> [Xerte-dev] Re: Modules and htaccess<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <div>
          <p class="MsoNormal">Well the tab is there for everyone, the
            only difference is the URL changes from<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal"><o:p> </o:p></p>
        </div>
        <div>
          <p class="MsoNormal">Xml_560 to<o:p></o:p></p>
        </div>
        <div>
          <p class="MsoNormal">Play_xml_560<br>
            <br>
            Pgogy Webstuff - <a moz-do-not-send="true" href="http://www.pgogywebstuff.com">http://www.pgogywebstuff.com</a><o:p></o:p></p>
          <div>
            <p class="MsoNormal">Makers of web things of a fair to
              middling quality<o:p></o:p></p>
          </div>
        </div>
        <div>
          <p class="MsoNormal" style="margin-bottom:12.0pt"><br>
            On 12 Apr 2013, at 13:49, Julian Tenney <<a moz-do-not-send="true" href="mailto:Julian.Tenney@nottingham.ac.uk">Julian.Tenney@nottingham.ac.uk</a>>
            wrote:<o:p></o:p></p>
        </div>
        <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
          <div>
            <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Getting
                xml out. I think that’s what you mean, anyway? I think
                that’s something for developers to get at, rather than
                end users to get confused about,</span><o:p></o:p></p>
            <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
            <div>
              <div style="border:none;border-top:solid #B5C4DF
                1.0pt;padding:3.0pt 0cm 0cm 0cm">
                <p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" lang="EN-US">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" lang="EN-US"> <a moz-do-not-send="true" href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">xerte-dev-bounces@lists.nottingham.ac.uk</a>
                    [<a moz-do-not-send="true" href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">mailto:xerte-dev-bounces@lists.nottingham.ac.uk</a>]
                    <b>On Behalf Of </b>Pat @ Pgogy<br>
                    <b>Sent:</b> 12 April 2013 12:58<br>
                    <b>To:</b> For Xerte technical developers<br>
                    <b>Subject:</b> [Xerte-dev] Re: Modules and htaccess</span><o:p></o:p></p>
              </div>
            </div>
            <p class="MsoNormal"> <o:p></o:p></p>
            <div>
              <p class="MsoNormal">The first or second bit<br>
                <br>
                Pgogy Webstuff - <a moz-do-not-send="true" href="http://www.pgogywebstuff.com">http://www.pgogywebstuff.com</a><o:p></o:p></p>
              <div>
                <p class="MsoNormal">Makers of web things of a fair to
                  middling quality<o:p></o:p></p>
              </div>
            </div>
            <div>
              <p class="MsoNormal" style="margin-bottom:12.0pt"><br>
                On 12 Apr 2013, at 11:37, Julian Tenney <<a moz-do-not-send="true" href="mailto:Julian.Tenney@nottingham.ac.uk">Julian.Tenney@nottingham.ac.uk</a>>
                wrote:<o:p></o:p></p>
            </div>
            <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
              <div>
                <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This
                    sounds like a rabbit hole for now,</span><o:p></o:p></p>
                <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
                <div>
                  <div style="border:none;border-top:solid #B5C4DF
                    1.0pt;padding:3.0pt 0cm 0cm 0cm">
                    <p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" lang="EN-US">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" lang="EN-US"> <a moz-do-not-send="true" href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">xerte-dev-bounces@lists.nottingham.ac.uk</a>
                        [<a moz-do-not-send="true" href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">mailto:xerte-dev-bounces@lists.nottingham.ac.uk</a>]
                        <b>On Behalf Of </b>Pat @ Pgogy<br>
                        <b>Sent:</b> 12 April 2013 11:03<br>
                        <b>To:</b> For Xerte technical developers<br>
                        <b>Subject:</b> [Xerte-dev] Re: Modules and
                        htaccess</span><o:p></o:p></p>
                  </div>
                </div>
                <p class="MsoNormal"> <o:p></o:p></p>
                <div>
                  <p class="MsoNormal">The play URL is now a sort of API<o:p></o:p></p>
                </div>
                <div>
                  <p class="MsoNormal"> <o:p></o:p></p>
                </div>
                <div>
                  <p class="MsoNormal">So rather than <o:p></o:p></p>
                </div>
                <div>
                  <p class="MsoNormal"> <o:p></o:p></p>
                </div>
                <div>
                  <div>
                    <p class="MsoNormal">play.php?template_id=1&method=flash<o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal"> <o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal">You could have <o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal"> <o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal">play.php?template_id=1&method=XML<o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal"> <o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal">Which just returns the XML<o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal"> <o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal">So you cold retire the XML page
                      from the root folder (over time)<o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal"> <o:p></o:p></p>
                  </div>
                  <div>
                    <p class="MsoNormal">Now where this could get
                      interesting is you could make an XML remote method
                      to change the file locations and host a single
                      engine at site x, and dynamically bring in content
                      that way. A sort of xpert shop window<br>
                      <br>
                      Pgogy Webstuff - <a moz-do-not-send="true" href="http://www.pgogywebstuff.com">http://www.pgogywebstuff.com</a><o:p></o:p></p>
                    <div>
                      <p class="MsoNormal">Makers of web things of a
                        fair to middling quality<o:p></o:p></p>
                    </div>
                  </div>
                  <div>
                    <p class="MsoNormal" style="margin-bottom:12.0pt"><br>
                      On 12 Apr 2013, at 10:08, Julian Tenney <<a moz-do-not-send="true" href="mailto:Julian.Tenney@nottingham.ac.uk">Julian.Tenney@nottingham.ac.uk</a>>
                      wrote:<o:p></o:p></p>
                  </div>
                  <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt;-webkit-tap-highlight-color:
                    rgba(26, 26, 26,
                    0.296875);-webkit-composition-fill-color: rgba(175,
                    192, 227, 0.230469);-webkit-composition-frame-color:
                    rgba(77, 128, 180, 0.230469)">
                    <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Is
                        that something end users would need to see, or
                        is this tech stuff for an API call?</span><o:p></o:p></p>
                    <p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
                    <div>
                      <div style="border:none;border-top:solid #B5C4DF
                        1.0pt;padding:3.0pt 0cm 0cm 0cm">
                        <p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" lang="EN-US">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" lang="EN-US"> <a moz-do-not-send="true" href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">xerte-dev-bounces@lists.nottingham.ac.uk</a>
                            [<a moz-do-not-send="true" href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">mailto:xerte-dev-bounces@lists.nottingham.ac.uk</a>] <b>On
                              Behalf Of </b>Pat @ Pgogy<br>
                            <b>Sent:</b> 12 April 2013 08:22<br>
                            <b>To:</b> For Xerte technical developers<br>
                            <b>Subject:</b> [Xerte-dev] Re: Modules and
                            htaccess</span><o:p></o:p></p>
                      </div>
                    </div>
                    <p class="MsoNormal"> <o:p></o:p></p>
                    <div>
                      <p class="MsoNormal">At the moment XML is a link
                        option for XOT files, but all it does is return
                        the XML.<o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal"> <o:p></o:p></p>
                    </div>
                    <div>
                      <p class="MsoNormal">As we now have different
                        methods for displaying content for a module, XML
                        could be one of those?<br>
                        <br>
                        Pgogy Webstuff - </p></div></blockquote></div></div></blockquote></div></blockquote></div></blockquote></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Xerte-dev mailing list</span><br><span><a href="mailto:Xerte-dev@lists.nottingham.ac.uk">Xerte-dev@lists.nottingham.ac.uk</a></span><br><span><a href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev">http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev</a></span><br></div></blockquote></body></html>