often your places are "parameterized", think of a detail/edit screen for example that needs the model's id. The token is a generic way to provide additional information (via the URL) to the place (i.e. the activity/-ies), i.e. "#editFoo:42". You can of course re-use one place to dispatch to several activities based on the token. See the (currently not used) for ProxyPlace and ProxyListPlace in the Expenses sample for an example.
Group items tagged
GWT 2.1 hellomvp using GIN - Google Web Toolkit | Google Groups - 0 views
-
The way we're minimizing code right now, is by creating some useful abstract tokenizers that handle the common use cases (no parameter tokenizer, key-value pair tokenizer). With those there are corresponding abstract tokenizers that handle creating the hashCode and equals methods. Aside from the 1:1 between Place and Activity, which bothers me in principle but may not be a practical concern just yet, it's coming along pretty nicely.
How to change the panel in Activity.start() - Google Web Toolkit | Google Groups - 0 views
-
there's absolutely nothing in GWT proper related to MVP actually; I refuse to call Activities an "MVP framework", it has nothing to do with MVP in my opinion
-
navigation (Places and Activities)
-
try to disconnect activities from MVP: Activities don't force you to do MVP, and you'll use MVP beyond Activities.
- ...4 more annotations...
GWT 2.1 hellomvp using GIN - Google Web Toolkit | Google Groups - 0 views
-
although we can't map a 1-Many relationship between a Place and an Activity, you can in fact map multiple places to the same activity and differentiate between the place with multiple init() methods in the activity.
« First
‹ Previous
81 - 100 of 191
Next ›
Last »
Showing 20▼ items per page