I am not sure I understood well but it seems that you loaded the GWT app in a webview or something similar. That is not what I meant. I'd like to be able to invoke the chrome.* apis from my GWT app (after I wrap them). I tried this by modifying the Browser sample app<https://github.com/GoogleChrome/chrome-app-samples/tree/master/browser>. I modified the browser.html file to load the GWT app. The GWT app is trivial, just an entry point with a simple JSNI method that logs a simple message via console.log (this part shouldn't break CSP). I tried with and without the DirectInstallLinker, the result is a bit better with the linker (it reports fewer errors in the app console) but it does not work either way. I didn't get the part about the "loaders". Thanks for your help.
On Sunday, February 9, 2014 3:18:42 PM UTC+1, Andrew Mackenzie wrote: > > I've developed a Chrome extension using mainly GWT, but it's mostly loaded > by the extension remotely (loading JS handcrafted). It's mainly a > build/packaging problem. GWT will build the JS for you and the "loaders" > then you have to include into your extension file hierarchy in your build, > and load as you desire. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
