FWIW A couple of years ago we decided to move away from GWT and move
to react+mobx+typescript under the assumption we could produce apps
faster. After several months in that world, we came back to the GWT
world. Mostly this was due to productivity.
Except for some legacy applications we don't use
Thanks Howard.
Definitely not planning a deep integration...
Interesting insight about GWT vs JS in terms of productivity. GWT always
felt 'enterprise' to me with large apps in mind.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To
Similar situation. Our single page app SPA is actually made up of many
separate sub pages, thus we stayed with GWT root and "injected" Angular by
adding new url/page in Angular, and thus breaking the SPA experience a bit
but we try to pass some info over to make it less jarring and more
It does somehow. I reminded myself of that today as well. Guess it just
feels unusual to me at this stage. Also investigating the iFrame option.
On Tue, 21 Apr 2020 at 20:23, Michael Conrad wrote:
> Don't know if this will help, but you can set the rootpanel for a GWT
> component using an id,
Don't know if this will help, but you can set the rootpanel for a GWT
component using an id, say on a div tag.
On 4/20/20 8:00 PM, Thomas wrote:
Thanks Jens. If I paraphrase in my words, you would keep the "shell"
(menu items etc) and have iFrames for new functionality?
Sounds like a
Thanks Jens. If I paraphrase in my words, you would keep the "shell" (menu
items etc) and have iFrames for new functionality?
Sounds like a reasonable approach, although I'd prefer to have the "shell"
in the new technology and have iFrames for the old GWT modules.
Have you come across any
Kind of in the same situation and I figured that using an iframe approach
is probably the best idea. So you would need to refactor your app in a way
that you can launch an external application in an iframe for a given menu
item, basically the content area in your app should be an iframe. That
