[Xerte-dev] Re: Modules and htaccess

[Pat @ Pgogy]

Hi Tom,

Cheers for doing all this - I feel like I'm being retired :) - found a few possible things that might not be quite right - not bugs, just logic stuff?

Would you prefer me to add comments to the files and commit or maybe send them to the list?

Pat

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

On 12 Apr 2013, at 22:31, Tom Reijnders <reijnders at tor.nl> wrote:

> Everything has just been committed. This is a fairly large commit (758). Don't forget to execute upgrade.php!! 
> 
> - Changed play.php (root) and modules/xerte/play.php and preview
> - Make play_html5.php (root) and preview_html5.php (root) redirect to new play
> - Make use of the same template files as export does for the play and preview
> - Get rid of difference between rloObject.js used for play and used for export
> - Only one location for MainPreloader.swf and xmlEngine.swf (for play and export, export used to copy it from a different location)
> - Modified wizard to call preview.php with 'engine=other' when Ctr+Play is clicked
> - Make peer.php use the same templates as play and preview and implement for javascript engine as well
> - Move site to its own module dir
> - Changed basic.sql
> - updates upgrade.php
> 
> 
> Op 12-4-2013 17:04, Tom Reijnders schreef:
>> Some questions, before I commit,
>> 
>> 1. Julian, do you already have a different name for 'site' or shall I commit site for the moment?
>> 2. Do we have consensus over the engine name? html5? javascript? xenith?
>> 
>> Now I have 'html5'  in the GUI, but 'javascript' in the code, because I think that is better w.r.t. flash.
>> 
>> The major reason I ask is that if we want to create the play_html5_560 play_flash_560 (not sure that's a good idea, I prefer that people have to put in a bit more effort to choose an engine different than the author wanted, so play_560?engine=html5)
>> 
>> Still even if we leave it at the engine=.... what will we call the engines? 
>> 
>> I prefer flash/javascript
>> 
>> Tom
>> 
>> 
>> 
>> Op 12-4-2013 16:48, Julian Tenney schreef:
>>> Oh, OK, sorry I was thinking you wanted to add XML as an option to the runtime dropdown. I don’t think that’s the right place for it, but I might have misunderstood,
>>>  
>>> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat @ Pgogy
>>> Sent: 12 April 2013 14:19
>>> To: For Xerte technical developers
>>> Subject: [Xerte-dev] Re: Modules and htaccess
>>>  
>>> Well the tab is there for everyone, the only difference is the URL changes from
>>>  
>>> Xml_560 to
>>> Play_xml_560
>>> 
>>> Pgogy Webstuff - http://www.pgogywebstuff.com
>>> Makers of web things of a fair to middling quality
>>> 
>>> On 12 Apr 2013, at 13:49, Julian Tenney <Julian.Tenney at nottingham.ac.uk> wrote:
>>> 
>>> Getting xml out. I think that’s what you mean, anyway? I think that’s something for developers to get at, rather than end users to get confused about,
>>>  
>>> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat @ Pgogy
>>> Sent: 12 April 2013 12:58
>>> To: For Xerte technical developers
>>> Subject: [Xerte-dev] Re: Modules and                       htaccess
>>>  
>>> The first or second bit
>>> 
>>> Pgogy Webstuff - http://www.pgogywebstuff.com
>>> Makers of web things of a fair to middling quality
>>> 
>>> On 12 Apr 2013, at 11:37, Julian Tenney <Julian.Tenney at nottingham.ac.uk> wrote:
>>> 
>>> This sounds like a rabbit hole for now,
>>>  
>>> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Pat @ Pgogy
>>> Sent: 12 April 2013 11:03
>>> To: For Xerte technical developers
>>> Subject: [Xerte-dev] Re: Modules and htaccess
>>>  
>>> The play URL is now a sort of API
>>>  
>>> So rather than 
>>>  
>>> play.php?template_id=1&method=flash
>>>  
>>> You could have 
>>>  
>>> play.php?template_id=1&method=XML
>>>  
>>> Which just returns the XML
>>>  
>>> So you cold retire the XML page from the root folder (over time)
>>>  
>>> Now where this could get interesting is you could make an XML remote method to change the file locations and host a single engine at site x, and dynamically bring in content that way. A sort of xpert shop window
>>> 
>>> Pgogy Webstuff - http://www.pgogywebstuff.com
>>> Makers of web things of a fair to middling quality
>>> 
>>> On 12 Apr 2013, at 10:08, Julian Tenney <Julian.Tenney at nottingham.ac.uk> wrote:
>>> 
>>> Is that something end users would need to see, or is this tech stuff for an API call?
>>>  
> _______________________________________________
> 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/20130412/c42f18af/attachment.html>