<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hmm...<br>
    <br>
    It is already kind of modular isn't it?<br>
    <br>
    I mean the root play.php checks security etc, and determines whether
    it is allowed to display the LO, and than it includes '
    module/<framework>/play.php'  that should have the proper
    'show_template'  and 'dont_show_template' routines. Only in the
    latter should we check for what engine to use, because that is xerte
    specific. We could call the column in the db about what engine top
    use in the templatesdetails 'extra_args' so other templates types
    can use this as well for other purposes.<br>
    <br>
    No need to have an extra play in the root then, only in the
    module/site/.... <br>
    <br>
    That seems like a nice way out of this. I'll implement it this way
    for play and module/xerte/play<br>
    <br>
    And you can use url params on play that would only make sense for
    certain modules, i.e. you could request
    play.php?template_id=4&engine=xenith and if this happens to be
    an eBook, the engine parameter would just be ignore. No harm
    done....<br>
    <br>
    So: The author determines what he or she would like to be the most
    appropriate engine, nothing will change on the urls, there is a way
    to overrule the author's wishes (we can even let the author prohibit
    that if we really want that) and there is a nice way to introduce
    new play, preview, peer etc.<br>
    <br>
    Tom<br>
    <br>
    <br>
    <div class="moz-cite-prefix">Op 10-4-2013 12:24, Julian Tenney
      schreef:<br>
    </div>
    <blockquote
