I have a large GWT app which unfortunately is slow in some old browsers I need to support (IE7). A major part of the slowness is my architecture - I am using GWT-RPC to download model objects from the server and then building a large HTML table in the browser using GWT Widgets. The table is not fancy - just text, links, and images - but it can get pretty big.
I'm considering fixing this by building some of my HTML on the server and then downloading it over GWT-RPC as a string, and injecting it in to the DOM using setInnerHtml(). I will still have to do some manipulation later in the browser though (my UI refreshes periodically in the background). What I would really like would be to write my code in such a way that I could decide at runtime if it was best to build the table on the server or in the browser. Elemental looks like a promising way to do this - it would not be hard to generate a server-side implementation of the Elemental HTML interfaces that built up an HTML string, and then send that string over the wire to be injected in the browser. My application logic would only interact with the Elemental interfaces, so I could decide at runtime which implementation to use. Does this sound reasonable or am I barking up the wrong tree here? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/pvkfPkKiSY0J. 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.
