Thanks. I am aware of SOP so that shouldn't be a problem. I got what you mentioned working easily, but it actually led to a different problem as follows:
The main screen of this app I am working on has a standard div along the left border, and a standard div on the top border of the screen. The remaining portion gets replaced by state dependent UI code. There are about 500 different ones! Each has its own layout, logic, and REST services. Naturally I can't compile that into one big JS file. I'd like to code the standard parts in one JS file, and each of the remaining 500 screens each in it's own JS file. This way I can edit/compile and load each separately. Can and how can I do that? Thanks! Blake On Sun, Feb 8, 2015 at 10:27 AM, Jens <[email protected]> wrote: > A compiled GWT app is just HTML + JS, so nothing special. That means you > can simply upload it to a web server and it will run. However you need to > take care of the same-origin-policy restriction in browsers when doing your > REST requests to the backend. How you do that kind of depends on how you > plan to deploy the frontend and how the backend is deployed and reachable. > > -- J. > > -- > 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/d/optout. > -- 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/d/optout.
