On Apr 6, 9:52 pm, Matt Kruse <[email protected]> wrote: > The Google-developed gadgets continue to work in inline mode. Why? If > your developers had to play the same rules as all the other > developers, we would either see a return to allowing inline gadgets or > much-improved API capabilities.
On Apr 6, 11:11 pm, "Vision Jinx (Guru)" <[email protected]> wrote: > I do strongly feel that Googles developers should have to play by the > same rules as us Dan, I think it's quite telling that iGoogle's most loyal, experienced, and evangelistic developers all share this view. The double standard of inline support (even if it is mostly about latency) sows resentment and an "us versus them" mentality among gadget developers. Matt also has an excellent point when he suggests that eliminating inlining for everyone would encourage improvements to the API that just don't happen now. When you deprecated inlining, you suggested that this might occur, that features which had been available via inlining would be built into future versions of the API. Has this happened at all? Like Vision, I do want to stress that this isn't aimed at you personally; you do an excellent job of keeping us informed, and I thank you. However, for a company with such a strong developer connection, Google Inc. can be remarkably insular when it comes to the developer-related actions they take. This is an example of it here, and it's endemic in the Themes, Android, and Gadgets for GMail communities as well. String --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
