Using Scheduler.scheduleDeferred vs DeferredCommand.addCommand()

311 views
Skip to first unread message

Joseph Lust

unread,
Jun 10, 2012, 7:04:43 PM6/10/12
to google-we...@googlegroups.com
For anyone that is knowledgeable, I noticed that with the wave of 2.5 release changes in the GWT trunk this weekend there were a number of places where code was switched from using DeferredCommand.addCommand() toScheduler.scheduleDeferred(). There was no mention in the comments on why this was changed and what the proper use case is for each. Ostensibly, the two commands are very similar according to their Javadocs. Does anyone know why this is and what devs on the forum might need to do to their existing DeferredCommand implementation? Thanks.

Effected checkins
#10996
#11005
#11010
#11011
#11012
#11013
#11014
#11021

Joe

Thomas Broyer

unread,
Jun 10, 2012, 9:53:40 PM6/10/12
to google-we...@googlegroups.com
DeferredCommand has been deprecated since Scheduler was added. Patrick Tucker submitted a bunch of patches to remove those uses of a deprecated API.
This is not something coming from Google, so don't see a sign or anything behind it, it's coming from an external contributor.

Be prepared though that a bunch of deprecated APIs will probably be removed in the next months, in order to clean-up the code base: event listeners, com.google.gwt.event (with a breaking change in Activities), many c.g.g.u.c.DOM methods, etc. SO if you're still using DeferredCommands, you should probably start slowly moving them to Scheduler.
Reply all
Reply to author
Forward
0 new messages