Comments (2)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 DavidDhuyvetter commented Permalink

No code is ever complete. :-)

 
It turns out that calling WL.Logger.debug() in the widget startup code is a problem because if the widget is on the default page of the app (as it is in this case) then the widget startup code gets called before WL.Client.init() runs. This will result in an exception on Android 2.2.
 
I've updated the project interchange, replacing WL.Logger.debug() with console.log()

2 David Whitehouse commented Permalink

Great post!

 
I look forward the the jQuery version.