On 22 jan, 13:26, vdimitrov <[email protected]> wrote: > Hi > > I'm not really having an issue of some kind. I just have some general > question on how to approach GWT. > > 1) I recently read and experimented with the new declarative ui. > Despite being easier to maintain and faster to develop, does it bring > any performance drawback compared to the old programmatic approach?
Depends what you call "the old programmatic approach", but it'll do its best to never be *worse* than what you'd have written by hand (@UiHandler might be an exception, but it has also room for improvement in future GWT releases). > 2) Could you someone give me a hint when should a new Entry Point > class be created or in that matter - a new HTML page? It probably > depends mostly on my business logic, but still.. You'd generally stick with one EntryPoint per application (where an application generally means an HTML host page). Third-party libs might use an additional EntryPoint to do some early initialization/setup without the app developer having to care about it (I seem to remember that gwt-log does this) > 3) I'm using RPC services, and in cases when I have data table paging, > I need to make 2 calls - one to get the count of the results, and the > other one to get a page of results. Is there another way to > synchronize those calls other than nesting the second call into the > first ones onSuccess() method? Try to always do a single call (just return an object with 2 properties: the total count and the page of results) -- 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.
