On Apr 6, 3:25 pm, "Dan (Google)" <[email protected]> wrote: > I'm sorry that your gadget has been disabled, but the deprecation > process has been public for some time now (http:// > igoogledeveloper.blogspot.com/2008/08/changes-to-inlined- > gadgets.html)
I'm obviously aware of this, but to quote the page: "All other inlined gadgets will continue to operate, but the gadget XML will be in read-only mode, served out of Google's cache. It will still be possible to update these gadgets, by filing a request to recache the gadget in the legacy issue tracker. We strongly recommend that the authors of these gadgets move to supported APIs." I thought the part about "all other inlined gadgets will continue to operate" meant that they would continue to operate. > The fact that inline is required in your > case, suggests, at least to me, that the gadget demonstrates > particular behavior that we weren't encouraging as part of the gadgets > API. Obviously, but as I've said before, you are discouraging community improvement to the iGoogle portal by eliminating the ability for skilled developers to enhance the experience. Since the API is very static and features are added/fixed very slowly (if at all), the gadget platform has become less than thrilling to develop for. Even this group has become pretty dead. > In short, in order to provide a consistent and secure experience > for iGoogle users, some inlined gadgets will need to be disabled. I don't buy this argument. Keeping inline gadgets such as mine that I rely on (along with 500 other people) would certainly hurt no one else's "experience". You should just say that it needs to be done to lock down functionality and to make sure that gadgets can continue to be embedded in gmail, gcalendar, and everywhere else you want them to be ported to. 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. > Have you thought about using Greasemonkey for customization? I use a variety of browsers across different machines to access iGoogle. That's one of the main benefits of it for me, so fixing functionality using GM wouldn't be a good solution. I'm also not sure that the same functionality would be possible with GM, or that the time invested would be worthwhile. Just compare the before screenshot: http://mattkruse.com/wp-content/uploads/2008/11/igoogle01-whole-page-8x6.png to the after screenshot: http://mattkruse.com/wp-content/uploads/2008/11/igoogle07-minimized-arrow-8x6.png You're sending me from #2 back to #1 by disabling my gadget! I wouldn't be so annoyed if the default RSS behavior on iGoogle wasn't so horrible. It took me one day to write my RSS Customizer gadget. I would love it if Google would invest a few hours into making their RSS interface more usable. I know that Google Reader is supposed to be God's Gift To Humanity, but I still prefer to get my RSS content through iGoogle along with all my other junk. :) Matt Kruse --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
