RAD includes the current popular technology (OKHttp, Rx, Aop, MVP), do not repeat, add some features
-
ViewModel Vertical and horizontal screen reuse
- AndroidManifest config configChanges Only suitable for horizontal and vertical screen layout consistent scene
- The screen is usually rotated to re-fill, but the data can be reused
- Some scenes can be combined with the ViewModel middle class to reuse, refer to ImageFragment
-
Network use OKNet
- Perfect cache, Rx, exception distribution support
-
Perfect UI and network, base class framework linkage writing
-
Base class free combination, support DataBinding
- DataBing layout xml file needs to wrap the layout node, the include node also needs, the layout of the new component or id, may need to be in the right panel of Android Studio Refresh All, or Rebuild
- Please see the project base class inheritance chain, if you want to use butterknife, direct inheritance ViewModelBaseActivity can
- Business base class only DataBinding as an alternative to butterknife use, the default layout bound variable id BR.viewModel
-
aop enable，in app module apply pluginRelease the comment
-
Welcome advice, issue