Rob, you mention that the legacy API will be deprecated in September. However, on 17th of December last year Dan posted the following on the developer blog: "Since the migration tool isn't yet available, we've decided to delay the next step of the migration process, the requirement that all new gadgets be written using gadgets.*, for an indefinite period. So, while we still recommend using the gadgets.* API, as it will save you time later, we're holding off on this requirement. Stay tuned for another update on the migration process, with a link to the migration tool, in early 2010."
>From this post I deducted the whole deprecation was paused till further notice. Although most of our gadgets are already migrated, we planned the migration of one (important to us) gadget after September because of some testing. Can you shed some light on this? Thanks in advance! Kind regards, Rik On 26 mrt, 02:31, Rob Russell <[email protected]> wrote: > For anyone that doesn't subscribe to the blog (and you should!), Dan H built > a tool to help anyone still migrating their gadgets from the deprecated _IG_ > api to the current gadgets.* > apihttp://igoogledeveloper.blogspot.com/2010/03/migration-made-easier.html. > The tool source is also available under the Apache license > athttp://code.google.com/p/gadget-migration/. > > Don't forget that the legacy _IG_ API won't be supported after this > September, so if you're still relying on the old API then get started on > your migration. > > Rob Russell > Google Developer Relations -- 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.
