List of Figures | Mining Google Web Services: Building Applications with the Google API

Chapter 1: Learning About Google Web Services

Figure 1.1: Use the Google Advanced Search page to get a feel for the power of the Web service.
Figure 1.2: Informational searches help you learn more about a Web site before you visit.
Figure 1.3: Cached data searches can be very helpful, especially during research.
Figure 1.4: You can obtain both the kit and the developer license on this site.
Figure 1.5: View example files using Internet Explorer or other XML-compatible browser.

Figure 2.1: The Google home page provides access to a simple search as well as tools and services.
Figure 2.2: The Google Advanced Search page helps you learn about special searches.
Figure 2.3: The Google Advanced Search page helps you learn about special searches.
Figure 2.4: Use URL searches to locate sites that have specific areas that match your keywords.
Figure 2.5: Locate related sites using the related links search.

Figure 3.1: Internet Explorer and other browsers can display XML files in a variety of ways.
Figure 3.2: Many XML editors provide a tree view display that experts like.
Figure 3.3: Netpadd provides an easy to understand display of the XML file.
Figure 3.4: View your XML files in various ways using Netpadd's View commands.
Figure 3.5: XMLwriter 2 uses a document style editor, but provides many features found in high-end products.
Figure 3.6: Select a tree view to see the overall layout of your XML document.
Figure 3.7: The example program shows how you can perform URL encoding.
Figure 3.8: Character Map makes it easy to learn the numbers associated with special characters .
Figure 3.9: The results of using a script to transform XML data received from Google.
Figure 3.10: An illustration of a typical SOAP message.
Figure 3.11: The kit contains a number of SOAP message examples.
Figure 3.12: Using WSDL makes SOAP messaging extremely easy for the developer.

Figure 4.1: This example shows typical spelling check results.
Figure 4.2: Use a tree view of the Google search results to understand the structure of the data you receive better.
Figure 4.3: Always check the assumptions you make about browser compatibility against a reliable chart.
Figure 4.4: Sometimes you can translate a limited amount of text free.

Figure 5.1: Use the Insert Hyperlink dialog box to add a hyperlink to your application.
Figure 5.2: Older versions of Office might require that you create hyper-links using the menu system.
Figure 5.3: The References dialog box helps you add an object library reference to VBA.
Figure 5.4: The resulting spreadsheet contains links to the sites you queried online.
Figure 5.5: Using hyperlinks within Excel makes it easy to move back and forth between spreadsheet and Internet connection.
Figure 5.6: Placing the buttons within the worksheet cell positions makes it look like the button is part of the worksheet.
Figure 5.7: The output chart shows how you can mix Google and locally created data.
Figure 5.8: You can easily download cached pages from Google for comparison purposes.
Figure 5.9: Use the Web Service References add-in to make using SOAP easier.

Figure 6.1: Add a reference to the appropriate type libraries using this dialog box.
Figure 6.2: Typical output for a Google search when using this application
Figure 6.3: Use the Components and Controls dialog box to add SOAP, XML, and FlexGrid support.
Figure 6.4: The Confirm Classes dialog box shows which classes the IDE adds to support the FlexGrid.
Figure 6.5: Use the Trace Utility to discover the true form of messages passed between your application and Google.
Figure 6.6: The high-level API automatically generates a request very similar to low-level API request you can create manually.
Figure 6.7: The Add Web Reference dialog box helps you create a connection to Google Web Services.
Figure 6.8: Scroll through the list of Google Web Services methods to learn more about it.
Figure 6.9: Check Solution Explorer for the new Web reference once the IDE finishes its work.
Figure 6.10: Use the example application to learn more about what Google Web Services can do.
Figure 6.11: Typical output for the Visual Basic .NET Search example
Figure 6.12: Output from the caching application demonstrates that a local cache is faster than calling Google Web Services.
Figure 6.13: Use the dgGoogle Properties dialog box to configure the DataGrid columns .
Figure 6.14: ASP.NET can produce an application with an appearance similar to a desktop application.

Figure 7.1: You can get great results from a site-specific search.
Figure 7.2: Providing multiple pages of results will make users happier , but uses up your Google search requests .
Figure 7.3: The WinMySQLadm in utility validates the success of the script on a Windows machine.
Figure 7.4: Using cached search data has a number of benefits for online users.

Figure 8.1: The Google example program outputs text to the command window.
Figure 8.2: The Google API works well for many of the requests you'll make.
Figure 8.3: Select a project type from the list of options.
Figure 8.4: Define one or more libraries as needed using the Required Libraries tab.
Figure 8.5: Add library paths or archives using the Set Library dialog box.
Figure 8.6: Make sure you always check the libraries that you want to use with your project.
Figure 8.7: A standard search works equally well with the Google or a third party library.

Figure 9.1: Use the options in this dialog box to choose a deployment option.
Figure 9.2: Configure the emulator to better model the mobile device you want to use.
Figure 9.3: Test each of the emulators to ensure they work.
Figure 9.4: Select custom options as needed for your emulator setup.
Figure 9.5: Using the Openwave emulator means starting the associated IDE and entering an URL using a menu command. Image courtesy Openwave Systems Inc.
Figure 9.6: Use the 5.1 version if you need an IDE in addition to the emulator. Image courtesy Openwave Systems Inc.
Figure 9.7: Create a complex emulator environment using the Smartphone Development mode.
Figure 9.8: Fine-tune the display details and perform final testing using the Display mode.
Figure 9.9: The detail page shows all of the links returned from the search.
Figure 9.10: The code automatically updates the main page with the estimated number of results and a new start index.
Figure 9.11: Typical output when working with a Web-based application. Image courtesy Open -wave Systems Inc.

Figure 10.1: You can use a standard Microsoft Web Browser control to display the results.
Figure 10.2: Cached pages are relatively easy to use once you convert the data.

Figure 11.1: High contrast displays can make some information unreadable.
Figure 11.2: Make sure you generate a compact policy for Web pages that have cookies.
Figure 11.3: Encoding your survey form correctly lets you read it directly in email.
Figure 11.4: Typical output from the combined Web services application