The dryRun mode flag in google content api v2 is extremely useful and it's going to be hard to live without in forth coming v2.1. Can someone suggest useful strategies to compensate?
Thanks
Related
I am trying to develop a contextual gadget, but not getting any documentation for it. Google provides a document which is very old and not updated from long time. Process explained in that documentation to develop a gadget is deprecated.
Please if anyone have solution, help me.
You may want to check full documentation in Gmail Contextual Gadgets which was last updated June 29, 2016.
To develop a Gmail Contextual Gadgets, you may want to first check the given implementation parts also discussed in the documentation. Then, you may go through these summary of steps:
Use JQuery, or write JavaScript that conforms to ECMAScript 5 Strict Mode.
Note: You need to be using the correct development frameworks to provide an extra layer of protection between your gadget's potential vulnerabilities and your end users. To find out why, see Using the right frameworks for security.
Choose one or more pre-canned extractors. This determines which type of content will trigger your gadget.
Write a manifest for the gadget.
Write the gadget spec. This determines what the gadget will do when it is triggered.
Publish the gadget spec to a location which is accessible on the public Internet. An intranet will not work. Your hard drive will not work. (Why? Google's servers need to download the gadget. If they can't reach it, then Gmail can't display it.)
Install the gadget.
Test the gadget by sending yourself some email. The gadget should appear in Gmail whenever you read an email that contains the right sort of content. For more tips on testing gadgets, see Publishing Your Gadget in the gadgets API site.
It will really help if you go through the documentation as there are best practices, limitations and important details that you should note.
This related SO post might also help.
HI I am trying to embed google earth map in my website at the moment, but because the "embed kml tool has been deprecated" I am unsure of how to do so ? I have tried using fake embed kml tools, but they don't seem to work as they are relying on Google APIs.
Has anyone had similar experience in embedding google earth in html?
The Google Earth Plugin javascript API still works for now. Google even has "adapter" code that will let you place an "Earth" toggle button next to the "Map" and "Satellite" toggles and sync a Google Map javascript API V3 implementation to the Google Earth plugin. I've got it working even now on my own website, and I put it together only two months ago.
However, it will stop working in December this year, so I know I'm going to have to replace that. You should note that the new Google Maps My Maps engine (aka Google Maps Engine Lite) now has a native Earth mode instead of a Satellite mode. It is widely hoped that Google will soon release a Google Maps javascript API V4 that accesses this new maps engine, and give everyone a more uniform API interface to both Maps and Earth (and is consistent with the Mobile API implementations)
So for now, if you are just learning and the map added to your site is not critical long-term, go ahead and use the Google Earth plugin API to learn how to use both Maps and Earth APIs even together. It really won't be time wasted. But you will have to rework and replace it before year's end.
If however you are building something long-term for a customer or that map is the key aspect of your site, you should start researching alternatives. There are all sorts of discussions and recommendations (just do a search) and Google itself is making recommendations to use other (non-free) replacement products for commercial uses.
And keep watching Google's own developer's site for announcements about the APIs. Likely there will soon be a way to access the new Earth interface.
I've been looking into getting a developer key for YouTube Data API v2.Navigating to the page Google lists for this purpose gives me a blank page--so there is no way to actually get a developer key. Does this page show up blank for anyone else?
Is this a sign from Google that it's time to move to version 3? I would really prefer not to, since it has some anti-features that I want to avoid.
There were some transient issues with https://code.google.com/apis/youtube/dashboard/gwt/index.html that should be resolved.
To answer the larger question, using the Data API v2 is still an option, but we're definitely recommending the Data API v3 for new development. (There are still a few pieces of functionality that are only available in v2, but that list is not very long.)
I'm not sure what "anti-features" you're referring to, so it's hard to comment beyond that.
I want to develop an application that will visualize the recommendations of Google instant. It is for a course project and for now, I don't know much about web programming tools. What I wonder is that is it possible to retrieve that data from another web page. If you think it is possible and it is possible with which platform, could you please guide me to the correct direction?
Without more information on what you're actually trying to do, it's difficult to give a proper answer. From what I can understand, you just want a list of the auto-completed items from a Google search, to manipulate however you like?
In which case, using the highest-rated answer from here, you can use http://suggestqueries.google.com/complete/search?client=firefox&q=YOURQUERY to give you a JSON object which you can then manipulate to get the auto-complete results. The client= part is needed, but I haven't looked at various options you can put in there.
Personally, I've never used JSON before, so can't give you any help on how to go about parsing it, but you can find more information about it on the JSON website, and w3 website.
Will need to act like javascript or run a javascript engine OR a browser add on and communication with that add on.
What happens as you type is a javascript function is called. So you need to call this function in your own or mimic what it does. I guess it calls a web service/ web page form programamtically (ajax) with what you have typed. The server responds with the suggestions. Not very difficult as long as Google does not deny you if it realizes your not a browser. i think they like only 100 free API calls but you can google google about that.
Http Components in java will help calling the serice, with cookeis etc. You should use the dev tools on firefox to see what happens under the hood when you type in the google search bar and see the code.
I'm making an app and I plan to have some cloud happening with it, but I do not want to create a user data base and have the users need to remember their username and password.
Since it will be distributed through the chrome app store it's basically guaranteed that the user will have a google account. All I want to do is:
Get the user's email through the google account stuff. If I get it through there, well then their email is all the authentication I need to get that user's data.
If I end up putting the application on something other than chrome browser, I'll just have the user use their email to request a validation link, and then I'll send them a validation code for that account, they put the validation code into the application, it takes that as a verified user, so that's secure and easy as well.
EDIT: I'm looking into this. So far I have:
OAuth 2
Google API
But I have a problem that I don't know what to set as my javascript origins in the Google API and there isn't too much info on this abroad. If anyone can tell me what javascript origins I need to set for a chrome extension to access google api it would be a great help.
PS: Thanks for down vote, this is why I love resorting to stack exchange.
Hmmm, I think the only reason this was voted down is the fact that this question may be been asked somewhere on the site already (but I'll help you and give give a 1up).
So what you are wanting to use the Google OpenID. You will have to register your application with Google so they can provide OAuth2 tokens for you application. I have not done this with Google but with other services and it is pretty easy, just search around.
In terms of obtaining OAuth2 for your application in the chrome extension - this can be a pain since the extension is sandboxed and Google's example uses OAuth not OAuth2.
Here is solution I host on GitHub for this - I also use this in my extension GitHub Repositories:
https://github.com/jjNford/oauth2-chrome-extension
Hope this helps in some way. Don't get discourages with StackOverflow, it is a great resource with many great contributors.
Good luck!
I had to up vote you too as I'm tracking down a related issue so here is what I've found that may help.
According to these directions - http://code.google.com/p/google-api-javascript-client/wiki/Authentication - "In the "Authorized JavaScript Origins" box, enter the protocol and domain for your site." This should be the protocol (http:// or https://) followed by any optional subdomain followed by your domain name and no trailing slash. Nothing after the domain name.
This prevents certain kind of security attacks, see: http://en.wikipedia.org/wiki/Same_origin_policy.
There are some related questions here that I found that may help:
Problems with Google Picker API and selecting Google Drive items and google apis console 'Javascript origins'.
Now with all of that said, I am still trying to track down what values to put in there for one of my sites hosted as a Google Site, as none of the obvious values are working for me. So there may be some subtlety there that I have missed in this explanation.