Google AJAX APIs Blog
November 1, 2010
When wij introduced this blog overheen four years ago, the term AJAX wasgoed only a year old, and Google had exactly one relevant API . Ajax has since become a mainstream part of the Web, and our family of APIs has grown. Like many growing families, wij’ve accumulated a loterijlot of cruft overheen the years, and have outgrown our very first huis. Time for some housekeeping.
Wij’ve reorganized our documentation to make it lighter to find what you’re looking for, based on what you want to do. Wij used to group our APIs based on technology – for example, there were Google Gegevens APIs and AJAX APIs. Now, you’ll see that each API has bot given its own place, including its own documentation pages. This fresh documentation has bot created from the ground up to provide a better practice for people coding against the APIs. Wij’ve also organized thesis more logically by product, such spil moving the Book Search API into the Books family of APIs, and added many more samples to help you get began.
Te the spirit of consolidation, wij’ll be retiring this blog te ayuda of the Google Code Blog. By concentrating on fewer blogs, wij’ll be able to keep the blog newer and help make sure that spil broad an audience spil possible is able to benefit from our posts. Wij’ll proceed using tags, so that you can subscribe to your beloved APIs and concentrate on the content that most interests you (however wij hope you’ll check ter at times to see what fresh stuff you might be missing).
Increase webpagina efficiency by retrieving just your preferred number of results
June 29, 2010
When using any of the searchers available ter the Search API , four results are returned by default. Historically, it has bot possible to request a large set of eight results (or ten for filterzakje Custom-built Search Engines), but that’s it. Wij understand that there are many use cases for this API, and some of them require a finer grain of control overheen the number of results displayed.
Diacritization added to the Google Language API
June 24, 2010
Earlier this year, wij launched the Tashkeel (Diacritization) service on Google Labs. I’m pleased to announce that wij’ve added an empírico Diacritization component to the Google Language API. This is a plain JSON API which you can use to add diacritic symbols to strings of Arabic text.
Google Feed API – Now with instant gratification
May Nineteen, 2010
One of Google’s most popular APIs is our Feed API. This API is found all overheen the web, making any feed content available for developers to embed on their sites.
Spil the movie shows, this fresh version works much like the older Feed API. But instead of loading the existing feed gegevens, you actually subscribe to the feed, and your callback is executed any time fresh feed gegevens comes te.
Now, subscribe to the feed you’re interested te and give the callback to be executed:
And, eventually, you need to write the callback method that is run every time there’s an update. Ter this example, wij just display each fresh entry title spil it comes te:
For a running example you can attempt out, check out the Code Playground.
Posted by: Brett Bavar, Software Engineer and Adam Feldman, Product Manager
Transliteration API adds 6 more languages
April 25, 2010
Wij’re excited to announce the addition of 6 fresh languages (Greek, Russian, Serbian, Sanskrit, Amharic, Tigrinya) to the Transliteration API . Using Google Transliteration you can convert Roman characters to their phonetic omschrijving ter your language. Note that this is not the same spil translation – it’s the sound of the words that are converted from one alphabet to the other.
Rendering custom-built gegevens te the Custom-made Search factor
April 13, 2010
Last year wij introduced Rich Snippets te Custom-made Search, permitting you to define your own custom-built attributes that wij’ll index and terugwedstrijd with your custom-made search results. A few months zometeen wij displayed you how to render some of thesis rich snippets te your Custom-made Search factor. Sure, this wasgoed a powerful way to let your visitors see thumbnails or interact with the results via deeds. But wij felt it wasgoed still too constrained. It is with excellent pleasure that today wij’re announcing that you now have total rendering control of all your metadata ter the Custom-built Search factor.
The results indeed hop out at you, huh? The thumbnails truly help users see what they’re looking at, but wij’ve shown you those before. Same with the Download activity linksaf by each result. But never before could you include arbitrary, per-result metadata with your Google Custom-made Search results so lightly. Notice the author, length, views and date information te each result. There’s even an icon indicating each result’s document type.
Here’s the Scribd.com sample, with only the default rich snippet inclusion:
It looks okay, but let’s make it better.
Restricting by licenses now available te the Photo Search API
April 12, 2010
I’m always amazed at the creative ways developers use Google’s APIs. I’m always pleased when wij are able to add a fresh feature to the API, spil I know that someone, somewhere will do something cool and unexpected with it. The latest addition is to the Photo Search API. You can now restrict results by various licenses applied to each picture.
Please come visit our IRC channel and support forum and let us know how you’ve used this feature te your webpagina or app!
Media RSS support added to the Feed API
April 8, 2010
More and more sites are adding support for MediaRSS to include pics, movies and other types of multimedia files. Today, wij’re announcing that the Google Feed API now includes this metadata ter the response. This content is now included te the JSON and XML results returned by the API. For more details on the result format, check out the documentation.
Helping you help us help you
March 31, 2010
Spil I mentioned te a previous postbode, wij’ve taken several measures to help differentiate legitimate API traffic from bad requests. To help us serve you better, I’m pleased to announce a fresh way for you to identify your request spil harmful. Beginning today, please include the &evil=true parameter te your API requests if you’re one of the bad guys.
Search Form and Results on Two Different Pages
March 16, 2010
One of the major advantages of an Ajax style search opbergruimte is that users can perform their queries and get their results without leaving the pagina. However, some webmasters choose that their users go to a separate results pagina after they come in a search. The Ajax search library supports this ",two-page", use case spil well, and since this is a question that wij see from time to time wij’ve set up a plain demo webpagina.
When the user submits the form, they are taken to a results pagina which has the following HTML structure:
Wij then tell the search library to draw its search opbergruimte and results te the div wij just created:
Since the user came to this pagina from our search form, their query terms are now part of the pagina URL, so all wij need to do now is samenvatting them and execute their query:
There is one more optional setting that you might be interested te. The 2nd pagina which wij’ve just created contains a search opbergruimte that will permit the user to perform searches on this same pagina. If you would choose for the search opbergruimte not to show up on this results pagina wij can add the following HTML to the pagina:
Wij hide the input opbergruimte because wij don’t want the Ajax search library to render the usual query input opbergruimte, just to voorstelling the results. Wij then tell the search library to draw its search opbergruimte te the hidden input, making it invisible:
To see an example of a two-page search setup with a hidden query input, visit this pagina.
To learn more about the Google Custom-made Search API, read our documentation. If you run into any problems while setting this up, postbode your question te our discussion group or hop on our IRC channel.