The gadget server is what has the direct access to fields like title (the metadata), but the gadget server does not make your gadget's chrome (the outer parts like the title bar, settings button, etc). So when your container starts making the chrome around a gadget, it needs to contact the gadget server to get the metadata from it. This can either be done directly (XMLHttpRequest) or indirectly (your webserver does the http request, passing back the results to your page).
javascript/container/sample-metadata.html is an example of doing it directly using XMLHttpRequest, but it only works if the gadget server is on the same origin as the container. More likely (like in my case) you'll have to do this request indirectly by having your webserver make the http request to the gadget server. Once your webserver receives the json metadata response, it passes it to the container javascript for use. -Tim On Wed, Jun 4, 2008 at 11:37 PM, Tyrell Perera <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I'm writing a dashboard page using the Shindig samples as a guideline > and noticed that the 'Title' attribute defined in a gadget xml is not > read (at least in the sample container pages). > > Is there a way to get the value given in the title attribute to be > displayed in the UI widgets title? > > thanks, > Tyrell > > > - -- > Tyrell Perera > Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/ > email: [EMAIL PROTECTED]; cell: +94 77 302 2505 > > "Oxygenating the Web Service Platform." > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFIR4m8ehFdPcgGx7oRArhDAKDPcOQwpnGtZkCj9NLEIQoiYye6CACguKuI > Q3/kwbUj9sq/PzjSttVQzhw= > =Dq8a > -----END PGP SIGNATURE----- >
