On Sun, May 14, 2017 at 1:39 AM, <[email protected]> wrote: > An alternate related approach is to look at the implementation of TM, and > advance that as TM did with GM. How did they implement asynchronous > functions for the webextensions API? Learn from the TM folk in terms of > how they went about their GM fork. They must already be supporting async > calls in the API already, given its webextensions-based anyway. >
Tampermonkey is not open source, so I've got no plans to try to "take" from it. Where I've heard other people describe it, it sounds like they've made compromises to provide compatible calls. Ones I'm not excited about emulating. On Sun, May 14, 2017 at 5:15 PM, jscher2000 <[email protected]> wrote: > Given this current pattern: > > var sData = GM_getValue("serialized"); > var oData = JSON.parse(sData); > // useful things happen here > Good point. If we go all-new async (2.2), I'd expect this would turn into something like: GM.getValue("serialized").then(sData => { var oData = JSON.parse(sData); // useful things happen here. }); Which is a change, but hopefully not a huge one. -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/greasemonkey-users. For more options, visit https://groups.google.com/d/optout.
