[Xerte-dev] Re: HTML5

Thu Mar 28 14:53:14 GMT 2013

At the moment pages that use the canvas tag (which doesn't work in IE8 for example) already give a message that your browser doesn't fully support this file type.  Maybe all we need to do then is just add a link pointing to the html5 version to the 'install Flash' message you already get if you try to view the Flash link without it.

I can probably come to the AGM if it's before the end of June but I'm unlikely to be here from July onwards...

From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Julian Tenney
Sent: 28 March 2013 14:37
To: For Xerte technical developers
Subject: [Xerte-dev] Re: HTML5

Brilliant.

1.       Exporting seems to cause people a lot of problems, but I guess they do seem to use it (rightly or wrongly). I'd prefer to have options to export the various types of zip for either html5 or flash, I think. I have no idea how hard this is to do? I'd love to drop this functionality because it just seems to cause a lot of unnecessary problems, I'm not sure people really need to export content as much as they do - but there are some valid reasons to do it, so I suppose we're stuck with it. Tom adapted the original exporting code, would this be something that is easy for Tom to look at? Or reassure me that I can adapt your code easily to use different paths / folders etc?

2.       The play_html5_1234 is a good idea, yes, for consistency. On installs where this works, does the play_html5.php?template_id= work as well?

3.       Yes, everything should default to the html5 output. Peer review needs a new URL as well. CTRL-Click can launch the flash version instead from the wizard. I'm not sure we need browser detection: people should use the URL they built it for; however, we should probably put something in place for older browsers to say 'upgrade your browser' or similar? I'm guessing the paths are easy to amend in the php?

What else do we need to look at before we can release this? This morning we tentatively agreed to have it all ready for FRIDAY 26th APRIL. Do we need a list of open issues that need resolving before the release? I'm thinking of the Firefox security thing in particular, though it sounds like you're getting close John? Also the thing with the buttons staying greyed out that appeared recently? If Tom's SCORM work isn't ready by then, I'm not sure it's a big problem?

I've made a titanpad here for a list of things to do: http://titanpad.com/xottwopointoh. I want to concentrate on finishing existing work, rather than starting anything new just now, but please add any bugs to it as well, and we'll fix as many as we can.

An aside, is it worth starting to think about when / where we do another AGM? If we do it outside of teaching time, we can do it in rooms here at no cost. Maybe sometime in July?

I'm off next week, but will have some time after that to help out with getting this finished,

Julian

From: xerte-dev-bounces at lists.nottingham.ac.uk<mailto: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.

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<http://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)

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.

b.      In the wizard should Ctrl-Click bring up the Flash version when clicking normally is changed to HTML5?

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.

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte-dev/attachments/20130328/e4a6db4b/attachment.html>