Chrome/Firefox Plugins made with GXT
Hi, I was planning to create either some Chrome or Firefox plugins. I was wondering if there is any experience in migrating an existing extGWT application as a Chrome/FF plugin or maybe creating it from scratch with extGWT. Maybe any related tutorial could be enough?
What about ExtJS?
example of client side working
Here is a good example where the client side works out of the box for the GWT sample app created by Eclipse GWT plugin.
It would be great to know what is needed to add in the manifest.json to make also work the GWT RPC and therefore the server side.
Does anyone know what permission is needed in the manifest for this task?
Would you expect any difference to make it work for GXT?
remove the iframe
My last findings on this here:
it looks that a small template application is needed to run GXT/GWT apps as Chrome extensions.
The only requirement looks to get rid of the iframe created on the template app by Eclipse plugins.
Possibilities looks great to create GXT enabled Chrome extensions. Any help?
Are you asking how to remove that iframe from the template? I'd just make another template that doesn't have it. The iframe is optional anyway, esp since a browser plugin is not going to have back/forward buttons to need that kind of history management.
From the linked blog post at http://hello-its-crazy.blogspot.com/...using-gwt.html there is a discussion on using the sso linker to avoid the second iframe - I suspect the xs linker will also work, in place of the sso linker.
Once any GWT app works as a browser extension, I would be surprised to find that including GXT adds any difficulty at all. All GXT code just uses existing ideas from GWT and extends them to build its components and tools.
no an iframe issue
Hi Colin, yes, thanks, you are correct. The iframe is an optional, element just for the history functionality.
I also tried by adding:
<add-linker name="xs" />
to the XXXX.gwt.xml file apart from the
<add-linker name="sso" />
Right now is not throwing any exception but it does not either connect to server side. The issue is still open.
Is a pitty because I can imagine great GXT Chrome extensions, but a template app, as a pattern, would be still needed. Not sure if currently is yet possible because the link and changes done by Chromium team. I will update the thread when I find out more information.
What server side should it be connecting to? Are Chrome extensions not subject to the Same Origin Policy that normal websites are? If the page loads from one domain (i.e. the local folder where the extension is stored) and connects to a remote site (the 'server'), that may not be allowed under the S.O.P.
Other options to consider include JSONP and CORS if that is the problem.
Tags for this Thread