Hello everybody, We are about to start the migration of a huge desktop application to GWT and we faced the following problem.
Application has a main module and about 20 different big submodules (almost independent and isolated from each other). These submodules are started from this main application. They all are based on the same framework though. We see two different ways to migrate it : 1. Make this submodules to be huge widgets and insert them somewhere (let's say in a TabLayoutPanel) in the Main module. 2. Make this submodules completely independent modules with their own entry points and run them in an <iframe> in the same TabLayoutPanel. For the first approach, as there is no reflection in GWT, main module must know directly all the submodules in order to start them. That's bad. But there is a significant economy of downloaded code and resources and you can easily enable communication between submodules, if it is necessary. For the second approach each submodule will start from scratch in it's own <iframe> and re-download a framework again and consume more resources and there will be troubles in establishing communication between submodules. But main application will no nothing about them and will be able to start them by simply launching say "submodule/ submodule.html". So, is there a way to combine advantages of both approaches? (i.e remove dependencies from the main module, enable normal communication, reduce size, etc) Are there any other ways to do it, or which approach would you pick? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
