Re: Best practice to implement hash bang tokens in activities and places keeping @WithTokenizers

Thanks for the quick reply.

Some of my thoughts regarding the different options.

1) @Prefix
- Since the hash bang is part of a a global scheme and the @Prefix a personal attribute of a Place, I don't feel comfortable to add it there.

2) Extending DefaultHistorian
- This does not 'force' the developer to use hash bang notation in hrefs (i.e. of anchors in UiBinder), and a crawler would miss those links. 

3) Extending PlaceHistoryMapper
- maybe I did actually find a good solution at 2am ;-)
- outlined in the my post above

best -R

 

But that's the easiest part of the #! story…

so true ;-)

--
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/-/Qs_EinOopSYJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.