[Xerte-dev] Re: Modular Play and New Templates

[Julian Tenney]

S'ok, there wasn't a media folder in templates...

From: Tenney Julian
Sent: 07 February 2013 11:32
To: 'For Xerte technical developers'
Subject: RE: [Xerte-dev] Re: Modular Play and New Templates

Having added the tempalte and put it basic.sql, there isn't a media folder being created in the project's user-files...?

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 Dave Burnett
Sent: 07 February 2013 11:14
To: xerte-dev at lists.nottingham.ac.uk<mailto:xerte-dev at lists.nottingham.ac.uk>
Subject: [Xerte-dev] Re: Modular Play and New Templates

Way cool.


________________________________
From: Julian.Tenney at nottingham.ac.uk<mailto:Julian.Tenney at nottingham.ac.uk>
To: Julian.Tenney at nottingham.ac.uk<mailto:Julian.Tenney at nottingham.ac.uk>; xerte-dev at lists.nottingham.ac.uk<mailto:xerte-dev at lists.nottingham.ac.uk>
Date: Thu, 7 Feb 2013 09:48:55 +0000
Subject: [Xerte-dev] Re: Modular Play and New Templates
Apologies, fat fingers:
http://www.nottingham.ac.uk/~cczjrt/bootstrapLO

From: Tenney Julian
Sent: 07 February 2013 09:47
To: 'For Xerte technical developers'
Subject: Modular Play and New Templates

Question for Pat I think:

With the html5 playout, Fay has added play_html5.php that does the work, that's all fine. I've got a new template I'd like to build in that produces this stuff:
http://www.nottingham.ac.uk/~cczjrt/boostrapLO. The editor is a standard xerte wizard / xwd thing, but it uses its own html page to parse the xml and create the content.

So I could add another html page to the folder and repeat what Fay has done for html5, but that seems a bit messy to sustain if, one day, we have loads of runtimes doing different things, I wondered if your modular stuff handled this in a more graceful way?

There's another difference here: Fay's html5 code plays existing content - so you have two alternative urls for the same piece, ultimately we'll switch toolkits to use the html5 one as the default, and the old one will remain as a legacy. In my case, it doesn't work like that, these projects will always only use their html page: so that needs to be the url to display in properties for the project, and I guess that's what needs to export as well.

What do you think is the best thing to do?

Julian




_______________________________________________ Xerte-dev mailing list Xerte-dev at lists.nottingham.ac.uk<mailto: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/20130207/234a1593/attachment.html>