<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Almost finished.<br>
<br>
I didn't change anything yet to modularize the properties page<br>
<br>
- Changed play.php (root) and modules/xerte/play.php and preview<br>
- Made play_html5.php (root) redirect to new play<br>
- Make use of the same template files as export does for the play
and preview<br>
- Make wizard toggle the engine on Ctrl-click<br>
- Move site to its own module dir<br>
- Changed basic.sql<br>
- updates upgrade.php<br>
<br>
Not thoroughly tested yet, not committed yet<br>
<br>
Patch is not attached but available. (from svn 752)<br>
<br>
It's about 2.2Mb<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">Op 10-4-2013 23:39,
<a class="moz-txt-link-abbreviated" href="mailto:xerte@pgogywebstuff.com">xerte@pgogywebstuff.com</a> schreef:<br>
</div>
<blockquote
cite="mid:7c0e022c334d026b2b432c6e3dce9bc633c93a0c@webmail.hosting.heartinternet.co.uk"
type="cite">
<div>Hello,</div>
<div><br>
</div>
<div>Sorry for delay - travelling home from a conference.... again</div>
<div><br>
</div>
<div>The properties page is at present not modular - as it is the
same code for each module. At present only Xerte Online Toolkits
modules will have more than one URL, hence it needs some
"Module" work.</div>
<div><br>
</div>
<div>I think I could see a case for giving XOT modules a new tab
on properties which is HTML access - because in theory some of
the projects are to become HTML5 projects. This tab could
explain the process and give the preview and default setting
options?</div>
<div><br>
</div>
<div>This way the main properties tab with the links in could
remain as is (for now) and as the XOT stuff is migrated then we
could remove the tab</div>
<div><br>
</div>
<div>OR</div>
<div><br>
</div>
<div>You could modularise part of the properties page and give
each module a URL_return function like what exists at present</div>
<div><br>
</div>
<div>I sort of prefer the top version, but am not fussed</div>
<div><br>
</div>
<div><a moz-do-not-send="true"
href="https://github.com/patlockley/XOT-templatecanvas">https://github.com/patlockley/XOT-templatecanvas</a> exists
as well</div>
<div><br>
</div>
<div>Peer.php doesn't exist for all projects, you can turn it on
in the .info file should you want too</div>
<div><br>
</div>
<div>REMEMBER</div>
<div><br>
</div>
<div>if you add a new module you need to add the new language
files as well</div>
<div><br>
</div>
<div>Tom how do you want to divide the work on this? I don't feel
it's fair for you to do it all given how much I've moaned about
this :)</div>
<br>
Pgogy Webstuff <a class="moz-txt-link-freetext" href="http://www.pgogywebstuff.com">http://www.pgogywebstuff.com</a>
<div>Makers of Web things of a fair to middling quality</div>
<br>
<blockquote><br>
----- Original Message -----<br>
<div style="width:100%;background:rgb(228,228,228);">
<div style="font-weight:bold;">From:</div>
"For Xerte technical developers"
<a class="moz-txt-link-rfc2396E" href="mailto:xerte-dev@lists.nottingham.ac.uk"><xerte-dev@lists.nottingham.ac.uk></a></div>
<br>
<div style="font-weight:bold;">To:</div>
"For Xerte technical developers"
<a class="moz-txt-link-rfc2396E" href="mailto:xerte-dev@lists.nottingham.ac.uk"><xerte-dev@lists.nottingham.ac.uk></a><br>
<div style="font-weight:bold;">Cc:</div>
<br>
<div style="font-weight:bold;">Sent:</div>
Wed, 10 Apr 2013 17:29:49 +0200<br>
<div style="font-weight:bold;">Subject:</div>
[Xerte-dev] Re: Modules and htaccess<br>
<br>
<br>
There are some subtle differences:<br>
<br>
Yes, the user could delivery options in the property page, but
you need to realise that the proerty page is also modular, the
form is generated from the modules/<framework> php code.
So... only xerte LO's would get that option.<br>
<br>
And then the URLs that would be provided will NOT be different,
but the way the URL behaves, i.e. in the module play.php the DB
is inquired to see which engine to use.<br>
<br>
I think that I go ahead and show you how everything is pieces
nicely together.<br>
<br>
As an example, your 'site' stuff needs to have 'site' (or
whetever you want to call it) in the originaltemplatesdetails
table in the 'framework' column, and the play_site.php,
preview_site.php and perhaps export_site.php should move to a
folder modules/site and be called play.php, preview.php and
perhaps export.php.<br>
<br>
Then you can use the regular 'root' play.php and 'root'
preview.php... and even peer.php<br>
<br>
Right Pat?<br>
<br>
I am working on it, and provide you with a patch so you can
test. Once you understand what is reuired, it is rather
straightforward. <br>
<br>
If we're committing this, I'll will also write an article of how
this works.<br>
<br>
Tom<br>
<br>
<br>
<div class="moz-cite-prefix">Op 10-4-2013 17:05, Julian Tenney
schreef:<br>
</div>
<blockquote>
<div class="WordSection1">
<p class="MsoNormal">I'd prefer to say, finish your stuff,
then I'll mangle</p>
<p> </p>
<p class="MsoNormal">Mangle away… this obviously has links
to the properties panel and URLs for each piece as we
discussed earlier in the week. To summarise the
discussions, here’s where I thought we’d got to:</p>
<p> </p>
<p class="MsoNormal">The user would select the delivery
option from the properties panel;</p>
<p class="MsoNormal">Different URLs would provide access to
the content – so the flash / html URLs would actually be
available</p>
<p class="MsoNormal">Principle: authors test and check
rather than auto-conversion</p>
<p class="MsoNormal">The setting in the properties panel
would drive the URLs in the various feeds etc</p>
<p class="MsoNormal">Principle: existing links continue to
work </p>
<p class="MsoNormal">Workaround: we can leave the
play_html5.php page in place as it’s not only Ron who is
already putting content ‘live’ this way</p>
<p class="MsoNormal">We need to accommodate the site
template as well (which I’m going to have to rename for
political reasons here, otherwise M&C will kill it.
Learning Module?)</p>
<p> </p>
<p class="MsoNormal">Is there anything else? If we have a
good list, we’ll only have to do the work once…</p>
<p> </p>
<p class="MsoNormal">Thanks Tom and Pat for picking this up,</p>
<p> </p>
<p class="MsoNormal">Julian</p>
<p> </p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,
'sans-serif';color:#1F497D;"></span></p>
<p> </p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1pt;padding:3pt 0cm 0cm 0cm;">
<p class="MsoNormal"><b><span
style="font-size:10pt;font-family:Tahoma,
'sans-serif';" xml:lang="en-us" lang="en-us">From:</span></b><span
style="font-size:10pt;font-family:Tahoma,
'sans-serif';" xml:lang="en-us" lang="en-us"> <a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">xerte-dev-bounces@lists.nottingham.ac.uk</a>
[<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="mailto:xerte-dev-bounces@lists.nottingham.ac.uk">mailto:xerte-dev-bounces@lists.nottingham.acuk</a>]
<b>On Behalf Of </b>Pat @ Pgogy<br>
<b>Sent:</b> 10 April 2013 12:13<br>
<b>To:</b> For Xerte technical developers<br>
<b>Subject:</b> [Xerte-dev] Re: Modules and htaccess</span></p>
</div>
</div>
<p> </p>
<div>
<p class="MsoNormal">I didn't make the changes last time
(as sorry to sound like a stuck record) as I didn't
think we'd agreed on it / added it to the road map. So I
didn't want to waste a day of Fay's time in changing
stuff.</p>
</div>
<div>
<p> </p>
</div>
<div>
<p class="MsoNormal">I felt xenith was important and so I
didn't want to screw it up with the wrong sort of
changes.</p>
</div>
<div>
<p> </p>
</div>
<div>
<p class="MsoNormal">You could place a header redirect in
playhtml5.php to redirect the URL to another link, thus
old links could be maintained - albeit as a work round.</p>
</div>
<div>
<p> </p>
</div>
<div>
<p class="MsoNormal">I'd prefer to say, finish your stuff,
then I'll mangle<br>
<br>
Pgogy Webstuff - <a moz-do-not-send="true"
href="http://www.pgogywebstuff.com">http://www.pgogywebstuff.com</a></p>
<div>
<p class="MsoNormal">Makers of web things of a fair to
middling quality</p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt;"><br>
On 10 Apr 2013, at 11:24, Julian Tenney <<a
moz-do-not-send="true"
href="mailto:Julian.Tenney@nottingham.ac.uk">Julian.Tenney@nottingham.ac.uk</a>>
wrote:</p>
</div>
<blockquote style="margin-top:5pt;margin-bottom:5pt;">
<div>
<p class="MsoNormal"><span
style="font-size:11pt;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.</span></p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,
'sans-serif';color:#1F497D;"> </span></p>
<p class="MsoNormal"><span
style="font-size:11pt;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.</span></p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,
'sans-serif';color:#1F497D;"> </span></p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,
'sans-serif';color:#1F497D;">What do others think?</span></p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,
'sans-serif';color:#1F497D;"> </span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1pt;padding:3pt 0cm 0cm 0cm;">
<p class="MsoNormal"><b><span
style="font-size:10pt;font-family:Tahoma,
'sans-serif';" xml:lang="en-us" lang="en-us">From:</span></b><span
style="font-size:10pt;font-family:Tahoma,
'sans-serif';" xml:lang="en-us" 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><a moz-do-not-send="true"
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</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span
style="font-size:9pt;font-family:Helvetica,
'sans-serif';">True, and happy to shut up</span></p>
<div>
<p class="MsoNormal"><span
style="font-size:9pt;font-family:Helvetica,
'sans-serif';"> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9pt;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</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:9pt;font-family:Helvetica,
'sans-serif';"> </span></p>
</div>
<div>
<blockquote style="margin-top:5pt;margin-bottom:5pt;">
<p class="MsoNormal"><span
style="font-size:9pt;font-family:Helvetica,
'sans-serif';">----- Original Message -----</span></p>
<div>
<div>
<p class="MsoNormal" style="background:#e4e4e4;"><b><span
style="font-size:9pt;font-family:Helvetica,
'sans-serif';">From:</span></b></p>
</div>
<p class="MsoNormal" style="background:#e4e4e4;"><span
style="font-size:9pt;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>></span></p>
</div>
<p class="MsoNormal"><span
style="font-size:9pt;font-family:Helvetica,
'sans-serif';"> </span></p>
<div>
<p class="MsoNormal"><b><span
style="font-size:9pt;font-family:Helvetica,
'sans-serif';">To:</span></b></p>
</div>
<p class="MsoNormal"><span
style="font-size:9pt;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>></span></p>
<div>
<p class="MsoNormal"><b><span
style="font-size:9pt;font-family:Helvetica,
'sans-serif';">Cc:</span></b></p>
</div>
<p class="MsoNormal"><span
style="font-size:9pt;font-family:Helvetica,
'sans-serif';"> </span></p>
<div>
<p class="MsoNormal"><b><span
style="font-size:9pt;font-family:Helvetica,
'sans-serif';">Sent:</span></b></p>
</div>
<p class="MsoNormal"><span
style="font-size:9pt;font-family:Helvetica,
'sans-serif';">Wed, 10 Apr 2013 09:41:32 +0100</span></p>
<div>
<p class="MsoNormal"><b><span
style="font-size:9pt;font-family:Helvetica,
'sans-serif';">Subject:</span></b></p>
</div>
<p class="MsoNormal"><span
style="font-size:9pt;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></span></p>
</blockquote>
</div>
</div>
</blockquote>
<blockquote style="margin-top:5pt;margin-bottom:5pt;">
<div>
<p class="MsoNormal">_______________________________________________<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></p>
</div>
</blockquote>
</div>
<br>
<br>
<pre>_______________________________________________
Xerte-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Xerte-dev@lists.nottingham.ac.uk">Xerte-dev@lists.nottingham.ac.uk</a>
<a moz-do-not-send="true" 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">--
--
Tom Reijnders
TOR Informatica
Chopinlaan 27
5242HM Rosmalen
Tel: 073 5226191
Fax: 073 5226196
</pre>
<br>
<br>
<br>
</blockquote>
<br>
<br>
<br>
<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>