Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I'd go with History tokens. It's the standard way of handling such situations. I don't understand though, what you mean by "It is hard to produce a human friendly URL with history tokens" - they seem pretty human friendly to me :) And if you use servlets for handling urls, I think that would cause the whole page to be reloaded - something which I think you'd rather want to avoid.</p> <blockquote> <p>Second, I'm using gwt-presenter and this approach would mean that we need to support subplaces in one token, which I'd rather avoid.</p> </blockquote> <p>If you are not satisfied with gwt-presenter (like I was :)), roll out your own classes to help with MVP - it's really easy (you can start from scratch or modify the gwt-presenter classes) and you'll get a solution suited to your needs. I did precisely that, because gwt-presenter seemed to "complicated"/complex to me - to generic, when all I needed was a subset of what it offered (or try to offer).</p> <p>As for the multiple modules idea - it's a good one, but I'd recommend using <a href="http://code.google.com/webtoolkit/doc/latest/DevGuideCodeSplitting.html" rel="nofollow noreferrer">Code Splitting</a> - this type of situation (pages/apps that can be divided into "standalone" modules/blocks) is just what it's meant to be used for, plus you bootstrap your application only once, so no extra code downloaded when switching between pages. <em>Plus</em>, it should be easier to share state that way (via event bus, for example).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload