Date Added August 26, Version 2. Operating Systems. Additional Requirements None. Total Downloads 16, Downloads Last Week 1. Report Software. Related Software. Core Temp Free. Monitor your processor temperature via a graph at the bottom of the gadget. Yahoo Widgets Free. Add standalone applications that provide a variety of features and content. Colorblind Assistant Free. Pick color from the mouse pointer and get its name, RGB, and hexadecimal values. CrossHair Free. Show full-screen lines intersecting your mouse cursor for aligning objects in design applications.
User Reviews. Google Chrome Free. Make the most of the Web with impeccably optimized, personalized, synced, and secured browsing. Google Play Free. Find, enjoy and share your favorite music, movies, books, and apps. Google Earth Free. Explore the entire world from above with satellite imagery, 3D globe terrain, real environments, and structures.
Make the most of the Web with optimized, personalized, synced, and secured browsing. Google Meet Free to try. Connect with your team from anywhere. Google Chrome bit Free. Explore the Web using Google's super-efficient, personalized, synced, and secured browser. Google Chrome Portable Free. Load Web pages, run diverse Web applications, search, navigate, and customize in a snap. Google Chrome OS Free.
Experience instant Web browsing, applications, and secured data management on your computer. Warning : Gadgets built with the legacy gadgets API may work in Sites but are not officially supported. Built-in and feed-based gadgets are similarly not supported. Therefore, Google recommends you build all Sites gadgets using the current gadgets.
Here is a simple but popular Include gadget that does little more than provide an iframe for passing through other web content:. See Getting Started: gadgets. Regardless of what your gadget does, its files must reside on the World Wide Web to be found and used.
Any online location accessible over HTTP without authentication will do. Just remember, your gadget will have to be published in a public directory to be selected. Otherwise, users must embed it by directly inserting its URL. If you put all of the gadget files in the static directory, you may then edit the files on your local directory and deploy to App Engine each time you make changes.
The Gadget Developer Guide provides all necessary details for building your own gadgets. In addition, OpenSocial templates may be used to quickly build social applications in gadgets. Gadgets can be embedded in Sites pages either by selecting it from the Sites gadget directory which is synchronized with the iGoogle gadget directory or by including its URL directly.
After building your gadget, you should test it thoroughly before using it and allowing others to do the same. Test your gadget manually by creating one or more test Google Sites and embedding your gadget. See the Embedding your gadget section for precise steps. The functionality and appearance of your gadget depends on the site that contains it. Therefore, the best way to debug your gadget is to test it in the context of an actual Google Site. Try switching between various Sites themes to ensure your gadget appears correctly in each.
As you test your gadget, you'll inevitably discover bugs and need to make corrections to your gadget. You should disable gadget caching while you're tweaking the XML. Otherwise, your changes won't show up on the page. Gadget specs are cached unless you tell Sites not to. To bypass the cache during development, add this to the end of the Sites page URL containing the gadget and not the URL of the gadget spec.
Sites provides a standard UI for adding and configuring gadgets. When you add a gadget, it will display a preview and show any UserPref parameters that can be configured. Test updating various configuration values and adding your gadget to your test site. Confirm your gadget works as expected on the site itself.
You should test that any UserPref you've defined can correctly be configured by the site administrator. Then refer to the Preparing for Publication section of Publishing Your Gadget for other tests to carry out. All gadgets may offer the ability to set basic user preferences, done through the UserPref section of the gadget spec file.
These typically affect dimensions, scrollbars, borders, titles and gadget-specific settings, as depicted in the screenshot here:. But there are many cases where gadgets benefit from more advanced preferences than the standard UserPref components offer.
Preferences often need to include features like custom business logic, validations, or pickers. The interface generated from the gadget UserPref sections supports a limited number of datatypes string, enum, etc. Further, in containers like iGoogle where the viewer and editor are the same, gadget authors can extended configuration as part of the standard view. In Sites, the viewer is not always the editor, so the gadget author can't guarantee the viewing user has access to update preferences.
Social containers such as Sites cannot allow any user to modify the preferences, only the author. In Sites, the basic gadget preferences interface generated by UserPref can be replaced by a configuration view where many additional preferences and data types may be supplied, as in the screenshot shown here:.
0コメント