thx again - didn't know about that. (i can't shake the feeling that google has some good engineers)
On Thursday, 8 March 2012 15:50:01 UTC+1, Thomas Broyer wrote: > > > On Thursday, March 8, 2012 3:28:18 PM UTC+1, tanteanni wrote: >> >> thx thomas (you seem to answer all "a&p" questions of the world) >> >> so you mean i have to provide an implementation (rather then an >> extension) of "PlaceHistoryMapper"? will @WithTokenizers work on that? Or >> do i have to implement all stuff for all places? or to make it simple (at >> least for me ;-)) could you probably give me a draft of " >> PlaceHistoryMapperWithFactory". > > > I meant using that one: > http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/place/shared/PlaceHistoryMapperWithFactory.html > > You use it the exact same way as PlaceHistoryMapper (you can use > @WithTokenizers too) except you have to provide a factory via setFactory() > before you can use it. the generated implementation will call methods of > the factory instead of instantiating tokenizers, when needed. This is > mostly useful when you have to somehow inject dependencies into your > tokenizers (and note that the factory could be your Ginjector; the > generator only looks at zero-arg methods returning subtypes of > PlaceTokenizer) > On Thursday, 8 March 2012 15:50:01 UTC+1, Thomas Broyer wrote: > > > On Thursday, March 8, 2012 3:28:18 PM UTC+1, tanteanni wrote: >> >> thx thomas (you seem to answer all "a&p" questions of the world) >> >> so you mean i have to provide an implementation (rather then an >> extension) of "PlaceHistoryMapper"? will @WithTokenizers work on that? Or >> do i have to implement all stuff for all places? or to make it simple (at >> least for me ;-)) could you probably give me a draft of " >> PlaceHistoryMapperWithFactory". > > > I meant using that one: > http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/place/shared/PlaceHistoryMapperWithFactory.html > > You use it the exact same way as PlaceHistoryMapper (you can use > @WithTokenizers too) except you have to provide a factory via setFactory() > before you can use it. the generated implementation will call methods of > the factory instead of instantiating tokenizers, when needed. This is > mostly useful when you have to somehow inject dependencies into your > tokenizers (and note that the factory could be your Ginjector; the > generator only looks at zero-arg methods returning subtypes of > PlaceTokenizer) > -- 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/-/RVHA7szPoE4J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
