Hi Thomas, I have something similar like you, I think. Okay, first .. YES, you have to define a new gwt.xml file, if you want to use your module on the clientside of your "main"-module.
I don´t exactly know, but I think not, that an extra js is created, You have to make your new module visible to your "main"-module, and I think the java-to- js compiler makes one file, but as I said, I dont´t exacly know. I decide, which module is displayed, by what the user wants to do. If you develope your App using MVP-Pattern, so you just can create an Event, and hanlde it in the App-Controller. There you can just flush your desired container, and create a new Presenter of your new module/View, and just show it. So thats it. If you don´t use MVP-pattern, you should change to MVP, it will cost you a few hours to understand MVP and convert your Project to MVP, but your code won´t end up in a mess. So I hope this helps. Greets Alex On 26 Aug., 10:42, Thomas Van Driessche <[email protected]> wrote: > Hi All, > > I need another module in my gwt project. > Do i need to define a new gwt.xml file? > > And how do you descide which module gets displayed on the page, > because it needs to be dependent from something so i can choose which > module i need to work with... > > Does each module have a different js file? > > kind regards -- 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.
