[Xerte-dev] Re: Youtube RSS

Julian Tenney Julian.Tenney at nottingham.ac.uk
Mon Jul 6 14:59:40 BST 2015


OK, will look inot those for examples

From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Ron Mitchell
Sent: 06 July 2015 14:59
To: 'For Xerte technical developers'
Subject: [Xerte-dev] Re: Youtube RSS

yeah sounds like a plan but I'd suggest api_keys-dist.php or api_keys-sample.php to follow the way moodle or wordpress do this.

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 Julian Tenney
Sent: 06 July 2015 14:46
To: For Xerte technical developers
Subject: [Xerte-dev] Re: Youtube RSS

Yes we do, there is hardcoded key in the flickr model file as well (presumably mine) which we should also split out, but I think that's it.

So perhaps we need an api_keys.php file that defines the vars, and you rename it from api_keys.txt ?

From: Tenney Julian
Sent: 06 July 2015 14:42
To: 'For Xerte technical developers'
Subject: RE: [Xerte-dev] Re: Youtube RSS

Do we use any other API keys anwhere?

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 Ron Mitchell
Sent: 06 July 2015 14:42
To: 'For Xerte technical developers'
Subject: [Xerte-dev] Re: Youtube RSS

Just a quick comment to confirm that adding my own key works fine.
We obviously do need to get this working in a way that future upgrades don't break locally added keys.

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 Julian Tenney
Sent: 06 July 2015 12:04
To: For Xerte technical developers (xerte-dev at lists.nottingham.ac.uk<mailto:xerte-dev at lists.nottingham.ac.uk>)
Subject: [Xerte-dev] Youtube RSS

Hi,

I've got the youtube rss working with a hardcode API key. Before we release the code we can split that out and provide a file for people to store their own keys in and read that. I'd appreciate someone peer-reviewing my code: couple of questions:

We need to load the google api which I've done by simply adding...

<script src="https://apis.google.com/js/client.js?onload=googleApiClientReady"></script>

...to the top of the file.

The onGoogleApiClientReady function is defined in global scope so I wondered how to make it part of the youtuberss object, but if I simply define it within the object, it doesn't get called (obviously).

I think Fay or John will have an idea how to make all this nice and graceful! I've committed the file (you'll need an API key!)

Let me know comments,

J







This message and any attachment are intended solely for the addressee

and may contain confidential information. If you have received this

message in error, please send it back to me, and immediately delete it.



Please do not use, copy or disclose the information contained in this

message or in any attachment.  Any views or opinions expressed by the

author of this email do not necessarily reflect the views of the

University of Nottingham.



This message has been checked for viruses but the contents of an

attachment may still contain software viruses which could damage your

computer system, you are advised to perform your own checks. Email

communications with the University of Nottingham may be monitored as

permitted by UK legislation.







This message and any attachment are intended solely for the addressee

and may contain confidential information. If you have received this

message in error, please send it back to me, and immediately delete it.



Please do not use, copy or disclose the information contained in this

message or in any attachment.  Any views or opinions expressed by the

author of this email do not necessarily reflect the views of the

University of Nottingham.



This message has been checked for viruses but the contents of an

attachment may still contain software viruses which could damage your

computer system, you are advised to perform your own checks. Email

communications with the University of Nottingham may be monitored as

permitted by UK legislation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte-dev/attachments/20150706/0d19f690/attachment-0001.html>


More information about the Xerte-dev mailing list