Communicating between modules directly is also a solution, but not so applicable in my case. As i said i have a application Controller that handles history, initialize and keep track of opened presenters. I could get rid of this app controller and replace it with some place handler mechanism from gwt platform or mvp4g libraries. I tried them but they were not exactly for my needs. For example u can pass parameters to a new place but they have to be serializable.
But regarding those two approaches, which one is better. I have some performance problems with my application. Target device has very low hardware resources and is moving pretty slow. Initially i was using gxt library but it was to slow and i get rid of it. Now i'm using pure gwt + a custom gwt table (inherited from incubator). But still is very slow. -- 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.
