On 1 déc, 21:36, Brian Reilly <[email protected]> wrote: > I haven't done this in a real project yet, but I was experimenting with > something similar. I think I was able to get this kind of behavior by > wrapping the ActivityMapper implementation in a CachingActivityMapper and > wrapping that in a FilteredActivityMapper. The idea is that the filtered > activity mapper recognizes some places (like detail views) and changes them > into whatever place invokes your list activity. Then, the caching activity > mapper, having already seen an equivalent place, doesn't invoke the wrapped > activity mapper since the display region is already showing that place. > > It seems rather roundabout to me, so I don't know if this is the best way to > do it, or if this is exactly what Caching/FilteredActivityMapper are for > (the documentation is pretty light there). I'd appreciate if others could > chime in with agreement or other options.
That's the exact use case for FilteredActivityMapper and CachingActivityMapper (and how they're used AFAICT in "scaffold" applications generated by String Roo for the "master" activities). Of course you could do the exact same thing right into your ActivityMapper (the need here is to return the same Activity instance, so te ActivityManager will detect it and won't do the stop/start dance); you'd however loose a bit of "separation of concerns". -- 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.