cite="mid:12C67A1EEC419342AF5E59DA31562C3F0C4F9FC46D@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:Helvetica;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@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.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.EmailStyle19
        {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">Is
            there any way we can do both things, i.e. leave the existing
            stuff in place so things don’t break, but build a new
            modular play engine that handles the modular stuff much
            better? When I put the site template in it was obvious that
            it was a bit of a pain, as you say having to add new files
            to the root folder is bad news, and having to modify other
            files in the root folder is also not so plug and play: there
            is specific (if (thisSortOfTemplate) do this else do that)
            code in there, which shouldn’t be there really.<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>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We
            wanted to put a new zip out on 26<sup>th</sup> April, a
            tentative deadline. I don’t mind waiting a few more weeks,
            but we really need to get this out there so that it can be
            installed in places before the summer – so those who want to
            build materials for next year can use it over the summer.
            The end of May would be about as far as I’d want to wait I
            think.<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>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">What
            do others think?<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><a class="moz-txt-link-abbreviated" href="mailto:xerte@pgogywebstuff.com">xerte@pgogywebstuff.com</a><br>
                <b>Sent:</b> 10 April 2013 11: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>
        <p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">True,
            and happy to shut up<o:p></o:p></span></p>
        <div>
          <p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif""><o:p> </o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">But
              I first raised this in November - <a
                moz-do-not-send="true"
href="http://lists.nottingham.ac.uk/pipermail/xerte-dev/2012-November/002868.html">http://listsnottingham.ac.uk/pipermail/xerte-dev/2012-November/002868.html</a> -
              but it didn't go anywhere<o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif""><o:p> </o:p></span></p>
        </div>
        <div>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">-----
                Original Message -----<o:p></o:p></span></p>
            <div>
              <div>
                <p class="MsoNormal" style="background:#E4E4E4"><b><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">From:<o:p></o:p></span></b></p>
              </div>
              <p class="MsoNormal" style="background:#E4E4E4"><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">"For
                  Xerte technical developers" <<a
                    moz-do-not-send="true"
                    href="mailto:xerte-dev@lists.nottingham.ac.uk">xerte-dev@lists.nottingham.ac.uk</a>><o:p></o:p></span></p>
            </div>
            <p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif""><o:p> </o:p></span></p>
            <div>
              <p class="MsoNormal"><b><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">To:<o:p></o:p></span></b></p>
            </div>
            <p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">"For
                Xerte technical developers" <<a
                  moz-do-not-send="true"
                  href="mailto:xerte-dev@lists.nottingham.ac.uk">xerte-dev@lists.nottingham.ac.uk</a>><o:p></o:p></span></p>
            <div>
              <p class="MsoNormal"><b><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">Cc:<o:p></o:p></span></b></p>
            </div>
            <p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif""><o:p> </o:p></span></p>
            <div>
              <p class="MsoNormal"><b><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">Sent:<o:p></o:p></span></b></p>
            </div>
            <p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">Wed,
                10 Apr 2013 09:41:32 +0100<o:p></o:p></span></p>
            <div>
              <p class="MsoNormal"><b><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">Subject:<o:p></o:p></span></b></p>
            </div>
            <p class="MsoNormal"><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">[Xerte-dev]
                Re: Modules and htaccess<br>
                <br>
                <br>
                Always we seem to hit something fundamental right before
                we're due to finish the work. There is a degree of
                frustration here with two things:<br>
                <br>
                - we have already worked through this twice: Fay has
                worked through it once with Pat to get the html5 links
                working, and I have worked through it with Pat to get
                the site template working. Now we want to do it
                differently?<br>
                - if you take pre-release code and it changes, well,
                that's sometimes life. Play_html5 was always intended as
                a way of beta testing the templates, rather than
                anything else.<br>
                <br>
                At this stage of things, I think we should go with what
                we have, and Tom's database solution solution, and get
                this phase of work done, and then address it later when
                we have a new cycle underway. I appreciate the issues,
                but there is no point in getting hung about
                functionality that no one is using yet (modularity), at
                the expense of functionality that everyone wants to use
                (html5 delivery). <br>
                <br>
                -----Original Message-----<br>
                From: <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>]
                On Behalf Of Ron Mitchell<br>
                Sent: 09 April 2013 18:15<br>
                To: 'For Xerte technical developers'<br>
                Subject: [Xerte-dev] Re: Modules and htaccess<br>
                <br>
                For me the basic principal must be whatever we want to
                be defaults for any new solution mustn't break existing
                links or require people to duplicate or re-write any
                code to maintain that compatibility. The vast majority
                will not have the time, skills or inclination to do
                that. So...<br>
                <br>
                /play.php?template_id=123 and /play_123 including the
                embed code links should continue to play existing LO's
                via Flash likewise<br>
                /play_html5.php?template_id=123 and /play_html5_123
                should continue to work even if that's no longer the
                default for new html 5, 6 or 7 LO's.<br>
                <br>
                I can see the point about not referring to html5 and
                keeping it more future proofed and again I can't see a
                problem with changes like this or the new defaults being
                Play.php?template_id=560&method=HTML as long as
                existing links aren't broken. But what would be the
                Apache/htaccess version of that? <br>
                <br>
                Over time JISC Techdis and other organisations and
                individuals have shared many links to LO's they have
                made public with the community, with their learners,
                with colleagues and this includes sharing of the
                play_html5 links. Rightly or wrongly that's what we've
                had since the 1.8 release so obviously we shouldn't
                break those links if we can possibly avoid it.<br>
                <br>
                HTH<br>
                Ron<br>
                <br>
                -----Original Message-----<br>
                From: <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>]
                On Behalf Of Smith, John<br>
                Sent: 09 April 2013 17:25<br>
                To: <a moz-do-not-send="true"
                  href="mailto:xerte-dev@lists.nottingham.ac.uk">xerte-dev@lists.nottingham.ac.uk</a><br>
                Subject: [Xerte-dev] Re: Modules and htaccess<br>
                <br>
                Howdy<br>
                <br>
                I personally think you need to run everything through
                the same page, with parameters. Its the only way you can
                prevent worsening the situation 12 months down the line
                where we have many deployed play urls which have to be
                maintained... Plan to deprecate play_html5 and then
                people can rewrite that page to your main play.php page
                with method=html or even duplicate the main play.php
                file as play_html5 if they must.<br>
                <br>
                Begs the question - should we drop references to html5
                and just call it html - what happens if they release
                html6 in a few years?<br>
                <br>
                Regards<br>
                <br>
                John Smith<br>
                Learning Technologist<br>
                School of Health and Life Sciences<br>
                <br>
                Sent from Samsung Galaxy SII<br>
                <br>
                <br>
                <br>
                "Pat @ Pgogy" <<a moz-do-not-send="true"
                  href="mailto:xerte@pgogywebstuff.com">xerte@pgogywebstuff.com</a>>
                wrote:<br>
                <br>
                <br>
                Could we use the following URL structure?<br>
                <br>
                Can the play URL be<br>
                <br>
                Play.php?template_id=560<br>
                And<br>
                Play.php?template_id=560&method=HTML<br>
                <br>
                And not playhtml.php?<br>
                <br>
                _______________________________________________<br>
                Xerte-dev mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:Xerte-dev@lists.nottingham.ac.uk">Xerte-dev@lists.nottingham.ac.uk</a><br>
                <a moz-do-not-send="true"
                  href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev">http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev</a><br>
                This message and any attachment are intended solely for
                the addressee and may contain confidential information.
                If you have received this message in error, please send
                it back to me, and immediately delete it. Please do not
                use, copy or disclose the information contained in this
                message or in any attachment. Any views or opinions
                expressed by the author of this email do not necessarily
                reflect the views of the University of Nottingham.<br>
                <br>
                This message has been checked for viruses but the
                contents of an attachment may still contain software
                viruses which could damage your computer system:<br>
                you are advised to perform your own checks. Email
                communications with the University of Nottingham may be
                monitored as permitted by UK legislation.<br>
                <br>
                Glasgow Caledonian University is a registered Scottish
                charity, number SC021474<br>
                <br>
                Winner: Times Higher Education’s Widening Participation
                Initiative of the Year 2009 and Herald Society’s
                Education Initiative of the Year 2009.<br>
                <a moz-do-not-send="true"
