On Friday, November 9, 2012 4:16:06 PM UTC+1, Joseph Lust wrote: > > I really enjoy the extension Library Detector for > Chrome<https://github.com/twistedpair/Library-Detector-for-Chrome>since I can > see what JS libs a site is running at a glance. However, it > does not support GWT. I've forked it to add this functionality and have > been trying to think of a good method for testing that a site is using GWT > since in reality it is not a library but a framework. > > So far I've got: > > 1. Look for *.nocache.js files in body - but this could trigger on non > GWT sites if someone likes that name/scheme > 2. Check for the __gwt_historyFrame iFrame - sounder > > I think method 2 should be sufficient, >
Google Groups or Blogger have neither of them. > but know there must be a more robust way. Thanks. > My method is to search for $gwt_version somewhere in the resources, but I have no idea if/how that could be done in this extension. Just try it on Google Groups, Blogger and your own GWT app (assuming you're using a built-in primary linker) and you'll find 3 different things. Another method is to look for the gwt_uid (generated by Document#createUniqueId(), itself used extensively by UiBinder and CellTable), __gwt_activeModules, __gwt_stylesLoaded or __gwt_scriptsLoaded (all three set by *.nocache.js, unless a custom linker has been used). You'll find out none of Groups or Blogger has the former (which I must say is a bit strange), Groups has activeModules and stylesLoaded, while Blogger has stylesLoaded and scriptsLoaded (uses a custom linker; Groups looks like it uses the xsiframe linker). -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/5wuFY8WP0OwJ. 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-web-toolkit?hl=en.
