<html><body style="font-family: 'Helvetica Neue',Helvetica,Arial,sans-serif; font-size: 12px;"><blockquote>But this isn't a new solution, it's stopping a problem getting stupid.</blockquote><blockquote>So I installed a new module called Ebook. I want a play option which downloads the ebook, and a play_html option which allows people to read the ebook online.</blockquote><blockquote>Sadly I can't have this, because play_html has already been claimed by another module, so I am a bit screwed? So logically I create a new play_ebook page, but then to install that module I've got to copy a new page into the root just to make it work. And then imagine 50 modules, which 50 different play pages, so your root folder is full of files and remembering which one does which is a little bit awkward.</blockquote><blockquote>The apache version is just play_<method>_<number></blockquote><blockquote>So no one needs edit a htaccess again? Because those people who don't want to, or can't write code are going to need to update their htaccess as part of any update, or in theory after any new module is introduced.</blockquote><blockquote>As a sideways statement, if we modularise properly, XOT becomes a lot more useful (especially to me), without it I think we're missing a huge trick</blockquote><blockquote>----- Original Message -----<br /><div style="width:100%;background:rgb(228,228,228);"><div style="font-weight:bold;">From:</div> "For Xerte technical developers" <xerte-dev@lists.nottingham.ac.uk></div><br /><div style="font-weight:bold;">To:</div>"For Xerte technical developers" <xerte-dev@lists.nottingham.ac.uk><br /><div style="font-weight:bold;">Cc:</div><br /><div style="font-weight:bold;">Sent:</div>Tue, 9 Apr 2013 18:15:20 +0100<br /><div style="font-weight:bold;">Subject:</div>[Xerte-dev] Re: Modules and htaccess<br /><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 <br />
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: xerte-dev-bounces@lists.nottingham.ac.uk [mailto:xerte-dev-bounces@lists.nottingham.ac.uk] On Behalf Of Smith, John<br />
Sent: 09 April 2013 17:25<br />
To: xerte-dev@lists.nottingham.ac.uk<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" <xerte@pgogywebstuff.com> 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 />
Xerte-dev@lists.nottingham.ac.uk<br />
http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev<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 />
http://www.gcu.ac.uk/newsevents/news/bycategory/theuniversity/1/name,6219,en.html<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 />
http://www.gcu.ac.uk/newsevents/news/bycategory/theuniversity/1/name,15691,en.html<br />
_______________________________________________<br />
Xerte-dev mailing list<br />
Xerte-dev@lists.nottingham.ac.uk<br />
http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev<br /><br /><br />
_______________________________________________<br />
Xerte-dev mailing list<br />
Xerte-dev@lists.nottingham.ac.uk<br />
http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev<br /></blockquote></body></html>