Other links: [[:/#drupal_gadgets]]

====== Suggestions for child modules ======

2007-07-29: dmitrig01 details some of his ideas regarding the distribution of work between the google_gadgets meta-module and gadgets actually supplying gadget content using the google_gadgets services.

  * In the module's hook_install, the modules supplying additional gadgets set up an fapi-like array, and call google_gadgets_save($gadget)
  * the google_gadgets module stores stuff in the database
  * and it will do menu sstuff for you, including defining callbacks and all that stuff
  * all you have to do is 
    * provide output, in which case the module would do absolutely nothing besides having to do with google_gadgets besides the hook_install
    * provide a callback function which returns HTML to display, including a pref api like:
<code php>
google_gadgets_get_preference()
</code>
  * I had a similar idea for several modules