-
Notifications
You must be signed in to change notification settings - Fork 100
GettingStarted
- summary Getting Started with mgwt
- labels Featured
MGWT heavily relies on GWT MVP, ClientBundles, GWT Logging. If you don`t know these GWT Basics read them up in the gwt docs. mgwt does not try to replicate GWT functionality, it only adds functionality thats currently missing in the gwt core for mobile development. mgwt alwawys tries to do this in a gwt fashion.
To use mgwt you need to include it in your gwt.xml file. You can also set the user agent property for gwt to safari, because almost any mobile device runs on webkit and mgwt relies on webkit.
mgwt adds its own ActivityManager (AnimationActivityManager) which can handle page transitions with animations. Therefore it needs an instance of AnimationMapper and an instanceof AnimatableDisplay. For every region of your screen you need an AnimatingActivityManager. (Similar to the GWT ActivityManager).
The MGWT ActivityManager relies on an AnimationMapper to provide the animation it needs to execute on a place change. For every possible combination of places you can provide different animations. Here is a quick example:
Animations are handled differently on different platforms by mgwt. To ensure you don´t get any overhead mgwt uses deferred binding. To get an instance of AnimatableDisplay simply use GWT create: