[Xerte-dev] Re: HTML5

[Pat @ Pgogy]

Ok, 

But we aren't just talking playing - we are also talking to export URLs and the scorm urls and the RSS feed urls and the syndicate urls.

So, yeah, two play urls is a bit messy

Pgogy Webstuff - http://www.pgogywebstuff.com
Makers of web things of a fair to middling quality

On 28 Mar 2013, at 09:51, Julian Tenney <Julian.Tenney at nottingham.ac.uk> wrote:

> play_560 for example should always play the flash version, because that was the version it was designed in / for. We should use a new URL for the play_html5 version. It’s up to people to decide whether to leave existing material as is, doing what it always has done, or whether to switch the links over.
>  
> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron Mitchell
> Sent: 28 March 2013 09:12
> To: 'For Xerte technical developers'
> Subject: [Xerte-dev] Re: HTML5
>  
> Personally I think we need manual choice as well as browser detection e.g. even if browser detection is built in it should still be possible to share a link to view via flash and a separate link to view via HTML 5
> So there’d be 3 types of links then? One forcing to Flash, one forcing to HTML5 and one deciding for you? Is that going to confuse people as to what link they’re sharing?  I agree you need to be able to make manual choice too though.
>  
> I think this kind of depends on the default e.g. right now we obviously have play.php for Flash and play_htm5.php for html 5
> If play.php detected for Flash player and if not found reverts to html 5 then perhaps only two links needed like we have now.
> I guess if play.php becomes the html 5 view by default then the second link could be play_flash.php which still reverts to html 5 if flash player not found.
>  
> Would that work?
>  
>  
> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Fay Cross
> Sent: 28 March 2013 08:52
> To: For Xerte technical developers
> Subject: [Xerte-dev] Re: HTML5
>  
> Thanks Ron
>  
>  
> Should there be a separate HTML5 only export option?
> That’s what I assumed there would be but I suppose the files could just be added into the existing export with an extra index page
>  
>  
> Should this be a management option e.g. giving people control over what is the default and what is the Ctrl + Click option?
> I like that idea
>  
>  
> Personally I think we need manual choice as well as browser detection e.g. even if browser detection is built in it should still be possible to share a link to view via flash and a separate link to view via HTML 5
> So there’d be 3 types of links then? One forcing to Flash, one forcing to HTML5 and one deciding for you? Is that going to confuse people as to what link they’re sharing?  I agree you need to be able to make manual choice too though.
>  
>  
> Thanks for files you sent – I’ll have a look at them in a bit
>  
>  
> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron Mitchell
> Sent: 27 March 2013 17:57
> To: 'For Xerte technical developers'
> Subject: [Xerte-dev] Re: HTML5
>  
> Hi Fay
> firstly on behalf of the whole community thanks for all your hard work on all the HTML 5 conversions - fantastic stuff!
>  
> A few comments/thoughts inline below...
>  
> HTH
> Ron
>  
> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Fay Cross
> Sent: 27 March 2013 17:17
> To: For Xerte technical developers
> Subject: [Xerte-dev] HTML5
>  
> Hello all
>  
> As you should know the HTML5 work is nearly complete and there are only a couple of page types for me to complete before we can release a new version of Toolkits with the HTML5 interface as the default view.  I have a few things that I could do with some help on before the release so if anyone can give me a hand with them or just give your opinions it would be much appreciated...
>  
> 1.       Exporting HTML projects:
> The files that would need to be in the zip would be more or less the same as for the Flash version but using the common_html5 and models_html5 folders instead of common/models.
> Would the easiest way to do this be to include an additional index page e.g. index_html5.htm
> Should there be a separate HTML5 only export option?
> HTML 5 export for vieing locally or importing into a VLE is certainly something people have been asking for
>  
> 2.       Abbreviated link:
> Possibly something Ron can help with as I’ve noticed it’s working on his install.  Can abbreviated links be made to work e.g. www.nottingham.ac.uk/toolkits/play_html5_560 rather than using the full url?
> (Apologies Pat, I think you partly answered this for me previously but I can’t find it)
> I've attached a sample .htaccess with most of this included you will need to replace /xerte/ with whatever your xot folder is which you can probably check in your existing .htaccess and just add in the missing lines. However at least some of the rss links need further work which I posted to the list previously but no reply.
> The htaccess.conf in the setup folder needs updating too but to be honest I'm not sure how that works e.g. if it's updated during install but I don't think it is.
>  
> 3.       Play / Preview links:
> a.       Links in project properties, preview button in workspace and preview in wizard need to be updated to go to the HTML5 version.
> Should this be a management option e.g. giving people control over what is the default and what is the Ctrl + Click option?
> b.      In the wizard should Ctrl-Click bring up the Flash version when clicking normally is changed to HTML5?
> Yes I think so but see response to a. above
> c.       Do you think there needs to be some browser detection that decides which version people see?  The problem I can see with this is that if we start adding new features or pages to the HTML5 version then by sending them to the Flash version instead they may miss out on some content.  Not many of the page types in the HTML5 version actually use HTML5 tags if that makes sense – probably just the handful where the canvas tag is used (textDrawing, charts etc.) so there might not be many instances where there will be problems if you’re on an older browser anyway.
> Personally I think we need manual choice as well as browser detection e.g. even if browser detection is built in it should still be possible to share a link to view via flash and a separate link to view via HTML 5
>  
> 4.       Page models:
> a.       John – is the flickr page finished?
> b.      Johnathan – I’ve emailed you off list about a few queries I’ve got with the connector pages, I hope this is ok – I didn’t want to bother everyone else with them
> c.       SCORM – this isn’t working at the moment but I can’t quite remember what’s missing.  I’ll email with more details of what help I might need when I’ve looked back at it
>  
> Thanks
> Fay
>  
> 
>  
> 
> 
> 
> 
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte-dev/attachments/20130328/6f091372/attachment-0001.html>