Hi Rob, In my case, because I could not afford waiting for a solution coming from Google, I immediately moved all my gadgets to JS/Ajax loading instead of server-side handling.
I am still surprised by this important change without any notice. How can the team decide such changes without imagining the consequences for the gadgets? All I need now is consistency from the API. Are we sure that this change is definite? How will you now distinguish the difference between content and URL gadgets? They are now very similar because they will both load content that depends on user prefereces through Ajax , except that content gadgets are cached by Google servers and that content gadgets have to deal with cross-domain concerns. -- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
