Looks nice although I think the real way GWT should go is to implement the Windows 8 approach. If you write an application for desktop and mobile all you need is:
- Device.isTouchEnabled() // although I am not sure how to obtain that information which allows you to swap out widgets that are more mouse or more touch friendly (e.g. change vertical mouse wheel scrolling to horizontal swipe scrolling) and - widget.addPointer[up/down/move/../../..]Handler() which is an abstraction layer of user input so it does not matter if its a touch device or not. Regardless of device type these pointer events will fire as fast as possible. Using GWT, on desktop you emulate them using click events, on iOS/Android you emulate them using touch events and on Windows 8 you use IE10's pointer events directly. Thanks to deferred binding this shouldn't be that hard to implement. Personally I think thats the way to go in the future. -- J. -- 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/-/Od7fOBW9_jMJ. 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.
