[Xerte-dev] Re: Players and alternative formats

[Julian Tenney]

I like to generalise solutions too. What would the implications be for what we have now?

From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat Lockley
Sent: 21 November 2012 12:43
To: For Xerte technical developers
Subject: [Xerte-dev] Players and alternative formats

Hello all,

This is a message from deep inside modularisation caves so it might not apply to all.

I have a semi working google maps making template, and when it "plays" at present it draws a map using the google maps API.

However, the play could also generate a KML file for people to download, or if the map couldn't load it could provide the data in a different way.

So then I thought this is effectively the HTML5 option (and you might argue the xml download, export, scorm are also "plays").

So I was thinking that rather than using ctrl + click, or extra buttons, you could facilitate an extra request variable consistently across modules.

Ergo you post a "HTML5" option at the URL and you get HTML5 back, you post a "XML" and get xml, or "JSON" and get json.

This way the URL Library doesn't need to change all the time, or the .htaccess, but you also get different plays for each module (and they are all distinct).

Thoughts?

Pat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte-dev/attachments/20121121/f1ccb106/attachment.html>