href="http://www.gcu.ac.uk/newsevents/news/bycategory/theuniversity/1/name,6219,en.html">http://www.gcu.ac.uk/newsevents/news/bycategory/theuniversity/1/name,6219,en.html</a><br>
                <br>
                Winner: Times Higher Education’s Outstanding Support for
                Early Career Researchers of the Year 2010, GCU as a lead
                with Universities Scotland partners.<br>
                <a moz-do-not-send="true"
href="http://www.gcu.ac.uk/newsevents/news/bycategory/theuniversity/1/name,15691,en.html">http://www.gcu.ac.uk/newsevents/news/bycategory/theuniversity/1/name,15691,en.html</a><br>
                _______________________________________________<br>
                Xerte-dev mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:Xerte-dev@lists.nottingham.ac.uk">Xerte-dev@lists.nottingham.ac.uk</a><br>
                <a moz-do-not-send="true"
                  href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev">http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev</a><br>
                <br>
                <br>
                _______________________________________________<br>
                Xerte-dev mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:Xerte-dev@lists.nottingham.ac.uk">Xerte-dev@lists.nottingham.ac.uk</a><br>
                <a moz-do-not-send="true"
                  href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev">http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev</a><br>
                _______________________________________________<br>
                Xerte-dev mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:Xerte-dev@lists.nottingham.ac.uk">Xerte-dev@lists.nottingham.ac.uk</a><br>
                <a moz-do-not-send="true"
                  href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev">http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev</a><o:p></o:p></span></p>
          </blockquote>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Xerte-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Xerte-dev@lists.nottingham.ac.uk">Xerte-dev@lists.nottingham.ac.uk</a>
<a class="moz-txt-link-freetext" href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev">http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
--

Tom Reijnders
TOR Informatica
Chopinlaan 27
5242HM Rosmalen
Tel: 073 5226191
Fax: 073 5226196

</pre>
  </body>
</html>