[Xerte-dev] Re: Players and alternative formats

[Pat Lockley]

Could do, and just leave out the new modules?

The changes I discussed don't exist in 1.9 just yet - would later in week.

I need to list what's changed for the purposes of testing, but am a bit
worried that since the 1.9 branch was made a lot of new stuff has joined
1.8 (LTI for example) and I might undo some stuff? I can't see it clashing,
but....


On Wed, Nov 21, 2012 at 3:58 PM, Julian Tenney <
Julian.Tenney at nottingham.ac.uk> wrote:

> Why don’t you merge in your mod stuff, it won’t make a lot of odds to most
> people, but will allow some cool stuff later… most people won’t see any
> difference, right?****
>
> ** **
>
> ** **
>
> *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 15:53
>
> *To:* For Xerte technical developers
> *Subject:* [Xerte-dev] Re: Players and alternative formats****
>
> ** **
>
> i could, but is the php in 1.8 svn?
>
> It isn't a lot of php (an if statement or two)****
>
> ** **
>
> On Wed, Nov 21, 2012 at 3:16 PM, Julian Tenney <
> Julian.Tenney at nottingham.ac.uk> wrote:****
>
> Could you do the php side? In the wizard we can add a parameter to the LO
> playback=”flash” which can be updated to playback=”html” for people who
> want to experiment with the beta.****
>
>  ****
>
> Then in the wizard we can do ****
>
>  ****
>
> If (set as flash or undefined) //do it flash style****
>
>  ****
>
> Else****
>
>  ****
>
> //do it html5 style****
>
>  ****
>
> Appreciate the flash side is probably easier than the PHP side…****
>
>  ****
>
> *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 14:45****
>
>
> *To:* For Xerte technical developers
> *Subject:* [Xerte-dev] Re: Players and alternative formats****
>
>  ****
>
> -- Flash side --
>
> put a radio button in the editor
> add an extra parameter to the url generation code (event handler for the
> play button)
>
> -- php side --
>
> Edit preview and play .php to check for this new $_GET and then branch
>
> -- .htaccess side --
>
> Mod the reg exp****
>
>  ****
>
> On Wed, Nov 21, 2012 at 1:37 PM, Julian Tenney <
> Julian.Tenney at nottingham.ac.uk> wrote:****
>
> Time is of the essence for the 1.9 drop because we want to get that done
> by 30th November, so I like what you’re saying, but wonder if it can be
> done in time…?****
>
>  ****
>
> *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 13:29****
>
>
> *To:* For Xerte technical developers****
>
> *Subject:* [Xerte-dev] Re: Players and alternative formats****
>
>  ****
>
> Well it depends on what we call "now"****
>
>
>
> It's a bit roadmappy, but for 1.9 you'd not have html_play.php and
> play.php, but one play.php which would then switch on the variable set
> (within the module folder).
>
> You'd have an option somewhere of setting "HTML5" somehow (perhaps a radio
> box on the editor?) which would then send a request to set this session to
> be "HTML5" and all previews from then on would be HTML5 mode.
>
> Then you add an extension to the current play rule in htaccess to support
> a "third" variable, so play_560_html would play the template in HTML5 mode.
> In the future, play_560_scorm would do the scorm export. As long as
> play_560_[a-z]+ was handled in the php play code for that module you could
> do whatever you wanted to do.
>
> In theory you could also have preview_560_html as well
>
> It seems neater to me, but this is me speaking from my cave.
>
> Oooh a flint.****
>
>  ****
>
> On Wed, Nov 21, 2012 at 12:57 PM, Julian Tenney <
> Julian.Tenney at nottingham.ac.uk> wrote:****
>
> 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****
>
>  ****
>
>
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev****
>
>  ****
>
> ** **
>
>
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev****
>
>  ****
>
>
>
> ****
>
>
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev****
>
> ** **
>
>
>
>
> _______________________________________________
> 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/20121121/82491bc7/attachment-0001.html>