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

[Pat @ Pgogy]

Preview and play differ in terms of logged in access and password protection - but the display code should be in a library function.

Agree your code base should be shared - wondering if modules could share that. In theory you could add a play parameter to the info file and then probably share the rest of the code?

That might work better?

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

On 8 Feb 2013, at 09:04, Julian Tenney <Julian.Tenney at nottingham.ac.uk> wrote:

> Well, it’s more that we have the same code in several places, and things like being able to get the runtime url in the wizard. I added a property to the wizard ‘runtime’ to point to my booststrap.php page.
>  
> A related question: is there anything different between preview and play, or could I just use the same file for both?
>  
> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat @ Pgogy
> Sent: 07 February 2013 17:51
> To: For Xerte technical developers
> Subject: [Xerte-dev] Re: Modular Play and New Templates
>  
> I would assume we accordion the templates list?
> 
> Pgogy Webstuff - http://www.pgogywebstuff.com
> Makers of web things of a fair to middling quality
> 
> On 7 Feb 2013, at 16:12, Julian Tenney <Julian.Tenney at nottingham.ac.uk> wrote:
> 
> Yeah, that’s pretty much what I’m doing. It will work and that’s fine, just wondering about the situation where there loads of these things…
>  
> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat @ Pgogy
> Sent: 07 February 2013 15:47
> To: For Xerte technical developers
> Subject: [Xerte-dev] Re: Modular Play and New Templates
>  
> Duplicate the modules xerte folder into modules new template name
>  
> Keep the edit php file as it is still xerte
>  
> Mangle play and preview to present the HTML
> 
> Pgogy Webstuff - http://www.pgogywebstuff.com
> Makers of web things of a fair to middling quality
> 
> On 7 Feb 2013, at 09:46, Julian Tenney <Julian.Tenney at nottingham.ac.uk> wrote:
> 
> 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
> 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/20130208/869ee67d/attachment.html>